From: eric@eukrea.com (Eric Bénard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] i.MX31 and i.MX35 : fix errate TLSbo65953 and ENGcm09472
Date: Tue, 05 Oct 2010 22:00:02 +0200 [thread overview]
Message-ID: <4CAB83C2.3040301@eukrea.com> (raw)
In-Reply-To: <20101005194659.GY11737@pengutronix.de>
Hi Uwe,
Le 05/10/2010 21:46, Uwe Kleine-K?nig a ?crit :
> hmm, it's a copy of the code suggested there, yes. The text before the
> example doesn't suggest that timing is an issue for the work around. I
> interpret it that everything is fine when the caches are off before
> executing the wfi instruction. But OK, it wouldn't be the first time
> hardware documentation isn't exact to the point.
>
Well the doc says there is an other workaround (setting CPU freq = AHB
freq, waiting clock to switch, WFI, restore original CPU freq) doesn't
work for me and support seems not very confident with this other
workaround as they immediatl directed me to this one ...
> Hmm, when the caches are off before entering wfi, does that mean that
> all interrupt (and fiq) handlers run with the caches off, too? That's
> very bad, isn't it?
>
If I understand well, this case happens only when they run after WFI
which means cpuidle was called (and thus CPU activity was null for a
certain amount of time, which explains why it's easier to reproduce the
problem with tslib than with qtdemo which takes 100% CPU and don't let
cpuidle to execute very often).
That may seems bad, but I find this solution better than having an oops
after a few IRQs which makes the CPU unusable for real life applications :-)
Eric
next prev parent reply other threads:[~2010-10-05 20:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 13:55 I.MX35 GPIO IRQ + Preempt -> Oops Eric Bénard
2010-10-03 11:41 ` Russell King - ARM Linux
2010-10-03 15:25 ` Eric Bénard
2010-10-03 16:20 ` Russell King - ARM Linux
2010-10-03 17:15 ` Eric Bénard
2010-10-04 7:39 ` Uwe Kleine-König
2010-10-04 8:08 ` Eric Bénard
2010-10-04 12:07 ` Eric Bénard
2010-10-05 5:06 ` Marc Reilly
2010-10-05 7:28 ` Eric Bénard
2010-10-05 9:13 ` Eric Bénard
2010-10-05 9:25 ` [PATCH/RFC] i.MX31 and i.MX35 : fix errate TLSbo65953 and ENGcm09472 Eric Bénard
2010-10-05 9:45 ` Sascha Hauer
2010-10-05 12:00 ` [PATCH v2] " Eric Bénard
2010-10-05 18:33 ` Uwe Kleine-König
2010-10-05 19:31 ` Eric Bénard
2010-10-05 19:46 ` Uwe Kleine-König
2010-10-05 20:00 ` Eric Bénard [this message]
2010-10-05 20:04 ` Uwe Kleine-König
2010-10-05 20:27 ` Eric Bénard
2010-10-06 2:28 ` Nicolas Pitre
2010-10-06 11:09 ` Eric Bénard
2010-10-08 8:49 ` [PATCH v3] " Eric Bénard
2010-10-07 7:27 ` [PATCH v2] " Russell King - ARM Linux
2010-10-05 16:29 ` [PATCH/RFC] " Uwe Kleine-König
2010-10-05 16:48 ` Eric Bénard
2010-10-05 17:40 ` Uwe Kleine-König
2010-10-06 6:35 ` Daniel Mack
2010-10-06 7:03 ` Uwe Kleine-König
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=4CAB83C2.3040301@eukrea.com \
--to=eric@eukrea.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;
as well as URLs for NNTP newsgroup(s).