From: Ben Dooks <ben-linux@fluff.org>
To: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: GPIO update to allow code to get at gpio_chip
Date: Fri, 8 Jan 2010 06:32:27 +0000 [thread overview]
Message-ID: <1262932348-2888-1-git-send-email-ben-linux@fluff.org> (raw)
Allowing gpiolib implementations to get at the gpio_chip from the
gpio number is useful to allow gpiolib gpio numbering to be used
for other gpio purposes such as changing pin configuration.
The following patch exports this information. A patch showing the
reason for my wanting this can be supplied on request.
WARNING: multiple messages have this Message-ID (diff)
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: GPIO update to allow code to get at gpio_chip
Date: Fri, 8 Jan 2010 06:32:27 +0000 [thread overview]
Message-ID: <1262932348-2888-1-git-send-email-ben-linux@fluff.org> (raw)
Allowing gpiolib implementations to get at the gpio_chip from the
gpio number is useful to allow gpiolib gpio numbering to be used
for other gpio purposes such as changing pin configuration.
The following patch exports this information. A patch showing the
reason for my wanting this can be supplied on request.
next reply other threads:[~2010-01-08 6:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 6:32 Ben Dooks [this message]
2010-01-08 6:32 ` GPIO update to allow code to get at gpio_chip Ben Dooks
2010-01-08 6:32 ` [PATCH] gpiolib: add gpio_lookup_chip() to get chip information for gpio Ben Dooks
2010-01-08 6:32 ` Ben Dooks
2010-01-08 7:30 ` Eric Miao
2010-01-08 7:30 ` Eric Miao
2010-01-08 7:30 ` Eric Miao
2010-01-08 8:28 ` Ben Dooks
2010-01-08 8:28 ` Ben Dooks
2010-01-21 6:12 ` Andrew Morton
2010-01-21 6:12 ` Andrew Morton
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=1262932348-2888-1-git-send-email-ben-linux@fluff.org \
--to=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.