public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sudeep Holla" <sudeep.holla@arm.com>
To: Sami Mujawar <sami.mujawar@arm.com>
Cc: devel@edk2.groups.io, ardb+tianocore@kernel.org,
	thomas.abraham@arm.com, Pierre.Gondois@arm.com,
	Matteo.Carlini@arm.com, Akanksha.Jain2@arm.com,
	Ben.Adderson@arm.com, Sibel.Allinson@arm.com, nd@arm.com
Subject: Re: [PATCH edk2-platforms v1 1/1] Platform/Arm: Disable memmap platform timers for JunoR0
Date: Fri, 16 Jun 2023 13:56:42 +0100	[thread overview]
Message-ID: <20230616125642.tydl6mfhr7ga4rcd@bogus> (raw)
In-Reply-To: <20230616124059.19524-1-sami.mujawar@arm.com>

On Fri, Jun 16, 2023 at 01:40:59PM +0100, Sami Mujawar wrote:
> Juno includes a system-level wakeup timer which is an implementation
> of the ARM Generic Timer architecture.
> The CNTCTL frame contains some registers that are accessible using a
> Non-Secure access. Juno R0 incorrectly limits these accesses to Secure
> access only. This issue is documented in the Juno Errata
> 832219: APB port security breaks SBSA compliance
> https://developer.arm.com/documentation/epm008857/latest
> 
> This results in a crash when the OS tries to access these registers.
> Therefore, disable memory mapped platform timers for Juno R0.
> 
> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
> Cc: Thomas Abraham <thomas.abraham@arm.com>
> Cc: Sudeep Holla <Sudeep.Holla@arm.com>
>

Tested-by: Sudeep Holla <Sudeep.Holla@arm.com>

(fixes the ACPI based Linux boot on Juno R0 platform)


-- 
Regards,
Sudeep

  reply	other threads:[~2023-06-16 12:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 12:40 [PATCH edk2-platforms v1 1/1] Platform/Arm: Disable memmap platform timers for JunoR0 Sami Mujawar
2023-06-16 12:56 ` Sudeep Holla [this message]
2023-06-28 10:56 ` PierreGondois

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=20230616125642.tydl6mfhr7ga4rcd@bogus \
    --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