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
Quoted 9 lines · Mohammed, Afzal
Hi Daniel,
Quoted 4 lines · Daniel Mack
Admittedly, I lost track on the multiple GPMC series here, and they also cause major merge conflicts with Linus' current master branch.
Could you tell me which patches I need on top of soon-to-be-3.7-rc1? I
Quoted 8 lines
Series [1-2] plus this series would be the required. Note that 1st patch of series [2] has already reached mainline.
Another easy way would be, pull,
git://gitorious.org/x0148406-public/linux-kernel.gitgpmc-timinggit checkout -b gpmc <myremote/gpmc-timing>
git rebase --onto <Linus-current-master> next-20121005 (or "080aa9c")
After -rc1 is out, let's plan on adding the minimal set required for removing plat and mach includes from drivers into a clean-up branch. Afzal, can you maybe do a pull request for that set against -rc1 when it's out? Just the minimal set of patches.
Quoted 7 lines
Quoted 2 lines
would like to augment this to make GPMC attached NAND probable in DT, in case this is still an open topic.
I would be doing gpmc DT conversion next. Hoping that this series too will be picked up by Tony, as once this series is accepted, during DT conversion we need not rely on auxdata (a last resort option) for timings.
Yes, then please do a second pull request for what's needed to apply the minimal DT bindings. For the DT binding, let's just leave out the timings for now as we can load those from auxdata. Then the binding for the timings can be added later on. So just the minimal binding using standard features for the iorange and interrupt.
Thanks,
Tony