mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Manni Stefano" <stefano.manni@eletechsrl.it>
To: s.hauer@pengutronix.de
Cc: barebox@lists.infradead.org,
	Aurelio Colosimo <aurelio@aureliocolosimo.it>
Subject: imx6ul: fec: stuck on ifup after ifdown
Date: Mon, 5 Oct 2020 14:43:15 +0200	[thread overview]
Message-ID: <005d01d69b15$180b4aa0$4821dfe0$@eletechsrl.it> (raw)

Hi,

on a custom board based on a i.MX6UL using barebox v2020.08.1 'ifup eth0'
invoked after 'ifdown eth0' stucks forever.

Have you ever experienced something similar?

Snippet from my device tree:

        &fec1 {
                pinctrl-names = "default";
                pinctrl-0 = <&pinctrl_enet1>;
                phy-mode = "rmii";
                phy-handle = <&ethphy1>;
                status = "okay";
                phy-reset-gpios = <&gpio1 23 GPIO_ACTIVE_LOW>;
                phy-reset-duration = <1>;

                mdio {
                        #address-cells = <1>;
                        #size-cells = <0>;

                        clock-frequency = <5000000>;
                        ethphy1: ethernet-phy@1 {
                                compatible = "ethernet-phy-ieee802.3-c22";
                                reg = <0>;
                                max-speed = <100>;
                                interrupt-parent = <&gpio1>;
                                interrupts = <22 IRQ_TYPE_LEVEL_LOW>;
                        };
                };
        };

        pinctrl_enet1: enet1grp {
                fsl,pins = <
                        MX6UL_PAD_GPIO1_IO06__ENET1_MDIO        0x1b0b0
                        MX6UL_PAD_GPIO1_IO07__ENET1_MDC         0x1b0b0
                        MX6UL_PAD_ENET1_TX_DATA0__ENET1_TDATA00 0x1b0b0
                        MX6UL_PAD_ENET1_TX_DATA1__ENET1_TDATA01 0x1b0b0
                        MX6UL_PAD_ENET1_TX_EN__ENET1_TX_EN      0x1b0b0
                        MX6UL_PAD_ENET1_TX_CLK__ENET1_REF_CLK1  0x4001b031
                        MX6UL_PAD_ENET1_RX_DATA0__ENET1_RDATA00 0x1b0b0
                        MX6UL_PAD_ENET1_RX_DATA1__ENET1_RDATA01 0x1b0b0
                        MX6UL_PAD_ENET1_RX_EN__ENET1_RX_EN      0x1b0b0
                        MX6UL_PAD_ENET1_RX_ER__ENET1_RX_ER      0x1b0b0
                        MX6UL_PAD_UART2_RTS_B__GPIO1_IO23       0x1b0b0
                        MX6UL_PAD_UART2_CTS_B__GPIO1_IO22       0x1b0b0
                >;
        };

Best,
Stefano


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2020-10-05 12:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 12:43 Manni Stefano [this message]
2020-10-05 15:17 ` Sascha Hauer
2020-10-06  8:44   ` Lucas Stach
2020-10-06  9:58     ` Sascha Hauer

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='005d01d69b15$180b4aa0$4821dfe0$@eletechsrl.it' \
    --to=stefano.manni@eletechsrl.it \
    --cc=aurelio@aureliocolosimo.it \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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