OMAP36xx-based Overo (Storm and alike) are now failing to boot with 3.14-rc2 [1]. This series fixes this, by moving model-agnostic DT into a common dtsi file, and creating model-specific DT files: - omap3-overo-tobi.dts -> older OMAP35xx Overo - omap3-overo-storm-tobi.dts -> newer OMAP36xx/AM37xx/DM37xx Overo People will have to use the right Overo / expansion board combination. (Patch 2 in an unrelated fix that was waiting in my queue.) omap3-overo-tobi.dts tested with Overo Sand (OMAP3503) and omap3-overo-storm-tobi.dts tested with Overo EarthStorm (AM3703). Both boot. With the Overo Sand, I cannot mount the ext3 rootfs, but this seems unrelated to the current topic, maybe a missing errata. Regards, Florian Changes since v1: - Add "ti,omap3430" as a compatible string for OMAP35xx-based Overo - Update the DT documentation to silence out checkpatch warnings (patch 4) [1] http://thread.gmane.org/gmane.linux.ports.arm.omap/110006 Florian Vaussard (4): ARM: dts: omap3-tobi: Fix boot with OMAP36xx-based Overo ARM: dts: omap3-tobi: Use the correct vendor prefix ARM: dts: Add support for both OMAP35xx and OMAP36xx Overo/Tobi Documentation: dt: OMAP: Update Overo/Tobi .../devicetree/bindings/arm/omap/omap.txt | 2 +- arch/arm/boot/dts/Makefile | 3 ++- arch/arm/boot/dts/omap3-overo-storm-tobi.dts | 22 ++++++++++++++++++++++ ...omap3-tobi.dts => omap3-overo-tobi-common.dtsi} | 3 --- arch/arm/boot/dts/omap3-overo-tobi.dts | 22 ++++++++++++++++++++++ arch/arm/boot/dts/omap3-overo.dtsi | 3 --- 6 files changed, 47 insertions(+), 8 deletions(-) create mode 100644 arch/arm/boot/dts/omap3-overo-storm-tobi.dts rename arch/arm/boot/dts/{omap3-tobi.dts => omap3-overo-tobi-common.dtsi} (94%) create mode 100644 arch/arm/boot/dts/omap3-overo-tobi.dts -- 1.8.1.2 -- 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
