From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: LiuYu <liuyu@greatwall.com.cn>, leif@nuviainc.com
Cc: devel@edk2.groups.io
Subject: Re: [edk2-devel][PATCH] ArmPkg/ArmPciCpuIo2Dxe: Correct pci io memmap address
Date: Tue, 15 Sep 2020 12:38:32 +0300 [thread overview]
Message-ID: <acb62bbe-a373-e676-6f93-dc25faac1aa4@arm.com> (raw)
In-Reply-To: <da342cbbdac2076c237474c1ca1520ea36b5355b.1600161581.git.liuyu@greatwall.com.cn>
On 9/15/20 11:35 AM, LiuYu wrote:
> Since the device addresss has been translated in PciRootBridgeIo.c
> so shuldn't translate it twice in ArmPciCpuIo2Dxe.c
>
> Signed-off-by: LiuYu <liuyu@greatwall.com.cn>
Nack. The I/O translation in the I/O domain and the mapping of the I/O
window in the physical memory space are two different translations, and
they both need to be applied.
PciRootBridgeIo.c deals with the former, whereas this driver deals with
the latter.
> ---
> ArmPkg/Drivers/ArmPciCpuIo2Dxe/ArmPciCpuIo2Dxe.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/ArmPkg/Drivers/ArmPciCpuIo2Dxe/ArmPciCpuIo2Dxe.c b/ArmPkg/Drivers/ArmPciCpuIo2Dxe/ArmPciCpuIo2Dxe.c
> index d8625e1593..8c46a2778b 100644
> --- a/ArmPkg/Drivers/ArmPciCpuIo2Dxe/ArmPciCpuIo2Dxe.c
> +++ b/ArmPkg/Drivers/ArmPciCpuIo2Dxe/ArmPciCpuIo2Dxe.c
> @@ -399,7 +399,6 @@ CpuIoServiceRead (
> return Status;
> }
>
> - Address += PcdGet64 (PcdPciIoTranslation);
>
> //
> // Select loop based on the width of the transfer
> @@ -485,7 +484,6 @@ CpuIoServiceWrite (
> return Status;
> }
>
> - Address += PcdGet64 (PcdPciIoTranslation);
>
> //
> // Select loop based on the width of the transfer
>
prev parent reply other threads:[~2020-09-15 9:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 9:35 [edk2-devel][PATCH] ArmPkg/ArmPciCpuIo2Dxe: Correct pci io memmap address Yu Liu
2020-09-15 9:38 ` Ard Biesheuvel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=acb62bbe-a373-e676-6f93-dc25faac1aa4@arm.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox