From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 3/3] ARM: dts: imx6x: Add enet2 support for imx6sx-sdb board
Date: Sun, 28 Sep 2014 11:28:53 +0800 [thread overview]
Message-ID: <20140928032852.GC12999@dragon> (raw)
In-Reply-To: <1411524680-12863-4-git-send-email-b38611@freescale.com>
On Wed, Sep 24, 2014 at 10:11:20AM +0800, Fugang Duan wrote:
> Add enet2 support for imx6sx-sdb board, and add the "fsl,imx6q-fec"
> compatible for fec2 node to be compatible with the old version.
>
> Signed-off-by: Fugang Duan <B38611@freescale.com>
> ---
> arch/arm/boot/dts/imx6sx-sdb.dts | 28 ++++++++++++++++++++++++++++
> arch/arm/boot/dts/imx6sx.dtsi | 2 +-
> 2 files changed, 29 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/boot/dts/imx6sx-sdb.dts b/arch/arm/boot/dts/imx6sx-sdb.dts
> index 82d6b34..06e0977 100644
> --- a/arch/arm/boot/dts/imx6sx-sdb.dts
> +++ b/arch/arm/boot/dts/imx6sx-sdb.dts
> @@ -133,6 +133,14 @@
> &fec1 {
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_enet1>;
> + pinctrl-assert-gpios = <&gpio4 16 GPIO_ACTIVE_HIGH>, <&gpio2 6 GPIO_ACTIVE_LOW>;
I do not think this property is supported by upstream kernel.
> + phy-mode = "rgmii";
> + status = "okay";
> +};
> +
> +&fec2 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_enet2>;
> phy-mode = "rgmii";
> status = "okay";
> };
> @@ -394,6 +402,26 @@
> MX6SX_PAD_RGMII1_RD2__ENET1_RX_DATA_2 0x3081
> MX6SX_PAD_RGMII1_RD3__ENET1_RX_DATA_3 0x3081
> MX6SX_PAD_RGMII1_RX_CTL__ENET1_RX_EN 0x3081
> + MX6SX_PAD_QSPI1A_DATA0__GPIO4_IO_16 0x80000000
> + MX6SX_PAD_QSPI1A_DATA3__GPIO4_IO_19 0x80000000
> + MX6SX_PAD_ENET2_RX_CLK__ENET2_REF_CLK_25M 0x91
> + >;
> + };
> +
> + pinctrl_enet2: enet2grp {
> + fsl,pins = <
> + MX6SX_PAD_RGMII2_TXC__ENET2_RGMII_TXC 0xa0b9
> + MX6SX_PAD_RGMII2_TD0__ENET2_TX_DATA_0 0xa0b1
> + MX6SX_PAD_RGMII2_TD1__ENET2_TX_DATA_1 0xa0b1
> + MX6SX_PAD_RGMII2_TD2__ENET2_TX_DATA_2 0xa0b1
> + MX6SX_PAD_RGMII2_TD3__ENET2_TX_DATA_3 0xa0b1
> + MX6SX_PAD_RGMII2_TX_CTL__ENET2_TX_EN 0xa0b1
> + MX6SX_PAD_RGMII2_RXC__ENET2_RX_CLK 0x3081
> + MX6SX_PAD_RGMII2_RD0__ENET2_RX_DATA_0 0x3081
> + MX6SX_PAD_RGMII2_RD1__ENET2_RX_DATA_1 0x3081
> + MX6SX_PAD_RGMII2_RD2__ENET2_RX_DATA_2 0x3081
> + MX6SX_PAD_RGMII2_RD3__ENET2_RX_DATA_3 0x3081
> + MX6SX_PAD_RGMII2_RX_CTL__ENET2_RX_EN 0x3081
> >;
> };
>
> diff --git a/arch/arm/boot/dts/imx6sx.dtsi b/arch/arm/boot/dts/imx6sx.dtsi
> index 888dd76..5a36053 100644
> --- a/arch/arm/boot/dts/imx6sx.dtsi
> +++ b/arch/arm/boot/dts/imx6sx.dtsi
> @@ -875,7 +875,7 @@
> };
>
> fec2: ethernet at 021b4000 {
> - compatible = "fsl,imx6sx-fec";
> + compatible = "fsl,imx6sx-fec", "fsl,imx6q-fec";
Why is this change is necessary? If "fsl,imx6sx-fec" is supported by
driver, it can be matched.
Shawn
> reg = <0x021b4000 0x4000>;
> interrupts = <GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>,
> <GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>;
> --
> 1.7.8
>
next prev parent reply other threads:[~2014-09-28 3:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 2:11 [PATCH v1 0/3] ARM: imx6sx: add enet support Fugang Duan
2014-09-24 2:11 ` [PATCH v1 1/3] ARM: imx6sx: add imx6sx iomux-gpr field define Fugang Duan
2014-09-24 2:11 ` [PATCH v1 2/3] ARM: imx: add enet init for i.mx6sx Fugang Duan
2014-09-24 2:11 ` [PATCH v1 3/3] ARM: dts: imx6x: Add enet2 support for imx6sx-sdb board Fugang Duan
2014-09-28 3:28 ` Shawn Guo [this message]
2014-09-28 3:34 ` fugang.duan at freescale.com
2014-09-28 3:42 ` Shawn Guo
2014-09-28 5:20 ` fugang.duan at freescale.com
2014-09-28 5:32 ` Shawn Guo
2014-09-28 5:40 ` fugang.duan at freescale.com
2014-09-28 3:45 ` [PATCH v1 0/3] ARM: imx6sx: add enet support Shawn Guo
-- strict thread matches above, loose matches on Subject: below --
2014-09-23 9:36 Fugang Duan
2014-09-23 9:36 ` [PATCH v1 3/3] ARM: dts: imx6x: Add enet2 support for imx6sx-sdb board Fugang Duan
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=20140928032852.GC12999@dragon \
--to=shawn.guo@freescale.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).