Gopinath, Thara had written, on 10/06/2009 01:59 AM, the following:
The problem here is not with the restore. If MPU reads the PADCONF_SAVEDONE bit very close
to the end of context save sequence for the pad conf registers, the last context is not
saved to the scratchpad memory. This is a h/w bug. The workaround proposed is to delay the
MPU access of SAVEDONE bit until the last context has been saved. 300 us delay is the current
safe delay proposed by TI. I believe investigations are going on to whether this delay can be
optimized. Also only the last context (ETK_D14) has the risk of not getting saved.
So, if I were to save specifically the ETK14 and restore it explicitly,
I could in theory work around this issue.
We could add a defconfig option for this workaround and enable it on need basis till TI
comes out with proper optimized workaround sequence.
we could probably hope to see a final patch then I believe?
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
