From: Russell King - ARM Linux <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
To: Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Linus Walleij
<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Sherman Yin <syin-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Subject: Re: [PATCH] pinctrl: phandle entries will be applied sequentially
Date: Thu, 10 Oct 2013 11:23:23 +0100 [thread overview]
Message-ID: <20131010102322.GQ25034@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20131010102205.GD29191-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
On Thu, Oct 10, 2013 at 06:22:07PM +0800, Shawn Guo wrote:
> What about the solution suggested by Stephen, moving
> MX6QDL_PAD_SD1_DAT3__SD1_DATA3 out from pinctrl_usdhc1_1 and having
> additional nodes/phandle for DAT3 with different settings?
>
> diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.dtsi
> index 59154dc..fd52f4e 100644
> --- a/arch/arm/boot/dts/imx6qdl.dtsi
> +++ b/arch/arm/boot/dts/imx6qdl.dtsi
> @@ -1157,7 +1157,6 @@
> MX6QDL_PAD_SD1_DAT0__SD1_DATA0 0x17059
> MX6QDL_PAD_SD1_DAT1__SD1_DATA1 0x17059
> MX6QDL_PAD_SD1_DAT2__SD1_DATA2 0x17059
> - MX6QDL_PAD_SD1_DAT3__SD1_DATA3 0x17059
> MX6QDL_PAD_NANDF_D0__SD1_DATA4 0x17059
> MX6QDL_PAD_NANDF_D1__SD1_DATA5 0x17059
> MX6QDL_PAD_NANDF_D2__SD1_DATA6 0x17059
> @@ -1165,6 +1164,18 @@
> >;
> };
>
> + pinctrl_usdhc1_1_dat3: usdhc1dat3-1 {
> + fsl,pins = <
> + MX6QDL_PAD_SD1_DAT3__SD1_DATA3 0x17059
> + >;
> + };
> +
> + pinctrl_usdhc1_1_dat3cd: usdhc1dat3cd-1 {
> + fsl,pins = <
> + MX6QDL_PAD_SD1_DAT3__SD1_DATA3 0x13059
> + >;
> + };
>
> Then pinctrl-0 = <&pinctrl_usdhc1_1 &pinctrl_usdhc1_1_dat3> for existing
> boards, and <&pinctrl_usdhc1_1 &pinctrl_usdhc1_1_dat3cd> for boards that
> want to use DAT3 for card detection.
Yes, that avoids the issue entirely, and is a much better solution IMHO.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-10-10 10:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 5:42 [PATCH] pinctrl: phandle entries will be applied sequentially Shawn Guo
[not found] ` <1381297324-19006-1-git-send-email-shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-10-09 12:40 ` Linus Walleij
[not found] ` <CACRpkdazPK6SNg9PdWCrjB8nwho1rCueumJWAN=STXdN1zNnMA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-09 12:44 ` Russell King - ARM Linux
[not found] ` <20131009124425.GG25034-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2013-10-09 13:09 ` Linus Walleij
[not found] ` <CACRpkda3J4cCTnFaQFrmZ=box6EeJ8WQZpuQpi2p_BFX+W2vuw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-09 13:45 ` Russell King - ARM Linux
[not found] ` <20131009134529.GH25034-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2013-10-09 14:14 ` Linus Walleij
2013-10-10 8:08 ` Shawn Guo
2013-10-09 15:58 ` Stephen Warren
2013-10-10 7:26 ` Shawn Guo
[not found] ` <20131010072624.GA29191-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2013-10-10 8:03 ` Linus Walleij
[not found] ` <CACRpkdZFx94kEXiWPHOZVmK1d21pM0jg4y6coqu3Pyd=9HES5w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-10 10:12 ` Shawn Guo
2013-10-10 10:08 ` Russell King - ARM Linux
[not found] ` <20131010100840.GP25034-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2013-10-10 10:22 ` Shawn Guo
[not found] ` <20131010102205.GD29191-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2013-10-10 10:23 ` Russell King - ARM Linux [this message]
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=20131010102322.GQ25034@n2100.arm.linux.org.uk \
--to=linux-lfz/pmaqli7xmaaqvzeohq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=syin-dY08KVG/lbpWk0Htik3J/w@public.gmane.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).