From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: "Kumar, Udit" <u-kumar1@ti.com>
Cc: Siddharth Vadapalli <s-vadapalli@ti.com>, <nm@ti.com>,
<vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <rogerq@kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<srk@ti.com>
Subject: Re: [PATCH v2 2/2] arm64: dts: ti: k3-j722s-main: Disable "serdes_wiz0" and "serdes_wiz1"
Date: Fri, 11 Apr 2025 19:47:35 +0530 [thread overview]
Message-ID: <475a1ac1-abb1-4c6e-b5b2-3f1a3399d5c4@ti.com> (raw)
In-Reply-To: <7b2f69ad-48aa-4aa9-be0e-f0edae272bdb@ti.com>
On Fri, Apr 11, 2025 at 07:31:52PM +0530, Kumar, Udit wrote:
Hello Udit,
>
> On 4/8/2025 4:06 PM, Siddharth Vadapalli wrote:
> > Since "serdes0" and "serdes1" which are the sub-nodes of "serdes_wiz0"
> > and "serdes_wiz1" respectively, have been disabled in the SoC file already,
> > and, given that these sub-nodes will only be enabled in a board file if the
> > board utilizes any of the SERDES instances and the peripherals bound to
> > them, we end up in a situation where the board file doesn't explicitly
> > disable "serdes_wiz0" and "serdes_wiz1". As a consequence of this, the
> > following errors show up when booting Linux:
> >
> > wiz bus@f0000:phy@f000000: probe with driver wiz failed with error -12
> > ...
> > wiz bus@f0000:phy@f010000: probe with driver wiz failed with error -12
> >
> > To not only fix the above, but also, in order to follow the convention of
> > disabling device-tree nodes in the SoC file and enabling them in the board
> > files for those boards which require them, disable "serdes_wiz0" and
> > "serdes_wiz1" device-tree nodes.
> >
> > Fixes: 628e0a0118e6 ("arm64: dts: ti: k3-j722s-main: Add SERDES and PCIe support")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
> > ---
> >
> > v1 of this patch is at:
> > https://lore.kernel.org/r/20250408060636.3413856-3-s-vadapalli@ti.com/
> > Changes since v1:
> > - Added "Fixes" tag and updated commit message accordingly.
> >
> > Regards,
> > Siddharth.
> >
> > arch/arm64/boot/dts/ti/k3-j722s-main.dtsi | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/ti/k3-j722s-main.dtsi b/arch/arm64/boot/dts/ti/k3-j722s-main.dtsi
> > index 6850f50530f1..beda9e40e931 100644
> > --- a/arch/arm64/boot/dts/ti/k3-j722s-main.dtsi
> > +++ b/arch/arm64/boot/dts/ti/k3-j722s-main.dtsi
> > @@ -32,6 +32,8 @@ serdes_wiz0: phy@f000000 {
> > assigned-clocks = <&k3_clks 279 1>;
> > assigned-clock-parents = <&k3_clks 279 5>;
> > + status = "disabled";
> > +
>
> Since you are disabling parent node.
>
> Do you still want to carry status = "disabled" in child nodes serdes0 and
> serdes1.
I could drop it, but then the patches will look something like:
1) Patch 1: Same as the first patch in this series
2) Patch 2: Current patch + Remove status = "disabled" within serdes0/1
3) Patch 3: Removed redundant status = "okay" within serdes0/1 in
k3-j722s-evm.dts
Updated Patch 2 and the new Patch 3 mentioned above aren't necessarily a
complete "Fix" and have other changes in addition to the "Fix". For that
reason, the changes associated with the updated patch 2 and the new patch 3
could be a separate series, unless you believe that they should go
together in the current series. Please let me know.
Regards,
Siddharth.
next prev parent reply other threads:[~2025-04-11 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 10:36 [PATCH v2 0/2] J722S: Disable WIZ0 and WIZ1 in SoC file Siddharth Vadapalli
2025-04-08 10:36 ` [PATCH v2 1/2] arm64: dts: ti: k3-j722s-evm: Enable "serdes_wiz0" and "serdes_wiz1" Siddharth Vadapalli
2025-04-11 13:56 ` Kumar, Udit
2025-04-08 10:36 ` [PATCH v2 2/2] arm64: dts: ti: k3-j722s-main: Disable " Siddharth Vadapalli
2025-04-11 14:01 ` Kumar, Udit
2025-04-11 14:17 ` Siddharth Vadapalli [this message]
2025-04-11 15:52 ` Kumar, Udit
2025-04-12 5:33 ` Siddharth Vadapalli
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=475a1ac1-abb1-4c6e-b5b2-3f1a3399d5c4@ti.com \
--to=s-vadapalli@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=srk@ti.com \
--cc=stable@vger.kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
/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®