From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: errata: LoUIS bit field in CLIDR register is incorrect
Date: Thu, 6 Jun 2013 16:43:39 +0100 [thread overview]
Message-ID: <20130606154339.GH16794@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1370532888.3500.11.camel@computer5.home>
On Thu, Jun 06, 2013 at 04:34:48PM +0100, Jon Medhurst (Tixy) wrote:
> On Thu, 2013-06-06 at 16:01 +0100, Will Deacon wrote:
> > > diff --git a/arch/arm/mach-vexpress/Kconfig b/arch/arm/mach-vexpress/Kconfig
> > > index 5907e10..fe637e9 100644
> > > --- a/arch/arm/mach-vexpress/Kconfig
> > > +++ b/arch/arm/mach-vexpress/Kconfig
> > > @@ -56,5 +56,6 @@ config ARCH_VEXPRESS_CORTEX_A5_A9_ERRATA
> > >
> > > config ARCH_VEXPRESS_CA9X4
> > > bool "Versatile Express Cortex-A9x4 tile"
> > > + select ARM_ERRATA_643719
> >
> > We don't do this for any other workarounds, so I'd suggest either dropping
> > this or having a separate patch adding all of those that are required.
>
> Not quite sure by what you mean by 'all of those that are required'. All
> the errata required for vexpress? Or all platforms which require the
> errata workaround?
I mean, the A9 coretile on vexpress also has other errata, for which we have
workarounds in the kernel. They aren't automatically selected (for example,
ARM_ERRATA_720789) so if you want to do this, it's worth selecting all or
none, rather than make it look like you're selecting all those that apply
when you're not.
> If we don't enable the workaround in the Kconfig, then do we just add it
> to the vexpress_defconfig and hope people notice? Or, as we have
> ARCH_VEXPRESS_CORTEX_A5_A9_ERRATA, we could select it in there?
It doesn't affect A5, so I wouldn't put it there. The usual place is the
defconfig.
> Finally, whilst I'm asking questions ;-) I was hoping to fix a
> regression that slipped into 3.10, is this late -rc material or will it
> end up waiting for 3.11?
The fix to v7_flush_dcache_louis should go in for 3.10 and probably stable
as well. I don't think the vexpress kconfig stuff is as important.
Will
next prev parent reply other threads:[~2013-06-06 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 13:58 [PATCH] ARM: errata: LoUIS bit field in CLIDR register is incorrect Jon Medhurst (Tixy)
2013-06-06 15:01 ` Will Deacon
2013-06-06 15:34 ` Jon Medhurst (Tixy)
2013-06-06 15:43 ` Will Deacon [this message]
2013-06-06 16:46 ` Nicolas Pitre
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=20130606154339.GH16794@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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