From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM:MX28: Add additionnal muxing options to iMX28 DTSI
Date: Tue, 26 Jun 2012 11:42:44 +0200 [thread overview]
Message-ID: <4FE98414.4070903@free-electrons.com> (raw)
In-Reply-To: <20120625155047.GD2342@S2101-09.ap.freescale.net>
Hi,
Le 25/06/2012 17:50, Shawn Guo a ?crit :
> Suggested subject prefix "ARM: dts: imx28: ..."
Ok.
> On Fri, Jun 22, 2012 at 11:14:53AM +0200, Maxime Ripard wrote:
>> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
>> ---
>> arch/arm/boot/dts/imx28.dtsi | 19 ++++++++++++++++++-
>> 1 file changed, 18 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.dtsi
>> index 4634cb8..babc604 100644
>> --- a/arch/arm/boot/dts/imx28.dtsi
>> +++ b/arch/arm/boot/dts/imx28.dtsi
>> @@ -159,7 +159,7 @@
>> #interrupt-cells = <2>;
>> };
>>
>> - duart_pins_a: duart at 0 {
>> + duart_pins_a: duart-a at 0 {
>
> Leave this line unchanged ...
>
>> reg = <0>;
>> fsl,pinmux-ids = <0x3102 0x3112>;
>> fsl,drive-strength = <0>;
>> @@ -167,6 +167,14 @@
>> fsl,pull-up = <0>;
>> };
>>
>> + duart_pins_b: duart-b at 0 {
>> + reg = <0>;
>
> ... and have the new mux option for duart like
>
> duart_pins_b: duart at 1 {
> reg = <1>;
>
> then, pinctrl system will be able to report there are 2 pin groups for
> function "duart" in debugfs.
Ok.
I have two questions here though.
First, I'm worrying a bit about the fact that the duart_pins_b is
actually the first pin groups in the muxing selection register by index,
before duart_pins_a. It's a bit confusing, but it would imply that we
would need to rename duart_pins_a to duart_pins_b, and change all the
references to it as well, but I can definitely send a patch for it. What
is your opinion ?
Secondly, why do we need to change the reg field as well ?
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-06-26 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 9:14 [PATCH v2] ARM:MXS: Initial support for the Crystalfontz CFA-10036 Maxime Ripard
2012-06-22 9:14 ` [PATCH 1/2] ARM:MX28: Add additionnal muxing options to iMX28 DTSI Maxime Ripard
2012-06-25 15:50 ` Shawn Guo
2012-06-26 9:02 ` Thomas Petazzoni
2012-06-26 11:33 ` Shawn Guo
2012-06-26 9:42 ` Maxime Ripard [this message]
2012-06-26 12:03 ` Shawn Guo
2012-06-22 9:14 ` [PATCH 2/2] ARM: MXS: Add Crystalfontz CFA-10036 DTS Maxime Ripard
2012-06-25 15:58 ` Shawn Guo
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=4FE98414.4070903@free-electrons.com \
--to=maxime.ripard@free-electrons.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).