[Maverick] [ti-omap4] SRU: A workaround for highmem issue on OMAP4 platform

[Shilimkar, Santosh]

> -----Original Message-----
> From: kernel-team-bounces at lists.ubuntu.com [mailto:kernel-team-
> bounces at lists.ubuntu.com] On Behalf Of Bryan Wu
> Sent: Friday, October 01, 2010 9:40 AM
> To: Ricardo Salveti de Araujo
> Cc: nicolas.pitre at linaro.org; kernel-team at lists.ubuntu.com;
> ogra at canonical.com; ricardo.salveti at canonical.com
> Subject: Re: [Maverick] [ti-omap4] SRU: A workaround for highmem issue on
> OMAP4 platform
> 
> On Fri, Oct 1, 2010 at 11:56 AM, Ricardo Salveti de Araujo
> <rsalveti at rsalveti.net> wrote:
> > On Thu, Sep 30, 2010 at 11:14:34PM +0200, Dechesne, Nicolas wrote:
> >> Santosh,
> >>
> >> > CONFIG_PL310_ERRATA_588369 errata is pretty much must for OMAP4 ES1.0.
> This
> >> > should always be enabled on OMAP4 ES1.0 not to see any undefined
> behaviour.
> >>
> >> but we are on ES2.0, not ES1.0. What is the impact of enabling this
> errata on ES2.0?
> >
> > From the talk I had with Rob Clark:
> >
> > <robclark> ndec / rsalveti: which errata?
> > <rsalveti> robclark: PL310_ERRATA_588369
> > <robclark> ok.. let me check
> > <robclark> rsalveti: ok.. this one seems to apply to the cortex-a9 IP,
> prior to r2p0
> > <robclark> (just need to check which rev on cortex is in es2.0)
> > <robclark> r1p2.. so keep the errata enabled
> >
> 
> I was confused here, if the errata is apply to cortex-a9 IP prior to
> r2p0, r1p2 silicon is supposed to fix this issue in hardware. Do we
> still need this in software?
> 
This errata is not applicable for ES2.0(Pl310) and should not be enabled.
I just think it's masking some other issue.