From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linus.walleij@linaro.org
Cc: linux-sh@vger.kernel.org, laurent.pinchart@ideasonboard.com,
linux-gpio@vger.kernel.org
Subject: [PATCH v3 2/3] sh-pfc: r8a7790: remove non-existing GPIO pins
Date: Fri, 26 Jun 2015 01:42:04 +0300 [thread overview]
Message-ID: <14360647.s1qTxSuam8@wasted.cogentembedded.com> (raw)
In-Reply-To: <1460630.GxHT4lRd7u@wasted.cogentembedded.com>
From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
GPIO banks 1 and 2 are missing pins 30 and 31. Remove them.
Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
---
Changes in version 2:
- renamed the patch.
drivers/pinctrl/sh-pfc/pfc-r8a7790.c | 21 +++++++++++++++++++--
1 file changed, 19 insertions(+), 2 deletions(-)
Index: linux-pinctrl/drivers/pinctrl/sh-pfc/pfc-r8a7790.c
===================================================================
--- linux-pinctrl.orig/drivers/pinctrl/sh-pfc/pfc-r8a7790.c
+++ linux-pinctrl/drivers/pinctrl/sh-pfc/pfc-r8a7790.c
@@ -27,10 +27,27 @@
#include "core.h"
#include "sh_pfc.h"
+#define PORT_GP_30(bank, fn, sfx) \
+ PORT_GP_1(bank, 0, fn, sfx), PORT_GP_1(bank, 1, fn, sfx), \
+ PORT_GP_1(bank, 2, fn, sfx), PORT_GP_1(bank, 3, fn, sfx), \
+ PORT_GP_1(bank, 4, fn, sfx), PORT_GP_1(bank, 5, fn, sfx), \
+ PORT_GP_1(bank, 6, fn, sfx), PORT_GP_1(bank, 7, fn, sfx), \
+ PORT_GP_1(bank, 8, fn, sfx), PORT_GP_1(bank, 9, fn, sfx), \
+ PORT_GP_1(bank, 10, fn, sfx), PORT_GP_1(bank, 11, fn, sfx), \
+ PORT_GP_1(bank, 12, fn, sfx), PORT_GP_1(bank, 13, fn, sfx), \
+ PORT_GP_1(bank, 14, fn, sfx), PORT_GP_1(bank, 15, fn, sfx), \
+ PORT_GP_1(bank, 16, fn, sfx), PORT_GP_1(bank, 17, fn, sfx), \
+ PORT_GP_1(bank, 18, fn, sfx), PORT_GP_1(bank, 19, fn, sfx), \
+ PORT_GP_1(bank, 20, fn, sfx), PORT_GP_1(bank, 21, fn, sfx), \
+ PORT_GP_1(bank, 22, fn, sfx), PORT_GP_1(bank, 23, fn, sfx), \
+ PORT_GP_1(bank, 24, fn, sfx), PORT_GP_1(bank, 25, fn, sfx), \
+ PORT_GP_1(bank, 26, fn, sfx), PORT_GP_1(bank, 27, fn, sfx), \
+ PORT_GP_1(bank, 28, fn, sfx), PORT_GP_1(bank, 29, fn, sfx)
+
#define CPU_ALL_PORT(fn, sfx) \
PORT_GP_32(0, fn, sfx), \
- PORT_GP_32(1, fn, sfx), \
- PORT_GP_32(2, fn, sfx), \
+ PORT_GP_30(1, fn, sfx), \
+ PORT_GP_30(2, fn, sfx), \
PORT_GP_32(3, fn, sfx), \
PORT_GP_32(4, fn, sfx), \
PORT_GP_32(5, fn, sfx)
next prev parent reply other threads:[~2015-06-25 22:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 22:39 [PATCH v3 0/3] Remove non-existing GPIO pins for R8A7790/1 Sergei Shtylyov
2015-06-25 22:40 ` [PATCH v3 1/3] sh-pfc: fix sparse GPIOs for R-Car SoCs Sergei Shtylyov
2015-07-07 17:39 ` Laurent Pinchart
2015-07-08 7:37 ` Geert Uytterhoeven
2015-07-13 20:29 ` Linus Walleij
2015-06-25 22:42 ` Sergei Shtylyov [this message]
2015-07-13 20:30 ` [PATCH v3 2/3] sh-pfc: r8a7790: remove non-existing GPIO pins Linus Walleij
2015-06-25 22:43 ` [PATCH v3 3/3] sh-pfc: r8a7791: " Sergei Shtylyov
2015-07-08 7:38 ` Geert Uytterhoeven
2015-07-13 20:32 ` Linus Walleij
2015-06-26 20:51 ` [PATCH v3 0/3] Remove non-existing GPIO pins for R8A7790/1 Sergei Shtylyov
2015-06-29 10:43 ` Linus Walleij
2015-07-03 23:29 ` Laurent Pinchart
2015-07-07 20:58 ` 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=14360647.s1qTxSuam8@wasted.cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).