From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: imx28: Add additionnal muxing options to iMX28 DTSI
Date: Wed, 27 Jun 2012 13:47:57 +0200 [thread overview]
Message-ID: <201206271347.57707.marex@denx.de> (raw)
In-Reply-To: <1340785092-27035-2-git-send-email-maxime.ripard@free-electrons.com>
Dear Maxime Ripard,
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
>
> Cc: Brian Lily <brian@crystalfontz.com>
Reviewed-by: Marek Vasut <marex@denx.de>
> ---
> arch/arm/boot/dts/imx28.dtsi | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.dtsi
> index 4634cb8..2b067d2 100644
> --- a/arch/arm/boot/dts/imx28.dtsi
> +++ b/arch/arm/boot/dts/imx28.dtsi
> @@ -167,6 +167,14 @@
> fsl,pull-up = <0>;
> };
>
> + duart_pins_b: duart at 1 {
> + reg = <1>;
> + fsl,pinmux-ids = <0x3022 0x3032>;
> + fsl,drive-strength = <0>;
> + fsl,voltage = <1>;
> + fsl,pull-up = <0>;
> + };
> +
> mac0_pins_a: mac0 at 0 {
> reg = <0>;
> fsl,pinmux-ids = <0x4000 0x4010 0x4020
> @@ -196,6 +204,15 @@
> fsl,pull-up = <1>;
> };
>
> + mmc0_4bit_pins_a: mmc0-4bit at 0 {
> + reg = <0>;
> + fsl,pinmux-ids = <0x2000 0x2010 0x2020
> + 0x2030 0x2080 0x2090 0x20a0>;
> + fsl,drive-strength = <1>;
> + fsl,voltage = <1>;
> + fsl,pull-up = <1>;
> + };
> +
> mmc0_cd_cfg: mmc0-cd-cfg {
> fsl,pinmux-ids = <0x2090>;
> fsl,pull-up = <0>;
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-06-27 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 8:18 [PATCH v3] ARM:MXS: Initial support for the Crystalfontz CFA-10036 Maxime Ripard
2012-06-27 8:18 ` [PATCH 1/2] ARM: dts: imx28: Add additionnal muxing options to iMX28 DTSI Maxime Ripard
2012-06-27 11:47 ` Marek Vasut [this message]
2012-06-28 3:37 ` Shawn Guo
2012-06-27 8:18 ` [PATCH 2/2] ARM: MXS: Add Crystalfontz CFA-10036 DTS Maxime Ripard
2012-06-27 11:48 ` Marek Vasut
2012-06-28 3:39 ` 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=201206271347.57707.marex@denx.de \
--to=marex@denx.de \
--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).