From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: phandle entries will be applied sequentially
Date: Wed, 9 Oct 2013 14:45:29 +0100 [thread overview]
Message-ID: <20131009134529.GH25034@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CACRpkda3J4cCTnFaQFrmZ=box6EeJ8WQZpuQpi2p_BFX+W2vuw@mail.gmail.com>
On Wed, Oct 09, 2013 at 03:09:21PM +0200, Linus Walleij wrote:
> It's more like the pin control core is passing the array of settings
> to the driver and the behaviour is specified per-driver.
>
> So that is from the kernels point of view, no matter whether
> device tree is used or not. A specific driver may instill specific
> behaviour - sequential or not.
Right, so that means doing this:
pinctrl_usdhc1_1: usdhc1grp-1 {
fsl,pins = <
...
MX6QDL_PAD_SD1_DAT3__SD1_DATA3 0x17059
...
>;
};
pinctrl_usdhc1_1_dat3cd: usdhc1grp-3 {
fsl,pins = <
MX6QDL_PAD_SD1_DAT3__SD1_DATA3 0x13059
>;
};
and then:
pinctrl-0 = <&pinctrl_usdhc1_1 &pinctrl_usdhc1_1_dat3cd>;
can result in either "MX6QDL_PAD_SD1_DAT3__SD1_DATA3 0x17059" or
"MX6QDL_PAD_SD1_DAT3__SD1_DATA3 0x13059" being the final configuration
for that pin.
What that means is that for any pinctrl setting, pins to be configured
must be mentioned exactly once and once only.
next prev parent reply other threads:[~2013-10-09 13:45 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
2013-10-09 12:40 ` Linus Walleij
2013-10-09 12:44 ` Russell King - ARM Linux
2013-10-09 13:09 ` Linus Walleij
2013-10-09 13:45 ` Russell King - ARM Linux [this message]
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
2013-10-10 8:03 ` Linus Walleij
2013-10-10 10:12 ` Shawn Guo
2013-10-10 10:08 ` Russell King - ARM Linux
2013-10-10 10:22 ` Shawn Guo
2013-10-10 10:23 ` Russell King - ARM Linux
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=20131009134529.GH25034@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).