[PATCH v2] i.MX31 and i.MX35 : fix errate TLSbo65953 and ENGcm09472
u.kleine-koenig at pengutronix.de
Tue Oct 5 16:04:14 EDT 2010
>> 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
Ack, but it makes me think if the caches should be enabled in the irq
entry point, too.
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
More information about the linux-arm-kernel