From: Dong Aisheng <aisheng.dong@nxp.com>
To: linux-gpio@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, linus.walleij@linaro.org,
shawnguo@kernel.org, aisheng.dong@nxp.com, dongas86@gmail.com,
stefan@agner.ch, ping.bai@nxp.com, fugang.duan@nxp.com,
kernel@pengutronix.de
Subject: [PATCH V4 RESEND 2/6] pinctrl: imx: switch to use the generic pinmux property
Date: Tue, 25 Jul 2017 21:41:52 +0800 [thread overview]
Message-ID: <1500990116-3620-3-git-send-email-aisheng.dong@nxp.com> (raw)
In-Reply-To: <1500990116-3620-1-git-send-email-aisheng.dong@nxp.com>
The generic pinmux property seems to be more suitable for IMX.
So we change to use 'pinmux' instead of 'pins'.
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: Bai Ping <ping.bai@nxp.com>
Acked-by: Shawn Guo <shawnguo@kernel.org>
Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com>
---
ChangeLog:
* new patch
---
drivers/pinctrl/freescale/pinctrl-imx.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/pinctrl/freescale/pinctrl-imx.c b/drivers/pinctrl/freescale/pinctrl-imx.c
index 72aca75..fc1ba3c 100644
--- a/drivers/pinctrl/freescale/pinctrl-imx.c
+++ b/drivers/pinctrl/freescale/pinctrl-imx.c
@@ -563,14 +563,14 @@ static int imx_pinctrl_parse_groups(struct device_node *np,
* do sanity check and calculate pins number
*
* First try legacy 'fsl,pins' property, then fall back to the
- * generic 'pins'.
+ * generic 'pinmux'.
*
- * Note: for generic 'pins' case, there's no CONFIG part in
+ * Note: for generic 'pinmux' case, there's no CONFIG part in
* the binding format.
*/
list = of_get_property(np, "fsl,pins", &size);
if (!list) {
- list = of_get_property(np, "pins", &size);
+ list = of_get_property(np, "pinmux", &size);
if (!list) {
dev_err(info->dev,
"no fsl,pins and pins property in node %s\n",
--
2.7.4
next prev parent reply other threads:[~2017-07-25 13:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 13:41 [PATCH V4 RESEND 0/6] pinctrl: imx: add imx7ulp pinctrl support Dong Aisheng
[not found] ` <1500990116-3620-1-git-send-email-aisheng.dong-3arQi8VN3Tc@public.gmane.org>
2017-07-25 13:41 ` [PATCH V4 RESEND 1/6] dt-bindings: pinctrl: add imx7ulp pinctrl binding doc Dong Aisheng
[not found] ` <1500990116-3620-2-git-send-email-aisheng.dong-3arQi8VN3Tc@public.gmane.org>
2017-08-01 11:50 ` Linus Walleij
2017-07-25 13:41 ` Dong Aisheng [this message]
2017-08-01 11:52 ` [PATCH V4 RESEND 2/6] pinctrl: imx: switch to use the generic pinmux property Linus Walleij
2017-07-25 13:41 ` [PATCH V4 RESEND 3/6] pinctrl: imx: add imx7ulp driver Dong Aisheng
2017-08-01 11:53 ` Linus Walleij
2017-07-25 13:41 ` [PATCH V4 RESEND 4/6] pinctrl: imx: remove gpio_request_enable and gpio_disable_free Dong Aisheng
2017-08-01 11:54 ` Linus Walleij
2017-07-25 13:41 ` [PATCH V4 RESEND 5/6] pinctrl: imx: make imx_pmx_ops.gpio_set_direction platform specific callbacks Dong Aisheng
2017-08-01 11:55 ` Linus Walleij
2017-07-25 13:41 ` [PATCH V4 RESEND 6/6] pinctrl: pinctrl-imx7ulp: add gpio_set_direction support Dong Aisheng
2017-08-01 11:56 ` 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=1500990116-3620-3-git-send-email-aisheng.dong@nxp.com \
--to=aisheng.dong@nxp.com \
--cc=dongas86@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=ping.bai@nxp.com \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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).