* Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx> [111026 05:22]: > >>>>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. > >> > >>You do not have to put it in the device tree for that, the device > >>driver can implement this itself if it cares. > > > >??? > > > >The driver is the user of that name, so it has to be populated > >before into the resource during device creation. > > It can be as simple as > > #define FOO_REG_INDEX 0 > #define BAR_REG_INDEX 1 > > but you can use C strings if you want to. Fox pin muxing, we really want to use the actual signal names in the drivers. The define example above would means mapping the defines multiple times depending which packaging you're using. There can be several packages for each SoC, where the pins wired up whichever way. For example, for a serial driver to use UART RX pin, the driver can just request a signal called "uart_tx", which is the actual hardware name for the signal inside the SoC. Using the signal names also makes it easier to make drivers to support the same device IP blocks across multiple SoC as the signal name most likely is the same as what the device IP block is using. Regards, Tony -- 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
