2011/10/14 Chanho Park :
> A gpio base number of gpio_range0 is 0 and pin base number is also 0.
> Converting gpio-pin number is no problem about the gpio_range0.
> A gpio base number of gpio_range1 is 32 but pin base number is 40(not 32).
Aha, I understand now, sorry I'm too slow in the head. :-
2011/10/13 Linus Walleij :
> On Thu, Oct 13, 2011 at 2:55 AM, Chanho Park wrote:
>
>> Some gpio-ranges doesn't match with pin numbers.
>> For example, gpio_range_b starts gpio 48.
>> However, a pin base number of gpio_range_b is 96. It isn't same with gpio
>> base.
>> A pinctrl driver must know t
On Thu, Oct 13, 2011 at 5:18 AM, Grant Likely wrote:
> Nit: put the changelog above the s-o-b lines so it will appear in the
> linux commit log.
OK I'll collect all of them and stash them into it for v10
>> +The GPIO drivers may want to perform operations of various types on the same
>> +physic
On Thu, Oct 13, 2011 at 2:55 AM, Chanho Park wrote:
> Some gpio-ranges doesn't match with pin numbers.
> For example, gpio_range_b starts gpio 48.
> However, a pin base number of gpio_range_b is 96. It isn't same with gpio
> base.
> A pinctrl driver must know this pin_space-gpio_range mappings.
On Mon, Oct 03, 2011 at 10:17:42AM +0200, Linus Walleij wrote:
> From: Linus Walleij
>
> This creates a subsystem for handling of pin control devices.
> These are devices that control different aspects of package
> pins.
>
> Currently it handles pinmuxing, i.e. assigning electronic
> functions t
> +Interaction with the GPIO subsystem
> +===
> +
> +The GPIO drivers may want to perform operations of various types on the same
> +physical pins that are also registered as GPIO pins.
> +
> +Since the pin controller subsystem have its pinspace local to the pin
> +c
On Mon, Oct 10, 2011 at 2:30 PM, Shawn Guo wrote:
>> +The example 8x8 PGA package above will have pin numbers 0 thru 63 assigned
>> to
>> +its physical pins. It will name the pins { A1, A2, A3 ... H6, H7, H8 } using
>> +pinctrl_register_pins_[sparse|dense]() and a suitable data set as shown
>
>
On Mon, Oct 10, 2011 at 10:23:53AM +0200, Linus Walleij wrote:
> On Sun, Oct 9, 2011 at 11:36 AM, Shawn Guo wrote:
>
> >> + * @hog_on_boot: if this is set to true, the regulator subsystem will
> >> itself
> > ^
> > s/regulator/pinmux?
>
> Y
On Sun, Oct 9, 2011 at 11:36 AM, Shawn Guo wrote:
>> + * @hog_on_boot: if this is set to true, the regulator subsystem will itself
> ^
> s/regulator/pinmux?
Yep!
>> +#endif /* !CONFIG_PINCTRL */
>
> s/!CONFIG_PINCTRL/CONFIG_PINMUX?
Yep!
F
On Mon, Oct 03, 2011 at 10:17:42AM +0200, Linus Walleij wrote:
[...]
> diff --git a/include/linux/pinctrl/machine.h b/include/linux/pinctrl/machine.h
> new file mode 100644
> index 000..2cd4033
> --- /dev/null
> +++ b/include/linux/pinctrl/machine.h
> @@ -0,0 +1,107 @@
> +/*
> + * Machine inter
10 matches
Mail list logo
