[RFC 0/6] pinctrl: samsung: Remove static platform-specific data
swarren at wwwdotorg.org
Mon Sep 24 13:34:12 EDT 2012
On 09/21/2012 01:31 PM, Tomasz Figa wrote:
> On Friday 21 of September 2012 12:40:35 Stephen Warren wrote:
>> On 09/20/2012 02:53 AM, Tomasz Figa wrote:
>>> This RFC series is a work on replacing static platform-specific data in
>>> pinctrl-samsung driver with data dynamically parsed from device tree.
>>> It aims at reducing the SoC-specific part of the driver and thus the
>>> amount of modifications to driver sources when adding support for next
>>> SoCs (like Exynos4x12).
>>> Furthermore, moving definitions of pin banks to device tree will allow
>>> to simplify GPIO and GEINT specification to a format similar to used
>>> previously by gpiolib-based implementation, using a phandle to the bank
>>> and pin index inside the bank, e.g.
>>> gpios = <&gpa1 4 0>;
>>> interrupt-parent = <&gpa1>;
>>> interrupts = <4 0>;
>> I don't think those two are correlated; the GPIO specifier format could
>> just as easily be <bank pin> irrespective of whether the pinctrl driver
>> contains SoC-specific tables or not.
> Correct me if I'm wrong, but each bank needs to have its own subnode to be
> able to address pins like this. That was the starting point of the whole
> series and the idea that if all the banks (which are SoC-specific) have to
> be defined anyway, maybe it wouldn't be too bad to put all the SoC-specific
> parameters there too.
If you write your own custom .xlate function, I think you can do
basically anything you want; all of the following are possible, I believe:
a) Single DT node covering all banks, with GPIO specifier being <n>
where n is some linearized GPIO ID across all banks.
b) Single DT node covering all banks, with GPIO specifier being <b n>
where b is the bank number, and n is the GPIO ID within the bank (xlate
would presumably calculate "(b * MAX_GPIOS_PER_BANK) + n" and up with
the same data as in (a) above.
c) One DT node per bank, one gpio_chip registered per node, with the
GPIO specifier being <n> where n is the GPIO ID within the bank the
phandle points at.
d) One DT node per bank, all contained within a single parent DT node,
one gpio_chip registered per node (one for each bank node, and one for
the parent node), with GPIO phandles pointing at the parent node, with
GPIO specifier in the format of either (a) or (b) above, and the
top-level node's .xlate returning a different gpio_chip (for one of the
child bank-specific nodes) rather than the parent chip. At least, IIRC,
Grant Likely was going to extend a gpio_chip's .xlate to be able to
return a different chip; I'm not sure if that was implemented yet or not.
More information about the linux-arm-kernel