From: Oliver Graute <oliver.graute@gmail.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: Anson Huang <anson.huang@nxp.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mripard@kernel.org" <mripard@kernel.org>,
"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
"dinguyen@kernel.org" <dinguyen@kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"olof@lixom.net" <olof@lixom.net>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
Leonard Crestez <leonard.crestez@nxp.com>,
"will@kernel.org" <will@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: defconfig: Change CONFIG_AT803X_PHY from m to y
Date: Tue, 26 Nov 2019 15:54:50 +0100 [thread overview]
Message-ID: <20191126145450.GB5108@optiplex> (raw)
In-Reply-To: <1572848275-30941-1-git-send-email-peng.fan@nxp.com>
On 04/11/19, Peng Fan wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> With phy-reset-gpios are enabled for i.MX8MM-EVK board, phy
> will be reset. Without CONFIG_AT803X_PHY as y, board will stop
> booting in NFS DHCP, because phy is not ready. So mark
> CONFIG_AT803X_PHY from m to y to make board boot when using nfs rootfs.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> arch/arm64/configs/defconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index c9a867ac32d4..cd778c9ea8a4 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -285,7 +285,7 @@ CONFIG_SNI_AVE=y
> CONFIG_SNI_NETSEC=y
> CONFIG_STMMAC_ETH=m
> CONFIG_MDIO_BUS_MUX_MMIOREG=y
> -CONFIG_AT803X_PHY=m
> +CONFIG_AT803X_PHY=y
> CONFIG_MARVELL_PHY=m
> CONFIG_MARVELL_10G_PHY=m
> CONFIG_MESON_GXL_PHY=m
> --
> 2.16.4
Hello Peng,
this patch broke my imx8qm nfs setup. With the generic phy driver my
board is booting fine. But with the AT803X_PHY=y enabled I'am running
into the following phy issue. So on my side it looks inverse as on
yours. What is the best proposal to fix this?
[ 5.550442] fec 5b040000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 5.573206] Sending DHCP requests ...... timed out!
[ 95.339702] IP-Config: Retrying forever (NFS root)...
[ 95.348873] Atheros 8035 ethernet 5b040000.ethernet-1:06: attached PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=5b040000.ethernet-1:06, irq=POLL)
[ 99.438443] fec 5b040000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 99.461206] Sending DHCP requests ...... timed out!
[ 174.419639] IP-Config: Retrying forever (NFS root)...
[ 174.428834] Atheros 8035 ethernet 5b040000.ethernet-1:06: attached PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=5b040000.ethernet-1:06, irq=POLL)
[ 178.542418] fec 5b040000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 178.565206] Sending DHCP requests .....
[ 209.261271] random: crng init done
[ 230.565202] . timed out!
[ 260.577340] IP-Config: Retrying forever (NFS root)...
[ 260.586497] Atheros 8035 ethernet 5b040000.ethernet-1:06: attached PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=5b040000.ethernet-1:06, irq=POLL)
[ 264.686438] fec 5b040000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 264.709206] Sending DHCP requests ...... timed out!
[ 339.259701] IP-Config: Retrying forever (NFS root)...
[ 339.268835] Atheros 8035 ethernet 5b040000.ethernet-1:06: attached PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=5b040000.ethernet-1:06, irq=POLL)
[ 343.374422] fec 5b040000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 343.405206] Sending DHCP requests ...... timed out!
[ 433.171676] IP-Config: Retrying forever (NFS root)...
[ 433.180842] Atheros 8035 ethernet 5b040000.ethernet-1:06: attached PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=5b040000.ethernet-1:06, irq=POLL)
[ 437.294439] fec 5b040000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 437.317206] Sending DHCP requests ...... timed out!
[ 509.003660] IP-Config: Retrying forever (NFS root)...
[ 509.012836] Atheros 8035 ethernet 5b040000.ethernet-1:06: attached PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=5b040000.ethernet-1:06, irq=POLL)
[ 513.102416] fec 5b040000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
Best Regards,
Oliver
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-26 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 6:19 [PATCH] arm64: defconfig: Change CONFIG_AT803X_PHY from m to y Peng Fan
2019-11-04 7:26 ` Shawn Guo
2019-11-26 14:54 ` Oliver Graute [this message]
2019-11-27 8:47 ` Marc Gonzalez
2019-11-27 12:46 ` Oliver Graute
2019-11-27 12:56 ` Fabio Estevam
2019-11-28 10:06 ` Oliver Graute
2019-11-28 9:11 ` Marc Gonzalez
2019-11-28 12:16 ` Oliver Graute
2019-12-02 8:38 ` Shawn Guo
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=20191126145450.GB5108@optiplex \
--to=oliver.graute@gmail.com \
--cc=anson.huang@nxp.com \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=dinguyen@kernel.org \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=olof@lixom.net \
--cc=peng.fan@nxp.com \
--cc=shawnguo@kernel.org \
--cc=will@kernel.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