From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] ARM: implement some Cortex-A9 errata workarounds
Date: Mon, 4 Mar 2013 19:00:10 +0100 [thread overview]
Message-ID: <20130304190010.37585859@lilith> (raw)
In-Reply-To: <5FBF8E85CA34454794F0F7ECBA79798F37A65ED78E@HQMAIL04.nvidia.com>
Hi Tom,
On Mon, 4 Mar 2013 08:30:11 -0800, Tom Warren <TWarren@nvidia.com>
wrote:
> Stephen & Albert,
>
> > -----Original Message-----
> > From: Stephen Warren [mailto:swarren at wwwdotorg.org]
> > Sent: Friday, March 01, 2013 2:54 PM
> > To: Tom Warren
> > Cc: u-boot at lists.denx.de; Stephen Warren
> > Subject: Re: [U-Boot] [PATCH 1/3] ARM: implement some Cortex-A9 errata
> > workarounds
> >
> > On 02/28/2013 10:08 AM, Stephen Warren wrote:
> > > On 02/26/2013 03:28 PM, Stephen Warren wrote:
> > >> From: Stephen Warren <swarren@nvidia.com>
> > >>
> > >> Various errata exist in the Cortex-A9 CPU, and may be worked around
> > >> by setting some bits in a CP15 diagnostic register. Add code to
> > >> implement the workarounds, enabled by new CONFIG_ options.
> > >>
> > >> This code was taken from the Linux kernel, v3.8,
> > >> arch/arm/mm/proc-v7.S, and modified to remove the logic to
> > >> conditionally apply the WAR (since we know exactly which CPU we're
> > >> running on given the U-Boot configuration), and use r0 instead of r10
> > >> for consistency with the rest of U-Boot's cpu_init_cp15().
> > >
> > > Hmmm. Lets hold off on this series; there are some conditions under
> > > which the kernel has to be able to apply these WARs anyway (e.g. SMP
> > > CPU power saving), which may impact which of the WARs the bootloader
> > > should apply even when booting the initial CPU 0. I'll repost once
> > > that's been resolved.
> >
> > Tom,
> >
> > It looks like the bootloader should always apply these WARs for CPU 0.
> > We just have to make sure that the kernel applies them for CPUs 1..n if/when
> > running in secure mode.
> >
> > In other words, I think these patches are good to go in as-is. Since there
> > are no changes to the patches, I won't repost them, unless you need me to.
>
> I can take these in via the Tegra tree, but the bulk of the changes are for ARM, not Tegra.
> Albert - do you want to take this directly into the ARM repo, or would you prefer me to take it?
I will take them in tonight.
> Tom
> --
> nvpublic
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-03-04 18:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 22:28 [U-Boot] [PATCH 1/3] ARM: implement some Cortex-A9 errata workarounds Stephen Warren
2013-02-26 22:28 ` [U-Boot] [PATCH 2/3] ARM: tegra: enable some CPU " Stephen Warren
2013-03-15 5:59 ` Albert ARIBAUD
2013-02-26 22:28 ` [U-Boot] [PATCH 3/3] ARM: mx6: use common CPU errata config options Stephen Warren
2013-02-27 0:15 ` Fabio Estevam
2013-02-27 2:44 ` Liu Hui-R64343
2013-03-07 17:24 ` Stefano Babic
2013-03-07 19:19 ` Stephen Warren
2013-03-08 8:12 ` Stefano Babic
2013-02-28 0:30 ` [U-Boot] [PATCH 1/3] ARM: implement some Cortex-A9 errata workarounds Simon Glass
2013-02-28 0:36 ` Stephen Warren
2013-02-28 0:38 ` Simon Glass
2013-02-28 17:08 ` Stephen Warren
2013-03-01 21:53 ` Stephen Warren
2013-03-01 23:02 ` Tom Warren
2013-03-04 16:30 ` Tom Warren
2013-03-04 18:00 ` Albert ARIBAUD [this message]
2013-03-04 19:07 ` Tom Warren
2013-03-15 5:58 ` Albert ARIBAUD
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-all 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=20130304190010.37585859@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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