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>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: imx6ul: Recent enet refclock changes breaks custom i.mx6ull board
Date: Mon, 6 Mar 2023 10:13:57 +0100 [thread overview]
Message-ID: <8a178040-ef52-d9ab-e704-69208d34f915@i2se.com> (raw)
In-Reply-To: <20230306052531.GA30081@pengutronix.de>
Hi Oleksij,
Am 06.03.23 um 06:25 schrieb Oleksij Rempel:
> Hi Stefan,
>
> On Sun, Mar 05, 2023 at 11:16:17PM +0100, Stefan Wahren wrote:
>> 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.
> It looks like in your kernel version are some missing patches. Can you please
> rebase your patches on top of this branch:
> https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git/log/?h=for-next
thanks for your fast reply. But i rebased my patches against Linux
v6.3-rc1 since this was released yesterday and should contain all
patches from Shawn. I also changed the clockref in my DTSI file:
https://github.com/chargebyte/linux/commits/v6.3-tarragon-v3
Now the PHY issue disappeared and ethernet is working, but the
imx:clk-gpr-mux: failed to get parent (-EINVAL)
is still there.
> and please rename IMX6UL_CLK_ENET_REF to IMX6UL_CLK_ENET1_REF_SEL in
> your dtsi.
Yes, this seems to be the issue in my case.
Does this mean a Linux 6.3 kernel doesn't work with a i.MX6ULL Linux 6.2
devicetree?
So there is no fallback?
What about these other dtsi in Linux 6.3rc-1?
$ grep IMX6UL_CLK_ENET_REF *
imx6ul-14x14-evk.dtsi: clocks = <&clks IMX6UL_CLK_ENET_REF>;
..
imx6ul-kontron-bl-common.dtsi: clocks = <&clks
IMX6UL_CLK_ENET_REF>;
imx6ul-kontron-sl-common.dtsi: clocks = <&clks
IMX6UL_CLK_ENET_REF>;
imx6ull-dhcom-picoitx.dts: clocks = <&clks IMX6UL_CLK_ENET_REF>;
imx6ull-dhcom-som.dtsi: clocks = <&clks IMX6UL_CLK_ENET_REF>;
imx6ull-jozacp.dts: clocks = <&clks IMX6UL_CLK_ENET_REF>;
imx6ull-myir-mys-6ulx.dtsi: clocks = <&clks IMX6UL_CLK_ENET_REF>;
imx6ul-phytec-phycore-som.dtsi: clocks = <&clks
IMX6UL_CLK_ENET_REF>;
mba6ulx.dtsi: clocks = <&clks IMX6UL_CLK_ENET_REF>;
>
> Regards,
> Oleksij
next prev parent reply other threads:[~2023-03-06 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 22:16 imx6ul: Recent enet refclock changes breaks custom i.mx6ull board Stefan Wahren
2023-03-06 5:25 ` Oleksij Rempel
2023-03-06 9:13 ` Stefan Wahren [this message]
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=8a178040-ef52-d9ab-e704-69208d34f915@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=abelvesa@kernel.org \
--cc=arnd@arndb.de \
--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