On Tue, Sep 25, 2012 at 03:45:50PM +0800, Shawn Guo wrote: > On Tue, Sep 25, 2012 at 09:38:08AM +0200, Sascha Hauer wrote: > > So you want to make the code conform to the common spec which has > > bus-width as a required property. Is this really worth it to add an > > incompatible change to our devicetrees? > > > I do want to have our implementation conform to common spec. At the > current stage devicetrees are not stable anyway, so we should make > them right as much as possible before they start getting maintained > separately from kernel tree, where we will be asked to maintain > devicetree compatibility a lot harder. Ok, how about this: - I add a bus-width = <4> property to all i.MX dtsi files - we merge the patch adding bus-width as an optional property - Make the bus-width option mandatory in the next step. This way we can merge the mmc related patches through the mmc tree and the dts changes through arm-soc. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
