From: sashiko-bot@kernel.org
To: "Heiner Kallweit" <hkallweit1@gmail.com>
Cc: Frank.Li@kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH] ARM: imx6q: remove KSZ9021 PHY fixup
Date: Sat, 15 Aug 2026 15:40:18 +0000 [thread overview]
Message-ID: <20260815154019.22C0E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <8fdc784c-5e2b-40ac-aed8-7639f43df88d@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Removing the KSZ9021 PHY fixup breaks backward compatibility with older Device Trees, causing Ethernet to fail.
--
--- Patch [1]: [PATCH] ARM: imx6q: remove KSZ9021 PHY fixup ---
commit 043c886239c15d5e6801536fd77e59f0f71dbb60
Author: Heiner Kallweit <hkallweit1@gmail.com>
ARM: imx6q: remove KSZ9021 PHY fixup
This commit removes the board-level PHY fixup for the KSZ9021 Ethernet PHY
on i.MX6Q boards, which was originally added to configure RGMII pad skew.
The commit notes that OF configuration support was added in 2013, making
the board-level fixup theoretically redundant.
> diff --git a/arch/arm/mach-imx/mach-imx6q.c b/arch/arm/mach-imx/mach-imx6q.c
> index 7f62009257526..58f53fba202f4 100644
> --- a/arch/arm/mach-imx/mach-imx6q.c
> +++ b/arch/arm/mach-imx/mach-imx6q.c
[ ... ]
> -static void __init imx6q_enet_phy_init(void)
> -{
> - if (IS_BUILTIN(CONFIG_PHYLIB)) {
> - phy_register_fixup_for_uid(PHY_ID_KSZ9021, MICREL_PHY_ID_MASK,
> - ksz9021rn_phy_fixup);
> - }
> -}
> -
[Severity: High]
Will removing this fixup break Ethernet for users booting with older Device
Trees that lack the explicit skew-ps properties?
The Linux kernel generally treats the Device Tree as a stable ABI. Older
DTBs implicitly relied on this board-level fixup to set the necessary PHY
delays because the KSZ9021 PHY driver only sets RGMII pad skew registers
if explicit *-skew-ps properties are present. It does not apply default
delays based solely on the phy-mode.
If a system boots an affected board (like Sabrelite) with an older DTB,
could this omission cause Ethernet communication to fail unconditionally?
To preserve backward compatibility while still removing it for unaffected
boards, would it be better to conditionally apply the fixup using
of_machine_is_compatible() instead of removing it entirely?
--
Sashiko AI review · https://sashiko.dev/#/patchset/8fdc784c-5e2b-40ac-aed8-7639f43df88d@gmail.com?part=1
prev parent reply other threads:[~2026-08-15 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 15:32 [PATCH] ARM: imx6q: remove KSZ9021 PHY fixup Heiner Kallweit
2026-08-15 15:40 ` sashiko-bot [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=20260815154019.22C0E1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=imx@lists.linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
/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