From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: imx6q: Add pinctrl for usdhc2 and enet
Date: Thu, 30 May 2013 14:25:29 +0800 [thread overview]
Message-ID: <20130530062526.GA2602@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <1369861609-30408-2-git-send-email-c.hemp@phytec.de>
On Wed, May 29, 2013 at 11:06:48PM +0200, Christian Hemp wrote:
> Add a group to the usdhc2 and enet pinctrl.
>
> Signed-off-by: Christian Hemp <c.hemp@phytec.de>
> ---
> arch/arm/boot/dts/imx6q.dtsi | 33 +++++++++++++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
>
> diff --git a/arch/arm/boot/dts/imx6q.dtsi b/arch/arm/boot/dts/imx6q.dtsi
> index ed11bcf..c0c8b7b 100644
> --- a/arch/arm/boot/dts/imx6q.dtsi
> +++ b/arch/arm/boot/dts/imx6q.dtsi
> @@ -157,6 +157,28 @@
> MX6Q_PAD_RGMII_RX_CTL__RGMII_RX_CTL 0x1b0b0
> >;
> };
> +
> + pinctrl_enet_3: enetgrp-3 {
> + fsl,pins = <
> + MX6Q_PAD_ENET_MDIO__ENET_MDIO 0x1b0b0
> + MX6Q_PAD_ENET_MDC__ENET_MDC 0x1b0b0
> + MX6Q_PAD_RGMII_TXC__RGMII_TXC 0x1b0b0
> + MX6Q_PAD_RGMII_TD0__RGMII_TD0 0x1b0b0
> + MX6Q_PAD_RGMII_TD1__RGMII_TD1 0x1b0b0
> + MX6Q_PAD_RGMII_TD2__RGMII_TD2 0x1b0b0
> + MX6Q_PAD_RGMII_TD3__RGMII_TD3 0x1b0b0
> + MX6Q_PAD_RGMII_TX_CTL__RGMII_TX_CTL 0x1b0b0
> + MX6Q_PAD_ENET_REF_CLK__ENET_TX_CLK 0x1b0b0
> + MX6Q_PAD_RGMII_RXC__RGMII_RXC 0x1b0b0
> + MX6Q_PAD_RGMII_RD0__RGMII_RD0 0x1b0b0
> + MX6Q_PAD_RGMII_RD1__RGMII_RD1 0x1b0b0
> + MX6Q_PAD_RGMII_RD2__RGMII_RD2 0x1b0b0
> + MX6Q_PAD_RGMII_RD3__RGMII_RD3 0x1b0b0
> + MX6Q_PAD_RGMII_RX_CTL__RGMII_RX_CTL 0x1b0b0
> + MX6Q_PAD_ENET_CRS_DV__SPDIF_EXT_CLK 0x1b0b0
Why do you need to set up SPDIF_EXT_CLK in ENET pin group?
Shawn
> + MX6Q_PAD_ENET_TX_EN__ENET_TX_EN 0x1b0b0
> + >;
> + };
> };
>
> gpmi-nand {
> @@ -266,6 +288,17 @@
> MX6Q_PAD_NANDF_D7__SD2_DATA7 0x17059
> >;
> };
> +
> + pinctrl_usdhc2_2: usdhc2grp-2 {
> + fsl,pins = <
> + MX6Q_PAD_SD2_CMD__SD2_CMD 0x17059
> + MX6Q_PAD_SD2_CLK__SD2_CLK 0x10059
> + MX6Q_PAD_SD2_DAT0__SD2_DATA0 0x17059
> + MX6Q_PAD_SD2_DAT1__SD2_DATA1 0x17059
> + MX6Q_PAD_SD2_DAT2__SD2_DATA2 0x17059
> + MX6Q_PAD_SD2_DAT3__SD2_DATA3 0x17059
> + >;
> + };
> };
>
> usdhc3 {
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2013-05-30 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 21:06 [PATCH 0/2] Add Phytec phyFLEX-i.MX6 board Christian Hemp
2013-05-29 21:06 ` [PATCH 1/2] ARM: dts: imx6q: Add pinctrl for usdhc2 and enet Christian Hemp
2013-05-30 6:25 ` Shawn Guo [this message]
2013-05-29 21:06 ` [PATCH 2/2] ARM: dts: Phytec phyFLEX-i.MX6 support Christian Hemp
2013-05-30 6:31 ` Shawn Guo
2013-05-31 9:56 ` Christian Hemp
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=20130530062526.GA2602@S2101-09.ap.freescale.net \
--to=shawn.guo@linaro.org \
--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