Hi
I have a pincontroller with different pin types
For example pin type A & B. (There are more but 2 is sufficient to
specify here).
Each pin type has its own register programming semantics
So each pin type is associated with its own programming vectors.
Of this lets say pin type A can support gpio funcitonality as well.
I model this as
1) total pins exported to pinctrl subsystem = num pins of type A +
num pins of type B
2) Each pin type is a child node of the pinctrl node in device tree.
3) The starting pin number of each pin type on the pinctroller depends
on the order in which it occurs in the device tree when the pinctrl
driver is parsing the device tree.
4) In this case, if a pintype supports gpio functionality, I could have
informed the pinctrl system of the pin range, based on the run time
determined start pin of that pin type. (This would have involved the use
of the now deprecated pinctrl_add_gpio_range())
5) The current way of notifying the pinctrl system of gpio functionality
is by using the gpio-ranges attribute in the gpio chip device tree node.
But in my case, this would require me to know run time what pin range is
going to correspond to my pin type.
Sample DT node
&pinctrl0: pinctrl@<0xfd110000> {
....
..
pinA: pinA {
pintype = "A";
num-pins = <100>;
#pin-cells = <1>;
};
pinB: pinB {
pintype = "B"
num-pins = <20>;
#pin-cells = <1>;
};
gpio_chip_A: GC_A {
pin-type-parent = <&pinA>;
gpio-controller
#gpio-cells = <2>;
interrupt-controller;
interrupt-cells = <2>;
gpio-ranges = <??????>;
};
/* Sample pin use case */
uart0_pins {
pins = <&pinA 22>, <&pinA 23>;
pins-func = <2>;
uart0_active {
pin-drv = <8>;
pin-pull = <1>;
};
uart0_suspend {
pin-drv = <2>;
pin-pull = <0>;
};
};
}
/* Sample gpio use case */
lcd@0xAb000000 {
gpios = <&gpio_chip_A 33 0>;
....
...
};
In the above example, i could assume since the pin type A occurs first
in order, the gpio-ranges = 0 to 99 for the corresponding. But that
would mean ensuring that your pin type occurs at a certain order in
Device tree.
The pinctrl_add_gpio_range() would have really helped here in specifying
the gpio range at device tree parsing time.
Is there a more elegant option rather then hard coding the order of pin
types.?
Thanks
Hanumant
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, hosted by The Linux Foundation
--
On Fri, May 10, 2013 at 1:51 AM, hanumant <[email protected]> wrote:
> 1) total pins exported to pinctrl subsystem = num pins of type A +
> num pins of type B
>
> 2) Each pin type is a child node of the pinctrl node in device tree.
>
> 3) The starting pin number of each pin type on the pinctroller depends on
> the order in which it occurs in the device tree when the pinctrl driver is
> parsing the device tree.
>
> 4) In this case, if a pintype supports gpio functionality, I could have
> informed the pinctrl system of the pin range, based on the run time
> determined start pin of that pin type. (This would have involved the use of
> the now deprecated pinctrl_add_gpio_range())
>
> 5) The current way of notifying the pinctrl system of gpio functionality is
> by using the gpio-ranges attribute in the gpio chip device tree node. But in
> my case, this would require me to know run time what pin range is going to
> correspond to my pin type.
> In the above example, i could assume since the pin type A occurs first
> in order, the gpio-ranges = 0 to 99 for the corresponding. But that would
> mean ensuring that your pin type occurs at a certain order in Device tree.
(...)
> The pinctrl_add_gpio_range() would have really helped here in specifying the
> gpio range at device tree parsing time.
>
> Is there a more elegant option rather then hard coding the order of pin
> types.?
I think I just cannot follow what you are trying to do or what kind of problem
you are facing, there is something wrong with the concepts or I'm just
stupid :-(
pinctrl_add_gpio_range() is one way to add pins at runtime which
unfortunately has the problem that i refers to the global GPIO number
space, which is something we want to avoid.
Instead we recommend that gpiochip_add_pin_range() from
<linux/gpio.h> is used, which us using numbering relative to the
pin controller and GPIO controller as well, which is nice, since
it removed the reliance on the global GPIO number space.
One way to use the latter function while having pin numbers
be dynamic would be to make sure you are doing a combined
driver, i.e. do not try to artificially split the pinctrl and GPIO drivers
in two files, instanstiate one driver container for all of this
hardware and let that driver control both GPIO and pinctrl. This
way all numbering is transparent between the pinctrl and GPIO
parts of the driver and the driver can use pinctrl_add_gpio_range()
or (better) the device-tree based standard bindings to do this.
See the drivers/pinctrl/pinctrl-abx500.c driver for such a combined
driver (albeit it is not using device tree).
Yours,
Linus Walleij