From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: NeilBrown <neilb@suse.de>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [GIT PULL] GPIO changes for v3.6
Date: Tue, 31 Jul 2012 14:35:28 +0100 [thread overview]
Message-ID: <20120731133527.GH4468@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120731144724.5ef139fa@notabene.brown>
On Tue, Jul 31, 2012 at 02:47:24PM +1000, NeilBrown wrote:
> ... though it occurs to me that it is possible that the GPIO number might not
> be allocated until something else has been probed, so a -ve gpio number could
> mean "there is no such gpio" or it could mean "gpio has not been allocated
> yet". I wonder if that should be allowed and where it should be handled.
If there's logic to do things like that I'd
> I'd really like to see gpios be requested by name ... anyone know if there
> are any plans along that line?
I've not noticed anyone doing much substantial work on GPIO recently.
next prev parent reply other threads:[~2012-07-31 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 22:48 [GIT PULL] GPIO changes for v3.6 Linus Walleij
2012-07-26 20:58 ` Linus Torvalds
2012-07-27 22:37 ` Linus Walleij
2012-07-28 15:34 ` Shawn Guo
2012-07-30 6:57 ` NeilBrown
2012-07-30 13:36 ` Mark Brown
2012-07-31 4:47 ` NeilBrown
2012-07-31 13:35 ` Mark Brown [this message]
2012-08-04 22:03 ` Linus Walleij
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=20120731133527.GH4468@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.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