From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Peter Tyser <ptyser@xes-inc.com>
Cc: linux-kernel@vger.kernel.org, Alek Du <alek.du@intel.com>,
Samuel Ortiz <sameo@linux.intel.com>,
David Brownell <dbrownell@users.sourceforge.net>,
Eric Miao <eric.y.miao@gmail.com>,
Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Joe Perches <joe@perches.com>,
"grant.likely" <grant.likely@secretlab.ca>
Subject: Re: [PATCH 1/3] gpiolib: Add ability to get GPIO pin direction
Date: Mon, 14 Feb 2011 17:08:12 +0000 [thread overview]
Message-ID: <20110214170812.6f54a4bb@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1297698493.965.5475.camel@petert>
> > If a GPIO driver implements get_direction(), it is called in
> > gpio_request() to set the initial direction of the pin accurately.
>
> I see Grant was just added as a GPIO maintainer, so added him on CC.
>
> Anything gating getting these 3 patches being picked up?
We need four states for a gpio pin direction though. A pin can be
- input
- output
- unknown (hardware lacks get functionality and it has not been set by
software yet)
- alt_func (pin is in use for some other purpose)
(and being able to set them alt_func was proposed a while ago and I think
wants revisiting judging by the number of platforms which use gpio, and
in their own arch code are privately handling alt_func stuff)
Alan
next prev parent reply other threads:[~2011-02-14 17:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 19:54 Peter Tyser
2011-01-06 19:54 ` [PATCH 2/3] gpio: pca953x: Implement get_direction() hook Peter Tyser
2011-01-06 23:16 ` David Brownell
2011-01-06 19:54 ` [PATCH 3/3] gpio: Add support for Intel ICHx/3100/Series[56] GPIO Peter Tyser
2011-01-06 23:12 ` David Brownell
2011-02-14 15:48 ` [PATCH 1/3] gpiolib: Add ability to get GPIO pin direction Peter Tyser
2011-02-14 16:02 ` Grant Likely
2011-02-14 19:14 ` Grant Likely
2011-02-14 20:01 ` Peter Tyser
2011-02-14 17:08 ` Alan Cox [this message]
2011-02-14 17:26 ` Grant Likely
2011-02-14 17:39 ` Mark Brown
2011-02-14 17:45 ` Peter Tyser
2011-02-14 18:04 ` Grant Likely
2011-02-14 18:46 ` Peter Tyser
2011-02-14 19:35 ` Alan Cox
2011-02-14 23:35 ` Peter Tyser
2011-02-15 11:42 ` Alan Cox
2011-02-15 17:05 ` Peter Tyser
2011-02-15 17:19 ` Alan Cox
2011-02-15 17:49 ` Peter Tyser
2011-02-15 19:41 ` Alan Cox
2011-02-17 8:06 ` Uwe Kleine-König
2011-03-06 7:53 ` Grant Likely
2011-02-15 23:55 ` Mark Brown
2011-03-06 7:49 ` Grant Likely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110214170812.6f54a4bb@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alek.du@intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dbrownell@users.sourceforge.net \
--cc=eric.y.miao@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ptyser@xes-inc.com \
--cc=sameo@linux.intel.com \
--cc=u.kleine-koenig@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®