On 05/03/2012 09:27 AM, Tony Lindgren wrote: > Hi, > > * Jean-Christophe PLAGNIOL-VILLARD <plagnioj@xxxxxxxxxxxx> [120503 00:16]: >> >> I really like it >> >> I was working on something simillar >> >> but can we split the group management so we can use it on other >> bindings > > Hmm I'm not sure I follow on the group management splitting, can you specify > what you have in mind here? > > If you mean moving more things into pinctrl fwk, then yeah I'd assume that > will happen eventually and drivers like this will end up becoming more minimal. Jean-Christophe, forgive me if I'm putting words in your mouth, but I assume the following is what you mean: There are two pieces of data required by the pinctrl subsystem: a) The set of pins, functions, and groups that exist. b) The specific function to select for each pin/group on a given board. Item (a) can be represented in the pinctrl driver (e.g. as in the Tegra driver), or can be represented in device tree in order to avoid large tables in the driver. Item (b) has to be represented in device tree, since the whole point is that it's board-specific. For all DT bindings I've seen that choose to represent (a) in the DT rather than in the driver, the DT represents (b) directly, and (a) is implicitly extracted/created based on (a). When I was first thinking about DT bindings for pinctrl, I had hoped that even if (a) was represented in DT, the DT nodes/properties for (a) and (b) would be entirely separate, so that the binding for (b) could be completely common across all SoCs, even though the binding for (a) would perhaps be different across SoCs (if it existed at all). So, perhaps Jean-Christophe is talking about splitting up (a) and (b) in device tree? Or perhaps Jean-Christophe only refers to the code that creates the group and function definitions from (b), and not the actual DT binding itself? -- 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
