public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: devel@edk2.groups.io, neiljay@gmail.com
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	 Sami Mujawar <Sami.Mujawar@arm.com>
Subject: Re: [edk2-devel] PATCH [1/1] ArmPkg: Fix GicV2 BaseAddress types
Date: Fri, 12 May 2023 19:28:55 +0100	[thread overview]
Message-ID: <CAKbZUD34gP5AtckpQ92K-Heh9ituBFYVL76amYcAUHqbJOvuVw@mail.gmail.com> (raw)
In-Reply-To: <d7QO.1683809553000172139.bILM@groups.io>

(+CC maintainers)

On Thu, May 11, 2023 at 5:47 PM <neiljay@gmail.com> wrote:
>
> The GIC v2 base addresses can be 64bit, don't limit to 32 on 64bit
> machines.
>
> Signed-off-by: Neil Jones <neil.jones@blaize.com>
> ---
>  ArmPkg/Drivers/ArmGic/GicV2/ArmGicV2Dxe.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/ArmPkg/Drivers/ArmGic/GicV2/ArmGicV2Dxe.c b/ArmPkg/Drivers/ArmGic/GicV2/ArmGicV2Dxe.c
> index 25290342bd..b990bf3a8a 100644
> --- a/ArmPkg/Drivers/ArmGic/GicV2/ArmGicV2Dxe.c
> +++ b/ArmPkg/Drivers/ArmGic/GicV2/ArmGicV2Dxe.c
> @@ -25,8 +25,8 @@ Abstract:
>  extern EFI_HARDWARE_INTERRUPT_PROTOCOL   gHardwareInterruptV2Protocol;
>  extern EFI_HARDWARE_INTERRUPT2_PROTOCOL  gHardwareInterrupt2V2Protocol;
>
> -STATIC UINT32  mGicInterruptInterfaceBase;
> -STATIC UINT32  mGicDistributorBase;
> +STATIC UINTN mGicInterruptInterfaceBase;
> +STATIC UINTN mGicDistributorBase;
>
>  /**
>    Enable interrupt source Source.
> --
> 2.39.2

LGTM, particularly as the PCDs are 64-bit already.
Reviewed-by: Pedro Falcato <pedro.falcato@gmail.com>

but CC'ing the proper maintainers (please do so in the future!)

-- 
Pedro

  reply	other threads:[~2023-05-12 18:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11 12:52 PATCH [1/1] ArmPkg: Fix GicV2 BaseAddress types neiljay
2023-05-12 18:28 ` Pedro Falcato [this message]
2023-05-24 10:48 ` [edk2-devel] " Sami Mujawar
2023-05-29 11:44   ` Ard Biesheuvel
2023-06-01 16:09     ` Ard Biesheuvel

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=CAKbZUD34gP5AtckpQ92K-Heh9ituBFYVL76amYcAUHqbJOvuVw@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