We have devices like co-processors, SoC internal busses, memory controllers etc which should not be idled or reset. In some cases erratas around IP blocks prevent them from either being idled or reset. Have a way to pass this information from Device tree, and get rid of similar information that exists as part of the omap_hwmod data files for various DT only OMAP SoCs. Patches are tested on am335x beagleboneblack and omap4 panda es boards. Rajendra Nayak (3): ARM: OMAP2+: hwmod: cleanup HWMOD_INIT_NO_RESET usage ARM: OMAP2+: Add new bindings for OMAP ARM: OMAP2+: Let DT say what devices should not to idled or reset .../devicetree/bindings/arm/omap/omap.txt | 3 ++- arch/arm/boot/dts/am33xx.dtsi | 2 ++ arch/arm/boot/dts/omap4.dtsi | 3 +++ arch/arm/boot/dts/omap5.dtsi | 2 ++ arch/arm/mach-omap2/omap_hwmod.c | 22 +++++++++++++------- arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 22 ++++++++++---------- arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 6 ++---- arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 4 +--- 8 files changed, 38 insertions(+), 26 deletions(-) -- 1.7.9.5 -- 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
