From: Roger Quadros <rogerq@ti.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "Dechesne, Nicolas" <n-dechesne@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: L2 cache stability workaround for 4460 ES1.0
Date: Mon, 2 Apr 2012 10:55:34 +0300 [thread overview]
Message-ID: <4F795B76.3030002@ti.com> (raw)
In-Reply-To: <CAMQu2gzsjUKUZtXnTeQ2UoRUQ5ZX4gxY3Cm9hGTLLc70eknUHA@mail.gmail.com>
On 04/02/2012 10:38 AM, Shilimkar, Santosh wrote:
> On Mon, Apr 2, 2012 at 12:25 PM, Roger Quadros <rogerq@ti.com> wrote:
>> Hi Santosh,
>>
>> I came across the attached patch from you. I also came across this post
>> stating that it was decided not to send this patch upstream.
>>
>> http://www.digipedia.pl/usenet/thread/18885/8437/#post8496
>>
>> The problem is that we have to keep porting this patch each time we
>> update the kernel.
>>
>> Do you know if the root cause has been found? If not can we have this
>> patch upstream till the root cause is found?
>>
> Yes and fixed in OMAP4460 ES1.2.
Did you mean ES1.1?
Could you please point me to the errata ID? The only cache related
errata I can see is Errata ID: i690
>
>> It seems the patch at least makes the kernel usable on ES1.0.
>>
> I know but that still is not enough. It's like 80 % WA of the issue
> seen on ES1.0. We are not suppose to have many boards with
> ES1.0
>
Even better if there are not many boards. It seems most of the boards
will be with TI. I think we should have the fix in even if it is not
100% fix.
What do you say?
regards,
-roger
next prev parent reply other threads:[~2012-04-02 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 6:55 L2 cache stability workaround for 4460 ES1.0 Roger Quadros
2012-04-02 7:38 ` Shilimkar, Santosh
2012-04-02 7:55 ` Roger Quadros [this message]
2012-04-02 7:58 ` Shilimkar, Santosh
2012-04-02 8:02 ` Roger Quadros
2012-04-02 9:13 ` Shilimkar, Santosh
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=4F795B76.3030002@ti.com \
--to=rogerq@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=n-dechesne@ti.com \
--cc=santosh.shilimkar@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.