OMAP-GPMC generic timing migration
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 4 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 4 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] OMAP-GPMC generic timing migration
Hi Tony,
Quoted 4 lines · Afzal Mohammed
I certainly don't think it is easier, rather tougher, cleaner as well. One thing that worried me was, if we pursue the auxdata path (a last resort option) and later if it is objected, we would be back to square one.
I commented on auxdata usage without visualising in more detail how it can be implemented, it was bad of me.
I doubt whether auxdata would help here, it seems using compatible field alone would help in deciding relevant custom timing routine. Whether we want this kind of peripheral knowledge in gpmc driver instead of using generic timing routine has to be decided though.
Quoted 1 line
Let me discuss internally and get back.
Regards
Afzal