On Fri, Jun 24, 2011 at 5:51 AM, Mike Frysinger wrote:
> can you guys start cc-ing uclinux-dist-de...@blackfin.uclinux.org on
> future pinmux discussions?
OK!
Please refer to the LKML thread:
[PATCH 1/2] drivers: create a pinmux subsystem v3
For now, I'll include blackfin for the v4 post.
> we
On Thu, Jun 16, 2011 at 15:12, Stephen Warren wrote:
> Linus Walleij wrote at Thursday, June 16, 2011 9:07 AM:
>> On Wed, Jun 15, 2011 at 11:48 PM, Stephen Warren wrote:
>> > Some more thoughts on pinmux:
can you guys start cc-ing uclinux-dist-de...@blackfin.uclinux.org on
future pinmux discussion
Linus Walleij wrote at Thursday, June 16, 2011 9:07 AM:
> On Wed, Jun 15, 2011 at 11:48 PM, Stephen Warren wrote:
>
> > Some more thoughts on pinmux:
>
> Thanks!
>
> Keep it coming until you get tired of me :-)
>
> > == GPIO/pinmux API interactions
> >
> > I'd like to understand how the gp
On Wed, Jun 15, 2011 at 11:48 PM, Stephen Warren wrote:
> Some more thoughts on pinmux:
Thanks!
Keep it coming until you get tired of me :-)
> == GPIO/pinmux API interactions
>
> I'd like to understand how the gpio and pinmux subsystems are intended
> to interact.
Mainly I'd like Gran
Linus (W),
Some more thoughts on pinmux:
== GPIO/pinmux API interactions
I'd like to understand how the gpio and pinmux subsystems are intended
to interact.
Quoting from Documentation/gpio.txt:
Note that requesting a GPIO does NOT cause it to be configured in any
way; it just marks
