On 10/25/2011 12:29 PM, Segher Boessenkool wrote:
+ compatible = "ti,mcasp";
+ reg =<0 0x10 0x10>,<0 0x20 0x10>,
+ <1 0x10 0x10>,<1 0x20 0x10>;
+ reg-names = "mpu", "dat",
+ "dma", "dma_dat";
Hmm for some systems looks like this can also solve how to pass the
mux signal names cleanly from DT.
What problem does any of this solve? The device binding for the
"mcasp" device will have to describe the possible "reg-names", and
what those mean; but the binding already has to describe its "reg"
property anyway.
What this solve is the ability to use the platform_get_resource_byname
directly to retrieve the proper register base address. The binding is
just a text description that the driver will not be able to use
directly. It will have to get the resource using an abstract index.
It thus removes a level of indirection that is error prone and useless
most of the time.
Benoit
--
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
