From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH] ArmPkg/ArmGicV3Dxe: use correct value for ARM_GICD_IROUTER
Date: Mon, 14 Jan 2019 16:22:44 +0100 [thread overview]
Message-ID: <CAKv+Gu_KpigLm+hr7w=+xx4Roh4f5AydmVZkHZo1fCju98CrrA@mail.gmail.com> (raw)
In-Reply-To: <20190114112424.weqnta4n4jijrszz@bivouac.eciton.net>
On Mon, 14 Jan 2019 at 12:24, Leif Lindholm <leif.lindholm@linaro.org> wrote:
>
> On Fri, Dec 21, 2018 at 04:08:48PM +0100, Ard Biesheuvel wrote:
> > Use the correct value for ARM_GICD_IROUTER as per the GIC spec,
> > and fix the code that relies on the value being skewed by 32 x 8
> > bytes.
> >
> > Contributed-under: TianoCore Contribution Agreement 1.1
> > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > ---
> > ArmPkg/Include/Library/ArmGicLib.h | 2 +-
> > ArmPkg/Drivers/ArmGic/GicV3/ArmGicV3Dxe.c | 2 +-
> > 2 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/ArmPkg/Include/Library/ArmGicLib.h b/ArmPkg/Include/Library/ArmGicLib.h
> > index 5775905ca91b..b52b77628ae1 100644
> > --- a/ArmPkg/Include/Library/ArmGicLib.h
> > +++ b/ArmPkg/Include/Library/ArmGicLib.h
> > @@ -43,7 +43,7 @@
> > #define ARM_GIC_ICDSGIR 0xF00 // Software Generated Interrupt Register
> >
> > // GICv3 specific registers
> > -#define ARM_GICD_IROUTER 0x6100 // Interrupt Routing Registers
> > +#define ARM_GICD_IROUTER 0x6000 // Interrupt Routing Registers
>
> Actually, whilst I agree the above would be more consistent, both
> revisions C and D of ARM IHI 0069 list the address offset of
> ARM_GICD_IROUTER as 0x6100 (and the preceding register space as
> "Reserved").
>
OK, in that case, please disregard this patch.
prev parent reply other threads:[~2019-01-14 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 15:08 [PATCH] ArmPkg/ArmGicV3Dxe: use correct value for ARM_GICD_IROUTER Ard Biesheuvel
2019-01-14 11:24 ` Leif Lindholm
2019-01-14 15:22 ` 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='CAKv+Gu_KpigLm+hr7w=+xx4Roh4f5AydmVZkHZo1fCju98CrrA@mail.gmail.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