[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <A6EC110C-1712-4AC7-B828-D7BB08278996@opensource.wolfsonmicro.com>
Date: Sat, 27 Feb 2010 17:20:58 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: David Brownell <david-b@...bell.net>
Cc: Ben Gardner <gardner.ben@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andres Salomon <dilinger@...labora.co.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Jani Nikula <ext-jani.1.nikula@...ia.com>
Subject: Re: [PATCH 1/3] gpiolib: add gpio_set_direction()
On 27 Feb 2010, at 16:24, David Brownell <david-b@...bell.net> wrote:
> On Saturday 27 February 2010, Mark Brown wrote:
>>> "none" ... since it's not even a GPIO, why would it show
>>> up through the GPIO subsystem???
>>
>> I suspect this is intended to be tristated, which might be useful
>> to add.
>
> That's what "input" means, as a rule: no output driver
> is active with a GPIO configured as "iput". "Tristate"
> is an option that's relevant for outputs ... low, high,
> or not-driven.
Indeed, but some devices do implement a distinct tristate state for
input mode pins (disabling interrupt generation logic and so on for
example).
--
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