From: "Pete Batard" <pete@akeo.ie>
To: devel@edk2.groups.io,
Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
Cc: Leif Lindholm <leif@nuviainc.com>,
Andrei Warkentin <awarkentin@vmware.com>,
Ard Biesheuvel <ard.biesheuvel@arm.com>
Subject: Re: [edk2-devel] [edk2-platform][PATCH v1 1/1] Platforms/RaspberryPi: Fix RPi4 GICC PMU PPI
Date: Mon, 3 Aug 2020 18:12:13 +0100 [thread overview]
Message-ID: <a0fd331d-fb1b-f498-0eee-180cb8829a35@akeo.ie> (raw)
In-Reply-To: <1626C72E5FC5B4C0.4967@groups.io>
Adding a tested-by, since these are values that could potentially trip
the custom handling that Windows seems to have of MADT, and I hadn't
tested that yet.
Testing shows that Windows is happy with these new values, so with this:
On 2020.07.31 08:55, Pete Batard via groups.io wrote:
> On 2020.07.28 22:00, Samer El-Haj-Mahmoud wrote:
>> Arm SBSA specification section ver 6.0, 4.1.5 defines specific PPI
>> values for certain standard interrupt IDs. The value for
>> "Performance Monitors Interrupt" needs to be 23.
>>
>> REF: https://developer.arm.com/documentation/den0029/latest
>>
>> This partially fixes SBSA test #11 ("Incorrect PPI value") reported in
>> https://github.com/pftf/RPi4/issues/74
>>
>> Cc: Leif Lindholm <leif@nuviainc.com>
>> Cc: Pete Batard <pete@akeo.ie>
>> Cc: Andrei Warkentin <awarkentin@vmware.com>
>> Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>
>> Signed-off-by: Samer El-Haj-Mahmoud <samer.el-haj-mahmoud@arm.com>
>> ---
>> Platform/RaspberryPi/RPi4/RPi4.dsc | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/Platform/RaspberryPi/RPi4/RPi4.dsc
>> b/Platform/RaspberryPi/RPi4/RPi4.dsc
>> index c481c3534263..00683afe96b9 100644
>> --- a/Platform/RaspberryPi/RPi4/RPi4.dsc
>> +++ b/Platform/RaspberryPi/RPi4/RPi4.dsc
>> @@ -433,10 +433,10 @@ [PcdsFixedAtBuild.common]
>> gRaspberryPiTokenSpaceGuid.PcdGicInterruptInterfaceHBase|0xFF844000
>> gRaspberryPiTokenSpaceGuid.PcdGicInterruptInterfaceVBase|0xFF846000
>> gRaspberryPiTokenSpaceGuid.PcdGicGsivId|0x19
>> - gRaspberryPiTokenSpaceGuid.PcdGicPmuIrq0|0x30
>> - gRaspberryPiTokenSpaceGuid.PcdGicPmuIrq1|0x31
>> - gRaspberryPiTokenSpaceGuid.PcdGicPmuIrq2|0x32
>> - gRaspberryPiTokenSpaceGuid.PcdGicPmuIrq3|0x33
>> + gRaspberryPiTokenSpaceGuid.PcdGicPmuIrq0|23
>> + gRaspberryPiTokenSpaceGuid.PcdGicPmuIrq1|23
>> + gRaspberryPiTokenSpaceGuid.PcdGicPmuIrq2|23
>> + gRaspberryPiTokenSpaceGuid.PcdGicPmuIrq3|23
>> #
>> # Fixed CPU settings.
>>
>
> Reviewed-by: Pete Batard <pete@akeo.ie>
Tested-by: Pete Batard <pete@akeo.ie>
>
>
>
next prev parent reply other threads:[~2020-08-03 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 21:00 [edk2-platform][PATCH v1 1/1] Platforms/RaspberryPi: Fix RPi4 GICC PMU PPI Samer El-Haj-Mahmoud
2020-07-31 7:55 ` Pete Batard
2020-08-13 13:52 ` Ard Biesheuvel
[not found] ` <1626C72E5FC5B4C0.4967@groups.io>
2020-08-03 17:12 ` Pete Batard [this message]
2020-08-11 12:24 ` [edk2-devel] " Samer El-Haj-Mahmoud
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=a0fd331d-fb1b-f498-0eee-180cb8829a35@akeo.ie \
--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