From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: doubt about where to put pin-mux in MX28 based platform DT
Date: Thu, 07 Mar 2013 14:06:27 +0100 [thread overview]
Message-ID: <513890D3.5060905@free-electrons.com> (raw)
In-Reply-To: <5137769F.1000308@digi.com>
Hi Hector,
Le 06/03/2013 18:02, Hector Palacios a ?crit :
> I'm creating the DT for a custom platform based on Freescale MX28 CPU
> and I have some doubts about where to add some pin mux configurations:
> whether in imx28.dtsi or in my platform dts.
>
> A pair of examples folow:
>
> Example #1. My platform is using a valid IOMUX for DUART TX/RX lines
> which is not covered in imx28.dtsi, namely the I2C0 pins. Since this is
> a valid IOMUX that can be used by other platforms, I'd say I should
> included it in imx28.dtsi:
>
> diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.dtsi
> index 3fa6d19..8928b7b 100644
> --- a/arch/arm/boot/dts/imx28.dtsi
> +++ b/arch/arm/boot/dts/imx28.dtsi
> @@ -186,6 +186,17 @@
> fsl,pull-up = <0>;
> };
>
> + duart_pins_c: duart at 2 {
> + reg = <2>;
> + fsl,pinmux-ids = <
> + 0x3182 /*
> MX28_PAD_I2C0_SCL__DUART_RX */
> + 0x3192 /*
> MX28_PAD_I2C0_SDA__DUART_TX */
> + >;
> + fsl,drive-strength = <0>;
> + fsl,voltage = <1>;
> + fsl,pull-up = <0>;
> + };
> +
> duart_4pins_a: duart-4pins at 0 {
> reg = <0>;
> fsl,pinmux-ids = <
That's right.
> Example #2. My platform assembles a NAND chip which is powered at 1.8V.
> The imx28.dtsi has a configuration 'gpmi_pins_a: gpmi-nand at 0' that
> configures the pins at 3.3V.
> Should I create another entry here 'gpmi_pins_b: gpmi-nand at 1' with
> fsl,voltage = <0>; or should I create a specific entry in my platform's
> DT instead?
> What is the convention?
Since it's the same pinset, I'd rather go for using gpmi_pins_a in your
NAND chip node, but also overload the fsl,voltage property of
gpmi_pins_a in your board device tree.
That would give something like
pinctrl at 80018000 {
gpmi_pins_a: gpmi-nand at 0 {
fsl,voltage = <0>;
};
};
nand at deadbeef {
pinctrl-names = "default";
pinctrl-0 = <&gpmi_pins_a>;
}
But maybe Sascha will have a different view on this.
Maxime
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Hector Palacios <hector.palacios-i7dp0qKlBMg@public.gmane.org>
Cc: "fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org"
<fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: doubt about where to put pin-mux in MX28 based platform DT
Date: Thu, 07 Mar 2013 14:06:27 +0100 [thread overview]
Message-ID: <513890D3.5060905@free-electrons.com> (raw)
In-Reply-To: <5137769F.1000308-i7dp0qKlBMg@public.gmane.org>
Hi Hector,
Le 06/03/2013 18:02, Hector Palacios a écrit :
> I'm creating the DT for a custom platform based on Freescale MX28 CPU
> and I have some doubts about where to add some pin mux configurations:
> whether in imx28.dtsi or in my platform dts.
>
> A pair of examples folow:
>
> Example #1. My platform is using a valid IOMUX for DUART TX/RX lines
> which is not covered in imx28.dtsi, namely the I2C0 pins. Since this is
> a valid IOMUX that can be used by other platforms, I'd say I should
> included it in imx28.dtsi:
>
> diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.dtsi
> index 3fa6d19..8928b7b 100644
> --- a/arch/arm/boot/dts/imx28.dtsi
> +++ b/arch/arm/boot/dts/imx28.dtsi
> @@ -186,6 +186,17 @@
> fsl,pull-up = <0>;
> };
>
> + duart_pins_c: duart@2 {
> + reg = <2>;
> + fsl,pinmux-ids = <
> + 0x3182 /*
> MX28_PAD_I2C0_SCL__DUART_RX */
> + 0x3192 /*
> MX28_PAD_I2C0_SDA__DUART_TX */
> + >;
> + fsl,drive-strength = <0>;
> + fsl,voltage = <1>;
> + fsl,pull-up = <0>;
> + };
> +
> duart_4pins_a: duart-4pins@0 {
> reg = <0>;
> fsl,pinmux-ids = <
That's right.
> Example #2. My platform assembles a NAND chip which is powered at 1.8V.
> The imx28.dtsi has a configuration 'gpmi_pins_a: gpmi-nand@0' that
> configures the pins at 3.3V.
> Should I create another entry here 'gpmi_pins_b: gpmi-nand@1' with
> fsl,voltage = <0>; or should I create a specific entry in my platform's
> DT instead?
> What is the convention?
Since it's the same pinset, I'd rather go for using gpmi_pins_a in your
NAND chip node, but also overload the fsl,voltage property of
gpmi_pins_a in your board device tree.
That would give something like
pinctrl@80018000 {
gpmi_pins_a: gpmi-nand@0 {
fsl,voltage = <0>;
};
};
nand@deadbeef {
pinctrl-names = "default";
pinctrl-0 = <&gpmi_pins_a>;
}
But maybe Sascha will have a different view on this.
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:[~2013-03-07 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 17:02 doubt about where to put pin-mux in MX28 based platform DT Hector Palacios
2013-03-07 13:06 ` Maxime Ripard [this message]
2013-03-07 13:06 ` Maxime Ripard
[not found] ` <513890D3.5060905-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2013-03-21 16:57 ` Hector Palacios
[not found] ` <514B3C15.8080103-i7dp0qKlBMg@public.gmane.org>
2013-03-22 13:28 ` Maxime Ripard
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=513890D3.5060905@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.