From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-gpio@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
Jassi Brar <jaswinder.singh@linaro.org>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Subject: [PATCH 5/5] pinctrl: uniphier: Fix Pro5 SD pin-mux setting
Date: Tue, 9 Jul 2019 19:29:16 +0900 [thread overview]
Message-ID: <1562668156-12927-6-git-send-email-hayashi.kunihiko@socionext.com> (raw)
In-Reply-To: <1562668156-12927-1-git-send-email-hayashi.kunihiko@socionext.com>
SD uses the following pins starting from 247:
SDCD, SDWP, SDVOLC, SDCLK, SDCMD, SDDAT{0,1,2,3}
Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
---
drivers/pinctrl/uniphier/pinctrl-uniphier-pro5.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/uniphier/pinctrl-uniphier-pro5.c b/drivers/pinctrl/uniphier/pinctrl-uniphier-pro5.c
index 577f12e..22ce0a5 100644
--- a/drivers/pinctrl/uniphier/pinctrl-uniphier-pro5.c
+++ b/drivers/pinctrl/uniphier/pinctrl-uniphier-pro5.c
@@ -807,7 +807,7 @@ static const unsigned nand_pins[] = {19, 20, 21, 22, 23, 24, 25, 28, 29, 30,
static const int nand_muxvals[] = {0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0};
static const unsigned nand_cs1_pins[] = {26, 27};
static const int nand_cs1_muxvals[] = {0, 0};
-static const unsigned sd_pins[] = {250, 251, 252, 253, 254, 255, 256, 257, 258};
+static const unsigned sd_pins[] = {247, 248, 249, 250, 251, 252, 253, 254, 255};
static const int sd_muxvals[] = {0, 0, 0, 0, 0, 0, 0, 0, 0};
static const unsigned spi0_pins[] = {120, 121, 122, 123};
static const int spi0_muxvals[] = {0, 0, 0, 0};
--
2.7.4
next prev parent reply other threads:[~2019-07-09 10:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 10:29 [PATCH 0/5] pinctrl: uniphier: Add some improvements and new settings Kunihiko Hayashi
2019-07-09 10:29 ` [PATCH 1/5] pinctrl: uniphier: Separate modem group from UART ctsrts group Kunihiko Hayashi
2019-07-29 13:45 ` Masahiro Yamada
2019-07-30 2:21 ` Kunihiko Hayashi
2019-07-09 10:29 ` [PATCH 2/5] pinctrl: uniphier: Add another audio I/O pin-mux settings for LD20 Kunihiko Hayashi
2019-07-29 13:44 ` Masahiro Yamada
2019-07-30 2:22 ` Kunihiko Hayashi
2019-07-09 10:29 ` [PATCH 3/5] pinctrl: uniphier: Add 4th LD20 MPEG2-TS input pin-mux setting Kunihiko Hayashi
2019-07-29 13:45 ` Masahiro Yamada
2019-07-09 10:29 ` [PATCH 4/5] pinctrl: uniphier: Add Pro5 PCIe pin-mux settings Kunihiko Hayashi
2019-07-29 13:46 ` Masahiro Yamada
2019-07-30 2:22 ` Kunihiko Hayashi
2019-07-09 10:29 ` Kunihiko Hayashi [this message]
2019-07-29 13:46 ` [PATCH 5/5] pinctrl: uniphier: Fix Pro5 SD pin-mux setting Masahiro Yamada
2019-07-28 23:07 ` [PATCH 0/5] pinctrl: uniphier: Add some improvements and new settings 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=1562668156-12927-6-git-send-email-hayashi.kunihiko@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=jaswinder.singh@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu@linaro.org \
--cc=yamada.masahiro@socionext.com \
/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).