Make omap24xx booting device tree based for v3.14 merge window
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 11 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 11 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 00/11] Make omap24xx booting device tree based for v3.14 merge window
Quoted 27 lines · Aaro Koskinen
Hi,
Quoted 10 lines · Tony Lindgren
Here are some early patches for the v3.14 merge window to make omap2 booting device tree based before we make omap3 device tree only. Otherwise we cannot remove the shared platform data between omap2 and 3 for things like some hwmod entries.
I've added minimal support for 2430sdp to boot it to serial console with ethernet working, and kept n8x0 support using the legacy init for the drivers. Then the old H4 I have not updated as I'm not using it.
Quoted 4 lines
Hopefully if there are still people using n8x0 they can pick up the work from here on removing the rest of the legacy platform data init as we're planning to drop those things completely over next few merge cycles.
Thanks for the effort, I'll try to continue this work. You can add my Tested-by for N8x0 bits.
Quoted 5 lines
Note that these patches are against mainline commit
10d0c9705as there are few device tree related fixes to stuff the resources. These also depend on the recently posted fixes series "[PATCH 0/8] Various omap device tree usability fixes for v3.13 merge window"
Quoted 5 lines
I noticed one bug. If you disable
MACH_NOKIA_N8X0from .config, there is a compilation failure:
arch/arm/mach-omap2/built-in.o: In function `omap2420_n8x0_legacy_init':/home/aaro/git/linux/arch/arm/mach-omap2/pdata-quirks.c:76: undefined reference to `n8x0_legacy_init'
OK thanks for testing, I'll fix that.
Regards,
Tony