From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Cc: devicetree-discuss@lists.ozlabs.org,
Linus Walleij <linus.walleij@linaro.org>,
Magnus Damm <damm@opensource.se>
Subject: [RFC/PATCH 1/2] gpio-rcar: Make the platform data gpio_base field signed
Date: Fri, 10 May 2013 16:48:36 +0200 [thread overview]
Message-ID: <1368197317-13169-2-git-send-email-laurent.pinchart@ideasonboard.com> (raw)
In-Reply-To: <1368197317-13169-1-git-send-email-laurent.pinchart@ideasonboard.com>
The gpio_base field is used to specify the desired GPIO base for the
GPIO controller. The GPIO core can automatically allocate a GPIO number
range when the base is set to -1. To make this possible, make the field
signed.
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
---
include/linux/platform_data/gpio-rcar.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/platform_data/gpio-rcar.h b/include/linux/platform_data/gpio-rcar.h
index cc472f6..fb2c718 100644
--- a/include/linux/platform_data/gpio-rcar.h
+++ b/include/linux/platform_data/gpio-rcar.h
@@ -17,7 +17,7 @@
#define __GPIO_RCAR_H__
struct gpio_rcar_config {
- unsigned int gpio_base;
+ int gpio_base;
unsigned int irq_base;
unsigned int number_of_pins;
const char *pctl_name;
--
1.8.1.5
next prev parent reply other threads:[~2013-05-10 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 14:48 [RFC/PATCH 0/2] R-Car GPIO DT bindings Laurent Pinchart
2013-05-10 14:48 ` Laurent Pinchart [this message]
2013-05-15 2:00 ` [RFC/PATCH 1/2] gpio-rcar: Make the platform data gpio_base field signed Simon Horman
2013-05-20 18:08 ` Linus Walleij
2013-05-10 14:48 ` [RFC/PATCH 2/2] gpio-rcar: Add DT support Laurent Pinchart
2013-05-17 12:22 ` Guennadi Liakhovetski
2013-05-18 6:30 ` Laurent Pinchart
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=1368197317-13169-2-git-send-email-laurent.pinchart@ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=damm@opensource.se \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linus.walleij@linaro.org \
--cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox