From: Stefan Wahren <stefan.wahren@i2se.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Abel Vesa <abelvesa@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Michael Heimpold <mhei@heimpold.de>
Subject: imx6ul: Recent enet refclock changes breaks custom i.mx6ull board
Date: Sun, 5 Mar 2023 23:16:17 +0100 [thread overview]
Message-ID: <3ceda169-de1b-2c1f-9ee8-bc8fdb547433@i2se.com> (raw)
Hi,
we planned to submit our custom i.MX6ULL board [1] to mainline after
release of Linux 6.3-rc1, but the recent enet refclock changes breaks
our Ethernet phy:
[ 0.000000] imx:clk-gpr-mux: failed to get parent (-EINVAL)
...
[ 18.574595] SMSC LAN8710/LAN8720 2188000.ethernet-1:00:
phy_poll_reset failed: -110
[ 18.581064] fec 2188000.ethernet eth0: Unable to connect to phy
I narrow down the PHY issue to this first bad commit:
5f82bfced611 ("clk: imx6ul: fix enet1 gate configuration")
The clock issues seems to be cause by the following commit. If i revert
5f82bfced611 and 4e197ee880c24 or use Linux 6.2 everything is fine.
Maybe this helps for further analyse:
--- clk_summary.good 2023-03-05 22:41:52.607392458 +0100
+++ clk_summary.bad 2023-03-05 22:41:52.587391697 +0100
@@ -46,12 +46,13 @@
usbphy2 0 0 0
480000000 0 0 50000 N
pll6 1 1 0
500000000 0 0 50000 Y
pll6_bypass 1 1 0
500000000 0 0 50000 Y
- pll6_enet 2 2 0
500000000 0 0 50000 Y
- enet_ptp_ref 1 1 0
25000000 0 0 50000 Y
- enet_ptp 1 1 0
25000000 0 0 50000 Y
+ pll6_enet 1 1 0
500000000 0 0 50000 Y
+ enet_ptp_ref 0 0 0
25000000 0 0 50000 Y
+ enet_ptp 0 0 0
25000000 0 0 50000 N
enet2_ref 0 0 0
50000000 0 0 50000 Y
- enet_ref_125m 0 0 0
50000000 0 0 50000 N
- enet_ref 3 3 0
50000000 0 0 50000 Y
+ enet2_ref_125m 0 0 0
50000000 0 0 50000 N
+ enet1_ref 1 1 0
50000000 0 0 50000 Y
+ enet1_ref_125m 0 0 0
50000000 0 0 50000 N
pll5 0 0 0
296600000 0 0 50000 Y
pll5_bypass 0 0 0
296600000 0 0 50000 Y
pll5_video 0 0 0
296600000 0 0 50000 N
@@ -137,19 +138,19 @@
step 0 0 0
528000000 0 0 50000 Y
periph_pre 1 1 0
528000000 0 0 50000 Y
periph 3 3 0
528000000 0 0 50000 Y
- ahb 9 9 0
132000000 0 0 50000 Y
+ ahb 8 8 0
132000000 0 0 50000 Y
sdma 4 1 0
132000000 0 0 50000 Y
rom 1 1 0
132000000 0 0 50000 Y
esai_mem 0 0 0
132000000 0 0 50000 N
esai_ipg 0 0 0
132000000 0 0 50000 N
aips_tz3 1 1 0
132000000 0 0 50000 Y
- enet_ahb 1 1 0
132000000 0 0 50000 Y
+ enet_ahb 0 0 0
132000000 0 0 50000 N
dcp 1 1 0
132000000 0 0 50000 Y
asrc_mem 0 0 0
132000000 0 0 50000 N
asrc_ipg 0 0 0
132000000 0 0 50000 N
aips_tz2 1 1 0
132000000 0 0 50000 Y
aips_tz1 1 1 0
132000000 0 0 50000 Y
- ipg 15 13 0
66000000 0 0 50000 Y
+ ipg 14 12 0
66000000 0 0 50000 Y
wdog3 0 0 0
66000000 0 0 50000 N
uart8_ipg 0 0 0
66000000 0 0 50000 N
usboh3 0 0 0
66000000 0 0 50000 N
@@ -180,7 +181,7 @@
uart2_ipg 0 0 0
66000000 0 0 50000 N
can2_ipg 0 0 0
66000000 0 0 50000 N
can1_ipg 0 0 0
66000000 0 0 50000 N
- enet 1 1 0
66000000 0 0 50000 Y
+ enet 0 0 0
66000000 0 0 50000 N
axi_sel 1 1 0
528000000 0 0 50000 Y
axi_podf 2 2 0
264000000 0 0 50000 Y
axi 1 1 0
264000000 0 0 50000 Y
[1] -
https://github.com/chargebyte/linux/commit/5f47f1b029d34391a4b24d4a30105f517126363e#diff-a3def31334aa0f3b641ed5b21a60b462a9cbdda064e7276770be22d9860f2ae7R137
next reply other threads:[~2023-03-05 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 22:16 Stefan Wahren [this message]
2023-03-06 5:25 ` imx6ul: Recent enet refclock changes breaks custom i.mx6ull board Oleksij Rempel
2023-03-06 9:13 ` Stefan Wahren
2023-03-06 9:47 ` Oleksij Rempel
2023-03-06 13:33 ` Stefan Wahren
2023-03-06 14:02 ` Oleksij Rempel
2023-03-06 15:50 ` Stefan Wahren
2023-03-07 6:06 ` Oleksij Rempel
2023-03-08 15:11 ` Stefan Wahren
2023-03-09 16:59 ` Stefan Wahren
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=3ceda169-de1b-2c1f-9ee8-bc8fdb547433@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=abelvesa@kernel.org \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=mhei@heimpold.de \
--cc=o.rempel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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