From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 2/5] pinctrl: SPEAr1310: Fix pin numbers for clcd_high_res
Date: Tue, 8 May 2012 09:10:26 +0530 [thread overview]
Message-ID: <3c578d3031b2b5ec6ecd05db65a925cb13e66ed0.1336448307.git.viresh.kumar@st.com> (raw)
In-Reply-To: <cover.1336448307.git.viresh.kumar@st.com>
Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
---
drivers/pinctrl/spear/pinctrl-spear1310.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/pinctrl/spear/pinctrl-spear1310.c b/drivers/pinctrl/spear/pinctrl-spear1310.c
index 12b094d..fff168b 100644
--- a/drivers/pinctrl/spear/pinctrl-spear1310.c
+++ b/drivers/pinctrl/spear/pinctrl-spear1310.c
@@ -437,7 +437,7 @@ static struct spear_pingroup clcd_pingroup = {
};
static const unsigned clcd_high_res_pins[] = { 30, 31, 32, 33, 34, 35, 36, 37,
- 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52 };
+ 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53 };
static struct spear_muxreg clcd_high_res_muxreg[] = {
{
.reg = PAD_FUNCTION_EN_1,
--
1.7.9
next prev parent reply other threads:[~2012-05-08 3:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 3:40 [PATCH V3 0/5] pinctrl: SPEAr Updates Viresh Kumar
2012-05-08 3:40 ` [PATCH V3 1/5] pinctrl: SPEAr: Don't set all non muxreg bits on pinctrl_disable Viresh Kumar
2012-05-08 3:40 ` Viresh Kumar [this message]
2012-05-08 3:40 ` [PATCH V3 3/5] pinctrl: SPEAr: Add plgpio driver Viresh Kumar
2012-05-08 3:40 ` [PATCH V3 4/5] pinctrl: SPEAr: Add gpio ranges support Viresh Kumar
2012-05-08 3:40 ` [PATCH V3 5/5] SPEAr: Add plgpio node in device tree dtsi files Viresh Kumar
2012-05-09 12:56 ` [PATCH V3 0/5] pinctrl: SPEAr Updates 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=3c578d3031b2b5ec6ecd05db65a925cb13e66ed0.1336448307.git.viresh.kumar@st.com \
--to=viresh.kumar@st.com \
--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).