From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] gpiolib: add gpio_lookup_chip() to get chip information for gpio
Date: Fri, 8 Jan 2010 06:32:28 +0000 [thread overview]
Message-ID: <1262932348-2888-2-git-send-email-ben-linux@fluff.org> (raw)
In-Reply-To: <1262932348-2888-1-git-send-email-ben-linux@fluff.org>
Add a call to get the 'struct gpio_chip' pointer for a given gpio, so
that core implementations which want to use gpiolib gpio numbering for
things like mux configuration can get back to the gpio_chip that they
registered without having to have their own list of gpio.
This is especially useful for the Samsung S3C64XX series where the GPIO
bank sizes can vary from 32 down to 3, making it difficult to store an
array to convert a number to chip.
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
---
drivers/gpio/gpiolib.c | 26 ++++++++++++++++++++++++++
include/asm-generic/gpio.h | 2 ++
2 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index a25ad28..d748600 100644
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpiolib.c
@@ -120,6 +120,32 @@ static inline struct gpio_chip *gpio_to_chip(unsigned gpio)
return gpio_desc[gpio].chip;
}
+/**
+ * gpio_lookup_chip - return the chip for a given gpio
+ * @gpio: The GPIO number to lookup
+ *
+ * Returns NULL if the GPIO chip is not valid or there is no chip registered
+ * for that GPIO. This call is available for core code to turn a GPIO number
+ * into a chip so that further information can be looked up.
+ *
+ * This call makes no guarantees about the actuall gpio_chip's state, or
+ * whether the @gpio itself is requested.
+ */
+struct gpio_chip *gpio_lookup_chip(unsigned gpio)
+{
+ struct gpio_chip *chip;
+ unsigned long flags;
+
+ if (!gpio_is_valid(gpio))
+ return NULL;
+
+ spin_lock_irqsave(&gpio_lock, flags);
+ chip = gpio_to_chip(gpio);
+ spin_unlock_irqrestore(&gpio_lock, flags);
+
+ return chip;
+}
+
/* dynamic allocation of GPIOs, e.g. on a hotplugged device */
static int gpiochip_find_base(int ngpio)
{
diff --git a/include/asm-generic/gpio.h b/include/asm-generic/gpio.h
index 485eeb6..34b3276 100644
--- a/include/asm-generic/gpio.h
+++ b/include/asm-generic/gpio.h
@@ -103,6 +103,8 @@ struct gpio_chip {
unsigned exported:1;
};
+extern struct gpio_chip *gpio_lookup_chip(unsigned gpio);
+
extern const char *gpiochip_is_requested(struct gpio_chip *chip,
unsigned offset);
extern int __must_check gpiochip_reserve(int start, int ngpio);
--
1.6.0.4
next prev parent reply other threads:[~2010-01-08 6:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 6:32 GPIO update to allow code to get at gpio_chip Ben Dooks
2010-01-08 6:32 ` Ben Dooks [this message]
2010-01-08 7:30 ` [PATCH] gpiolib: add gpio_lookup_chip() to get chip information for gpio Eric Miao
2010-01-08 8:28 ` Ben Dooks
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-2-git-send-email-ben-linux@fluff.org \
--to=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).