[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbJbUefH+Q0GMp+_4FhV5RqQ+KHrGnJLR6jZSNR16NbSw@mail.gmail.com>
Date: Fri, 21 Oct 2011 14:28:25 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc: Barry Song <21cnbao@...il.com>,
Shawn Guo <shawn.guo@...escale.com>,
Linus Walleij <linus.walleij@...ricsson.com>,
linux-kernel@...r.kernel.org, Stephen Warren <swarren@...dia.com>,
Linaro Dev <linaro-dev@...ts.linaro.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
David Brown <davidb@...eaurora.org>,
Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [PATCH 2/2] pinctrl: add a generic control interface
On Thu, Oct 20, 2011 at 5:42 PM, Mark Brown
<broonie@...nsource.wolfsonmicro.com> wrote:
> On Thu, Oct 20, 2011 at 04:43:30PM +0200, Linus Walleij wrote:
>> In Ux500 we model our power domain switches as regulators,
>> does such a property even belong in pin control? Is there
>> one power domain switch per pin you mean, or a power switch
>> for a whole group of pins?
>
> This isn't an on/off control and in this cae it's per pin.
If this is a binary output pin, I suspect that
I suspect that what you call "off" is actually implemeted as
in this figure:
http://upload.wikimedia.org/wikipedia/commons/c/c0/Tristate_buffer.svg
In which case:
PIN_CONFIG_DRIVE_PUSH_PULL
PIN_CONFIG_DRIVE_OFF
or PIN_CONFIG_BIAS_HIGH_IMPEDANCE
Is a config pair which most often correspond to
exactly what you're doing here, albeit with a different
terminology.
However, if it is an *analog* pin....
Then it's something else.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists