From: 李志 <lizhi2@eswincomputing.com>
To: "Conor Dooley" <conor@kernel.org>
Cc: sashiko-reviews@lists.linux.dev, robh@kernel.org,
devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: Re: Re: [PATCH net v2 1/5] dt-bindings: ethernet: eswin: add optional TXD and RXD delay register offsets
Date: Fri, 22 May 2026 10:52:27 +0800 (GMT+08:00) [thread overview]
Message-ID: <1dd4d673.86ff.19e4d99369e.Coremail.lizhi2@eswincomputing.com> (raw)
In-Reply-To: <20260519-presuming-arrest-718fc461b055@spud>
> -----Original Messages-----
> From: "Conor Dooley" <conor@kernel.org>
> Send time:Tuesday, 19/05/2026 17:55:27
> To: 李志 <lizhi2@eswincomputing.com>
> Cc: sashiko-reviews@lists.linux.dev, robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
> Subject: Re: Re: [PATCH net v2 1/5] dt-bindings: ethernet: eswin: add optional TXD and RXD delay register offsets
>
> On Tue, May 19, 2026 at 05:51:05PM +0800, 李志 wrote:
> >
> >
> >
> > > -----Original Messages-----
> > > From: "Conor Dooley" <conor@kernel.org>
> > > Send time:Tuesday, 19/05/2026 17:11:59
> > > To: sashiko-reviews@lists.linux.dev
> > > Cc: lizhi2@eswincomputing.com, robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
> > > Subject: Re: [PATCH net v2 1/5] dt-bindings: ethernet: eswin: add optional TXD and RXD delay register offsets
> > >
> > > On Tue, May 19, 2026 at 02:23:33AM +0000, sashiko-bot@kernel.org wrote:
> > > > Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> > > > - [Medium] Missing `minItems: 4` constraint makes the newly added optional cells mandatory, breaking schema backward compatibility.
> > > > --
> > > >
> > > > commit 2992483df88af2823c275fc86187f7e38acbee5c
> > > > Author: Zhi Li <lizhi2@eswincomputing.com>
> > > >
> > > > dt-bindings: ethernet: eswin: add optional TXD and RXD delay register offsets
> > > >
> > > > This commit documents two optional cells in the eswin,hsp-sp-csr property
> > > > for the TXD and RXD delay control register offsets.
> > > >
> > > > > diff --git a/Documentation/devicetree/bindings/net/eswin,eic7700-eth.yaml b/Documentation/devicetree/bindings/net/eswin,eic7700-eth.yaml
> > > > > --- a/Documentation/devicetree/bindings/net/eswin,eic7700-eth.yaml
> > > > > +++ b/Documentation/devicetree/bindings/net/eswin,eic7700-eth.yaml
> > > >
> > > > [ ... ]
> > > >
> > > > > @@ -82,6 +91,8 @@ properties:
> > > > > - description: Offset of AXI clock controller Low-Power request
> > > > > register
> > > > > - description: Offset of register controlling TX/RX clock delay
> > > > > + - description: Optional offset of register controlling TXD delay
> > > > > + - description: Optional offset of register controlling RXD delay
> > > >
> > > > Will this make the two new offsets strictly required instead of optional?
> > > >
> > > > In dt-schema, when an items list defines a tuple, minItems implicitly
> > > > defaults to the total number of items in that list. By increasing the list
> > > > from 4 to 6 items without adding a minItems: 4 constraint to the inner items
> > > > list, won't validation now strictly require exactly 6 items?
> > > >
> > > > Could this cause dt_binding_check to fail for existing device trees that
> > > > correctly specify only the original 4 elements?
> > >
> > > Looks like a valid complaint to me.
> > > pw-bot: changes-requested
> > >
> > You're right, this is a valid issue.
> >
> > I'll fix it in v3 by adding only minItems: 4 to preserve backward
> > compatibility with existing 4-cell device trees.
> >
> > Should I drop your Acked-by in v3 due to the schema change, or should
> > it be retained?
>
> Just fix it, and you can retain.
Hi Conor,
I noticed that the v2 series has already been applied to net.git:
https://lore.kernel.org/lkml/177935821264.4013498.4647676520552839707.git-patchwork-notify@kernel.org/
Since the missing minItems: 4 breaks backward compatibility for
existing 4-cell device trees, I plan to send a new single-patch series
targeting net to add the missing constraint.
Just wanted to confirm that this is the preferred approach.
Thanks,
Zhi
next prev parent reply other threads:[~2026-05-22 2:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 2:19 [PATCH net v2 0/5] net: stmmac: eic7700: fix delay calculation and initialization ordering lizhi2
2026-05-18 2:20 ` [PATCH net v2 1/5] dt-bindings: ethernet: eswin: add optional TXD and RXD delay register offsets lizhi2
2026-05-19 2:23 ` sashiko-bot
2026-05-19 9:11 ` Conor Dooley
2026-05-19 9:51 ` 李志
2026-05-19 9:55 ` Conor Dooley
2026-05-22 2:52 ` 李志 [this message]
2026-05-22 16:02 ` Conor Dooley
2026-05-18 2:20 ` [PATCH net v2 2/5] net: stmmac: eswin: fix HSP CSR init ordering after clock enable lizhi2
2026-05-19 2:23 ` sashiko-bot
2026-05-19 9:58 ` 李志
2026-05-21 5:53 ` 李志
2026-05-18 2:21 ` [PATCH net v2 3/5] net: stmmac: eswin: clear TXD and RXD delay registers during initialization lizhi2
2026-05-18 2:21 ` [PATCH net v2 4/5] net: stmmac: eswin: correct RGMII delay granularity to 20 ps lizhi2
2026-05-18 2:22 ` [PATCH net v2 5/5] net: stmmac: eswin: validate RGMII delay values lizhi2
2026-05-21 10:10 ` [PATCH net v2 0/5] net: stmmac: eic7700: fix delay calculation and initialization ordering patchwork-bot+netdevbpf
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=1dd4d673.86ff.19e4d99369e.Coremail.lizhi2@eswincomputing.com \
--to=lizhi2@eswincomputing.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--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