All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Duan <fugang.duan@nxp.com>
To: Oliver Graute <oliver.graute@gmail.com>
Cc: "festevam@gmail.com" <festevam@gmail.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	dl-linux-imx <linux-imx@nxp.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [EXT] fec driver: ethernet rx is deaf on variscite imx6ul board
Date: Thu, 24 Oct 2019 03:08:53 +0000	[thread overview]
Message-ID: <VI1PR0402MB360013E0A785313D5D676633FF6A0@VI1PR0402MB3600.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20191023201000.GE20321@ripley>

From: Oliver Graute <oliver.graute@gmail.com> Sent: Thursday, October 24, 2019 4:10 AM
> Hello,
> 
> I use the following nodes in my devicetree to get two ethernet ports working
> with fec driver on a Variscite DART-6UL SoM Board (imx6ul).
> 
> But ethernet RX is deaf and not working. Some clue whats is the issue here?
> 
> Best regards,
> 
> Oliver

It is for new board bringup ? If so, please ask support from NXP in normal operation.
I check your dts in simple, below are my comments:
- MDIO/MDC pins are not configurated
- Please ensure the RMII reference clock 50Mhz active on line, measured it by oscillometer.

Andy
> 
> &fec1 {
>         pinctrl-names = "default";
>         pinctrl-0 = <&pinctrl_enet1>;
>         phy-mode = "rmii";
>         phy-reset-gpios = <&gpio5 0 1>;
>         phy-reset-duration = <100>;
>         phy-handle = <&ethphy0>;
> };
> 
> &fec2 {
>         pinctrl-names = "default";
>         pinctrl-0 = <&pinctrl_enet2>;
>         phy-mode = "rmii";
>         phy-handle = <&ethphy1>;
>         phy-reset-gpios = <&gpio1 10 1>;
>         phy-reset-duration = <100>;
> 
>         mdio {
>                 #address-cells = <1>;
>                 #size-cells = <0>;
> 
>                 ethphy0: ethernet-phy@1 {
>                         compatible = "ethernet-phy-ieee802.3-c22";
>                         micrel,rmii-reference-clock-select-25-mhz;
>                         clocks = <&clk_rmii_ref>;
>                         clock-names = "rmii-ref";
>                         reg = <1>;
>                 };
> 
>                 ethphy1: ethernet-phy@3 {
>                         compatible = "ethernet-phy-ieee802.3-c22";
>                         micrel,rmii-reference-clock-select-25-mhz;
>                         clocks = <&clk_rmii_ref>;
>                         clock-names = "rmii-ref";
>                         reg = <3>;
>                 };
>         };
> };
>         pinctrl_enet1: enet1grp {
>                 fsl,pins = <
>                         MX6UL_PAD_ENET1_RX_EN__ENET1_RX_EN
> 0x1b0b0
>                         MX6UL_PAD_ENET1_RX_ER__ENET1_RX_ER
> 0x1b0b0
> 
> MX6UL_PAD_ENET1_RX_DATA0__ENET1_RDATA00 0x1b0b0
> 
> MX6UL_PAD_ENET1_RX_DATA1__ENET1_RDATA01 0x1b0b0
>                         MX6UL_PAD_ENET1_TX_EN__ENET1_TX_EN
> 0x1b0b0
> 
> MX6UL_PAD_ENET1_TX_DATA0__ENET1_TDATA00 0x1b0b0
> 
> MX6UL_PAD_ENET1_TX_DATA1__ENET1_TDATA01 0x1b0b0
> 
> MX6UL_PAD_ENET1_TX_CLK__ENET1_REF_CLK1  0x4001b031
>                 >;
>         };
> 
>         pinctrl_enet2: enet2grp {
>                 fsl,pins = <
>                         MX6UL_PAD_ENET2_RX_EN__ENET2_RX_EN
> 0x1b0b0
>                         MX6UL_PAD_ENET2_RX_ER__ENET2_RX_ER
> 0x1b0b0
> 
> MX6UL_PAD_ENET2_RX_DATA0__ENET2_RDATA00 0x1b0b0
> 
> MX6UL_PAD_ENET2_RX_DATA1__ENET2_RDATA01 0x1b0b0
>                         MX6UL_PAD_ENET2_TX_EN__ENET2_TX_EN
> 0x1b0b0
> 
> MX6UL_PAD_ENET2_TX_DATA0__ENET2_TDATA00 0x1b0b0
> 
> MX6UL_PAD_ENET2_TX_DATA1__ENET2_TDATA01 0x1b0b0
> 
> MX6UL_PAD_ENET2_TX_CLK__ENET2_REF_CLK2  0x4001b031
>                         MX6UL_PAD_JTAG_MOD__GPIO1_IO10
> 0x1b0b0
>                 >;
>         };

      parent reply	other threads:[~2019-10-24  3:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 20:10 fec driver: ethernet rx is deaf on variscite imx6ul board Oliver Graute
2019-10-23 20:28 ` Andrew Lunn
2019-10-24  3:08 ` Andy Duan [this message]

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=VI1PR0402MB360013E0A785313D5D676633FF6A0@VI1PR0402MB3600.eurprd04.prod.outlook.com \
    --to=fugang.duan@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-imx@nxp.com \
    --cc=netdev@vger.kernel.org \
    --cc=oliver.graute@gmail.com \
    /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.