On 16:49-20130314, Jon Hunter wrote: > > On 03/14/2013 03:58 PM, Nishanth Menon wrote: > > OMAP4430 and 4460 have different OPP definitions. So, create an SoC > > variant dtsi file for 4460 and move the OPP definitions to it. > > FYI, I had to create a similar file for PMU [1]. However, I called it > omap4460.dtsi and not omap446x.dtsi as there is only one omap446x Hmm, guess I was paranoid about marketing folks spinning off another omap446x variant out into the market. Since it is not yet done, nor known if they will ever do it, am OK with 4460 convention. > device. That should go into to v3.10 and so may be worth basing this on > top. I do like your omap4-panda-common.dtsi that is a nice clean-up. Thanks on the tip - Sounds good, since this series is based on DT, I will base my changes on top of for_3.10 branch. > > Cheers > Jon > > [1] > http://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git/commit/?h=for_3.10/dts&id=5e64b6b1137a54f353528d6da60071c1ef0043ba -- Regards, Nishanth Menon -- 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
