OMAP-GPMC related cleanup for common zImage
Get series with b4
b4 am [email protected]Versions newest first
- v2 Latest1 of 14 patches 0 repliesNew
1 of 14 patches is in this archive. The cover letter announces 14.
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 6/14 | mtd: onenand: omap: use pdata info instead of cpu_is | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 00/14] OMAP-GPMC related cleanup for common zImage
Hi Ivan,
Quoted 8 lines · Tony Lindgren
Quoted 5 lines · Ivan Djelic
I ran several mtd regression tests on a Beagle Board on your gpmc-czimage-v2 tag. All BCH error correcting tests passed successfully.
I occasionally had weird read errors though, especially when reading blank pages:
the omap driver returned 512-byte sectors containing something like:
Quoted 7 lines
Quoted 3 lines
I was able to reproduce the problem also on l2-mtd tip, albeit less often. The problem seems to occur quite randomly, it may be a hardware issue on my board...
Things like this typically happen in the GPMC timings are not correct. Maybe add #define DEBUG to top of
gpmc.cand compare the timings before and after Afzal's patches?
Latest series for gpmc related cleanup for common zImage removed dependency on minor timing cleanups (this series was dependent on on another series that did minor timing cleanups).
A pull request for the new series on gpmc cleanup for common zImage that does not contain timing related changes and without dependency on timing related changes has been sent to Tony (forwarded to you now). He has pulled those changes onto l-o in "omap-for-v3.8/cleanup-headers-gpmc"
As there are no changes w.r.t timing's in the new series, behaviour should be same as without.
Quoted 1 line
Quoted 1 line
Anyway, the ECC handling part looks OK to me.
Regards
Afzal