Message ID | 20140115094551.GA26117@frolo.macqel (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On Wed, Jan 15, 2014 at 7:45 AM, Philippe De Muyter <phdm@macq.eu> wrote: > Here are my patches (I have called my board imx6dl-p6-2094): > Do I need to replace the hex value after MX6QDL_PAD_GPIO_16__ENET_REF_CLK > by something else ? hummingboard uses: MX6QDL_PAD_GPIO_16__ENET_REF_CLK 0xc0000000 Check arch/arm/boot/dts/imx6qdl-microsom-ar8035.dtsi in linux-next. Regards, Fabio Estevam
On Wed, Jan 15, 2014 at 08:13:15AM -0200, Fabio Estevam wrote: > On Wed, Jan 15, 2014 at 7:45 AM, Philippe De Muyter <phdm@macq.eu> wrote: > > > Here are my patches (I have called my board imx6dl-p6-2094): > > Do I need to replace the hex value after MX6QDL_PAD_GPIO_16__ENET_REF_CLK > > by something else ? > > hummingboard uses: > > MX6QDL_PAD_GPIO_16__ENET_REF_CLK 0xc0000000 I quickly tried that, but that does not solve my problem (still tx timeout) > > Check arch/arm/boot/dts/imx6qdl-microsom-ar8035.dtsi in linux-next. I will look there now. Thanks Philippe
On Wed, Jan 15, 2014 at 08:13:15AM -0200, Fabio Estevam wrote: > On Wed, Jan 15, 2014 at 7:45 AM, Philippe De Muyter <phdm@macq.eu> wrote: > > > Here are my patches (I have called my board imx6dl-p6-2094): > > Do I need to replace the hex value after MX6QDL_PAD_GPIO_16__ENET_REF_CLK > > by something else ? > > hummingboard uses: > > MX6QDL_PAD_GPIO_16__ENET_REF_CLK 0xc0000000 > > Check arch/arm/boot/dts/imx6qdl-microsom-ar8035.dtsi in linux-next. They use RGMII, while I have RMII :( Philippe
On Wed, Jan 15, 2014 at 8:55 AM, Philippe De Muyter <phdm@macq.eu> wrote: > On Wed, Jan 15, 2014 at 08:13:15AM -0200, Fabio Estevam wrote: >> On Wed, Jan 15, 2014 at 7:45 AM, Philippe De Muyter <phdm@macq.eu> wrote: >> >> > Here are my patches (I have called my board imx6dl-p6-2094): >> > Do I need to replace the hex value after MX6QDL_PAD_GPIO_16__ENET_REF_CLK >> > by something else ? >> >> hummingboard uses: >> >> MX6QDL_PAD_GPIO_16__ENET_REF_CLK 0xc0000000 >> >> Check arch/arm/boot/dts/imx6qdl-microsom-ar8035.dtsi in linux-next. > > They use RGMII, while I have RMII :( Are you able to do TFTP in the bootloader? Maybe it is easier to debug from the bootloader and check if the PHY is being properly powered and clocked. You can check mx6slevk which uses RMII. Regards, Fabio Estevam
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile index d57c1a6..bc115f7 100644 --- a/arch/arm/boot/dts/Makefile +++ b/arch/arm/boot/dts/Makefile @@ -136,6 +136,7 @@ dtb-$(CONFIG_ARCH_MXC) += \ imx53-mba53.dtb \ imx53-qsb.dtb \ imx53-smd.dtb \ + imx6dl-p6-2094.dtb \ imx6dl-sabreauto.dtb \ imx6dl-sabresd.dtb \ imx6dl-wandboard.dtb \ diff --git a/arch/arm/boot/dts/imx6dl-p6-2094.dts b/arch/arm/boot/dts/imx6dl-p6-2094.dts new file mode 100644 index 0000000..526e83a --- /dev/null +++ b/arch/arm/boot/dts/imx6dl-p6-2094.dts @@ -0,0 +1,35 @@ +/* + * Copyright (C) 2013 Freescale Semiconductor, Inc. + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + */ + +/dts-v1/; + +#include "imx6dl.dtsi" +#include "imx6qdl-sabresd.dtsi" + +&usdhc4 { + non-removable; +#if 0 + vmmc-supply = <®_3p3v>; +#endif + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_usdhc4_1>; + bus-width = <8>; + status = "okay"; +}; + +&fec { + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_enet_4>; + phy-mode = "rmii"; + status = "okay"; +}; + +/ { + model = "Macq i.MX6 DualLite P6-2094 Board"; + compatible = "fsl,imx6dl-sabresd", "fsl,imx6dl"; +}; diff --git a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi index e75e11b..d850ff1 100644 --- a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi +++ b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi @@ -181,7 +181,9 @@ MX6QDL_PAD_NANDF_CLE__GPIO6_IO07 0x80000000 MX6QDL_PAD_ENET_TXD1__GPIO1_IO29 0x80000000 MX6QDL_PAD_EIM_D22__GPIO3_IO22 0x80000000 +#if 0 /* conflicts with pinctrl_enet_4:MX6QDL_PAD_ENET_CRS_DV__ENET_RX_EN */ MX6QDL_PAD_ENET_CRS_DV__GPIO1_IO25 0x80000000 +#endif >; }; }; diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.dtsi index fb28b2e..7a0b341 100644 --- a/arch/arm/boot/dts/imx6qdl.dtsi +++ b/arch/arm/boot/dts/imx6qdl.dtsi @@ -729,6 +729,22 @@ MX6QDL_PAD_ENET_TX_EN__ENET_TX_EN 0x1b0b0 >; }; + + pinctrl_enet_4: enetgrp-4 { + fsl,pins = < + MX6QDL_PAD_ENET_MDC__ENET_MDC 0x1b0b0 + MX6QDL_PAD_ENET_MDIO__ENET_MDIO 0x1b0b0 + MX6QDL_PAD_GPIO_16__ENET_REF_CLK 0x1b0b0 /* RMII */ + MX6QDL_PAD_ENET_RXD0__ENET_RX_DATA0 0x1b0b0 /* MII/RMII */ + MX6QDL_PAD_ENET_RXD1__ENET_RX_DATA1 0x1b0b0 /* MII/RMII */ + MX6QDL_PAD_ENET_CRS_DV__ENET_RX_EN 0x1b0b0 /* MII/RMII */ + MX6QDL_PAD_ENET_RX_ER__ENET_RX_ER 0x1b0b0 /* MII/RMII */ + MX6QDL_PAD_ENET_TXD0__ENET_TX_DATA0 0x1b0b0 /* MII/RMII */ + MX6QDL_PAD_ENET_TXD1__ENET_TX_DATA1 0x1b0b0 /* MII/RMII */ + MX6QDL_PAD_ENET_TX_EN__ENET_TX_EN 0x1b0b0 /* MII/RMII */ + MX6QDL_PAD_GPIO_19__ENET_TX_ER 0x1b0b0 /* MII/RMII */ + >; + }; }; esai {