Hi Brian, On Tue, Nov 26, 2013 at 05:23:38PM -0800, Brian Norris wrote: [..] > > > > If we do resort to a new binding for auto-buswidth, it should be a > > generic one that all NAND drivers can use. Why do we need yet another binding to describe something that's completely discoverable? I'm working on *removing* any need to set the bus width, either from the driver or from the DT, so I see this patch as step backwards. Can anyone help me understand if there's *any* valid use case where we want to specify a-priori the bus width, considering it's completely discoverable at run-time? -- Ezequiel García, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
