question: pin mux & gpio

question: pin mux & gpio

[David Cohen]

Hi,

I've got a question WRT pin muxing.
gpio-intel-mid registers are responsible to set alternative functions
to some pins. Despite pin mux is not directly related to gpio in
general, in this case it is.

Is there any other gpio driver doing this same task? Or maybe
suggestion about how to handle it?

Br, David Cohen

Re: question: pin mux & gpio

[Linus Walleij]

On Wed, Oct 23, 2013 at 6:28 PM, David Cohen
<david.a.cohen@linux.intel.com> wrote:

> I've got a question WRT pin muxing.
> gpio-intel-mid registers are responsible to set alternative functions
> to some pins. Despite pin mux is not directly related to gpio in
> general, in this case it is.

I know this use case.

> Is there any other gpio driver doing this same task? Or maybe
> suggestion about how to handle it?

First read Documentation/pinctrl.txt :-)

Move the driver to drivers/pinctrl/pinctrl-intel-mid.c in the next
merge window, and add pin control interfaces in the style of the
other combined pin control+GPIO drivers there. Keeping one state
struct but exposing interfaces to both subsystems is perfectly
acceptable. Use GPIO ranges to cross-reference GPIO lines
to pins.

Yours,
Linus Walleij

Re: question: pin mux & gpio

[David Cohen]

Hi Linus,

On 10/29/2013 10:03 AM, Linus Walleij wrote:
> On Wed, Oct 23, 2013 at 6:28 PM, David Cohen
> <david.a.cohen@linux.intel.com> wrote:
>
>> I've got a question WRT pin muxing.
>> gpio-intel-mid registers are responsible to set alternative functions
>> to some pins. Despite pin mux is not directly related to gpio in
>> general, in this case it is.
>
> I know this use case.
>
>> Is there any other gpio driver doing this same task? Or maybe
>> suggestion about how to handle it?
>
> First read Documentation/pinctrl.txt :-)
>
> Move the driver to drivers/pinctrl/pinctrl-intel-mid.c in the next
> merge window, and add pin control interfaces in the style of the
> other combined pin control+GPIO drivers there. Keeping one state
> struct but exposing interfaces to both subsystems is perfectly
> acceptable. Use GPIO ranges to cross-reference GPIO lines
> to pins.

Thanks. I'll work on that change.

Br, David Cohen