Dear Ezequiel Garcia, On Tue, 27 Aug 2013 05:36:04 -0300, Ezequiel Garcia wrote: > > Is there a reason we're going this route over adding a new compatible > > string? > > Well, it seemed to me that this register splitting was more device-treeish: > it prevents you from fixing your driver, adding a new compatible-string, > and rebuilding a kernel each time a new SoC appears with a different offset > between registers. I don't think encoding register offsets in the DT is a good idea. The compatible string is here to identify different revisions/versions of the same hardware block, and the driver should abstract out the details. Otherwise, you'll start encoding bit numbers, mask values, and other crazy things in the Device Tree. Best regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. 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
