From: Andrew Lunn <andrew@lunn.ch>
To: Josef Schlehofer <pepe.schlehofer@gmail.com>
Cc: "Madhavan Srinivasan" <maddy@linux.ibm.com>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Christophe Leroy" <chleroy@kernel.org>,
"Ritesh Harjani" <ritesh.list@gmail.com>,
"Shrikanth Hegde" <sshegde@linux.ibm.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Pali Rohár" <pali@kernel.org>, "Marek Behún" <kabel@kernel.org>,
devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] powerpc: dts: turris1x.dts: Describe switch PHYs on the MDIO bus
Date: Sun, 18 Oct 2026 17:51:04 +0200 [thread overview]
Message-ID: <cb96159f-c510-49ab-bc1d-20149222781a@lunn.ch> (raw)
In-Reply-To: <20261018015311.4822-1-pepe.schlehofer@gmail.com>
On Sun, Oct 18, 2026 at 03:53:11AM +0200, Josef Schlehofer wrote:
> The QCA8337's integrated PHYs are visible on the same MDIO bus as the
> KSZ9031, at addresses 0–4. Since they are not described in the device
> tree, qca8k accesses them through the switch's MDIO master.
>
> Describe the PHYs and reference them from the switch ports so phylib
> accesses them directly through the MDIO bus. This fixes intermittent
> WAN link recovery failures on Turris 1.x.
>
> Tested on Turris 1.1: 40 WAN link down/up cycles across 3 boots and
> 10 LAN link down/up cycles passed.
>
> Fixes: 54c15ec3b738 ("powerpc: dts: Add DTS file for CZ.NIC Turris 1.x routers")
> Cc: stable@vger.kernel.org
> Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
prev parent reply other threads:[~2026-10-18 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 1:53 Josef Schlehofer
2026-10-18 15:51 ` Andrew Lunn [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=cb96159f-c510-49ab-bc1d-20149222781a@lunn.ch \
--to=andrew@lunn.ch \
--cc=chleroy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kabel@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=pali@kernel.org \
--cc=pepe.schlehofer@gmail.com \
--cc=ritesh.list@gmail.com \
--cc=robh@kernel.org \
--cc=sshegde@linux.ibm.com \
--cc=stable@vger.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
all inboxes | Powered by JetHome®