From: Nishanth Menon <nm@ti.com>
To: Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: <vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <u-kumar1@ti.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <srk@ti.com>
Subject: Re: [PATCH 0/2] J722S: DT Node cleanup for serdes0 and serdes1
Date: Mon, 14 Apr 2025 09:39:16 -0500 [thread overview]
Message-ID: <20250414143916.zhskssezbffmvnsz@dragonfly> (raw)
In-Reply-To: <79ef7f50-22d5-4c40-ae28-02bf297ca79c@ti.com>
On 18:30-20250414, Siddharth Vadapalli wrote:
> On Mon, Apr 14, 2025 at 07:09:30AM -0500, Nishanth Menon wrote:
>
> Hello Nishanth,
>
> > On 10:57-20250412, Siddharth Vadapalli wrote:
> > > Hello,
> > >
> > > This series is based on the following series:
> > > https://patchwork.kernel.org/project/linux-arm-kernel/cover/20250408103606.3679505-1-s-vadapalli@ti.com/
> > > Based on the discussion in the above series which disabled 'serdes_wiz0'
> > > and 'serdes_wiz1' nodes in the SoC file and enabled them in the board
> > > file, Udit pointed out that it wasn't necessary to disable 'serdes0' and
> > > 'serdes1' in the SoC file anymore, since that is not a working
> > > configuration - serdes_wizX enabled and serdesX disabled doesn't work.
> > >
> > > Hence, this series aims to cleanup the serdesX nodes after the changes
> > > made by the above series.
> > >
> > > Regards,
> > > Siddharth.
> > >
> > > Siddharth Vadapalli (2):
> > > arm64: dts: ti: k3-j722s-main: don't disable serdes0 and serdes1
> > > arm64: dts: ti: k3-j722s-evm: drop redundant status within
> > > serdes0/serdes1
> > >
> > > arch/arm64/boot/dts/ti/k3-j722s-evm.dts | 2 --
> > > arch/arm64/boot/dts/ti/k3-j722s-main.dtsi | 4 ----
> > > 2 files changed, 6 deletions(-)
> > >
> > > --
> > > 2.34.1
> > >
> >
> >
> > I do not understand the logic here. serdes cannot operate without wiz
> > nodes, correct? why would we leave serdes on by default?
>
> Yes, serdesX requires serdes_wizX, but at the same time, serdesX is the
> child node of serdes_wizX. Therefore, without enabling serdes_wizX, we
> cannot enable serdesX.
>
> Prior to this series, but with the dependent series at:
> https://patchwork.kernel.org/project/linux-arm-kernel/cover/20250408103606.3679505-1-s-vadapalli@ti.com/
> applied, the nodes look like:
>
> serdes_wizX {
> ...
> status = "disabled";
>
> serdesX {
> ...
> status = "disabled";
> };
> };
>
> The dependent series fixes 'serdes_wizX' by disabling it in the SoC file
> k3-j722s-main.dtsi. But after the fix, we have a 'status = "disabled";'
> within the serdesX node which isn't required since:
> a) serdes_wizX enabled but serdesX disabled is non-functional and
> unusable
> b) serdes_wizX disabled in DT implies that serdesX is also disabled
Can we handle all of this in one series instead of two series?
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2025-04-14 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 5:27 [PATCH 0/2] J722S: DT Node cleanup for serdes0 and serdes1 Siddharth Vadapalli
2025-04-12 5:27 ` [PATCH 1/2] arm64: dts: ti: k3-j722s-main: don't disable " Siddharth Vadapalli
2025-04-12 5:27 ` [PATCH 2/2] arm64: dts: ti: k3-j722s-evm: drop redundant status within serdes0/serdes1 Siddharth Vadapalli
2025-04-13 9:48 ` [PATCH 0/2] J722S: DT Node cleanup for serdes0 and serdes1 Kumar, Udit
2025-04-14 12:09 ` Nishanth Menon
2025-04-14 13:00 ` Siddharth Vadapalli
2025-04-14 14:39 ` Nishanth Menon [this message]
2025-04-14 14:43 ` Siddharth Vadapalli
2025-04-17 12:34 ` 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=20250414143916.zhskssezbffmvnsz@dragonfly \
--to=nm@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=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.com \
--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