From: Conor Dooley <conor@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: sashiko-reviews@lists.linux.dev, robh@kernel.org,
vkoul@kernel.org, neil.armstrong@linaro.org, conor+dt@kernel.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
olteanv@gmail.com
Subject: Re: [PATCH v3 phy-next 14/16] dt-bindings: phy: lynx-10g: initial document
Date: Wed, 3 Jun 2026 16:50:39 +0100 [thread overview]
Message-ID: <20260603-numerate-unbundle-ef259832006d@spud> (raw)
In-Reply-To: <20260603133825.l544tnmtn2pqfrzh@skbuf>
[-- Attachment #1: Type: text/plain, Size: 2916 bytes --]
On Wed, Jun 03, 2026 at 04:38:25PM +0300, Vladimir Oltean wrote:
> On Wed, Jun 03, 2026 at 01:33:50PM +0000, sashiko-bot@kernel.org wrote:
> > Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> > - [Medium] The `if` condition for enforcing the `big-endian` property incorrectly matches the `compatible` string array directly against an `enum`, which will always evaluate to false and cause the requirement to silently fail.
> > --
> >
> > commit 8bd3982a89722b20a3686e42d4ab3b9f0711ae11
> > Author: Vladimir Oltean <vladimir.oltean@nxp.com>
> >
> > dt-bindings: phy: lynx-10g: initial document
> >
> > This commit adds the schema for the 10G Lynx SerDes used on most QorIQ and
> > Layerscape SoCs. It defines the valid compatible strings, PHY cell requirements,
> > and enforces SoC-specific constraints such as lane counts and endianness.
> >
> > > diff --git a/Documentation/devicetree/bindings/phy/fsl,lynx-10g.yaml b/Documentation/devicetree/bindings/phy/fsl,lynx-10g.yaml
> > > new file mode 100644
> > > index 0000000000000..8cf6027a75b91
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/phy/fsl,lynx-10g.yaml
> > > + - if:
> > > + properties:
> > > + compatible:
> > > + enum:
> > > + - fsl,ls1046a-serdes1
> > > + - fsl,ls1046a-serdes2
> >
> > [Severity: Medium]
> > Does this conditional correctly enforce the big-endian property?
> >
> > Since the compatible property is a string array in device trees, evaluating it
> > directly against an enum always returns false. Should this use "contains:"
> > with the enum, similar to the preceding if block, so dt_binding_check
> > correctly enforces the requirement?
>
> The tests I did suggest that it does enforce the requirement.
Yeah, sashiko just doesn't understand how this works without "contains".
"contains" is only actually required for validation purposes if there's
fallback compatibles and you're trying to get a partial match.
>
> - "make dt_binding_check" passes with the submitted example
>
> - If I replace "fsl,ls1028a-serdes" from the example with
> "fsl,ls1046a-serdes1" but leave everything else as is (implying:
> little endian), I get:
>
> $ make -j 8 DT_CHECKER_FLAGS=-m dt_binding_check DT_SCHEMA_FILES=phy/fsl,lynx-10g.yaml
> SCHEMA Documentation/devicetree/bindings/processed-schema.json
> CHKDT ../Documentation/devicetree/bindings
> LINT ../Documentation/devicetree/bindings
> DTEX Documentation/devicetree/bindings/phy/fsl,lynx-10g.example.dts
> DTC [C] Documentation/devicetree/bindings/phy/fsl,lynx-10g.example.dtb
> Documentation/devicetree/bindings/phy/fsl,lynx-10g.example.dtb: serdes@1ea0000 (fsl,ls1046a-serdes1): 'big-endian' is a required property
> from schema $id: http://devicetree.org/schemas/phy/fsl,lynx-10g.yaml
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-06-03 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260603131914.503053-1-vladimir.oltean@nxp.com>
2026-06-03 13:20 ` [PATCH v3 phy-next 14/16] dt-bindings: phy: lynx-10g: initial document Vladimir Oltean
2026-06-03 13:33 ` sashiko-bot
2026-06-03 13:38 ` Vladimir Oltean
2026-06-03 15:50 ` Conor Dooley [this message]
2026-06-03 13:21 ` [PATCH v3 phy-next 15/16] phy: lynx-10g: new driver Vladimir Oltean
2026-06-03 13:21 ` [PATCH v3 phy-next 16/16] MAINTAINERS: expand Lynx 28G entry to cover Lynx 10G SerDes Vladimir Oltean
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=20260603-numerate-unbundle-ef259832006d@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@kernel.org \
--cc=vladimir.oltean@nxp.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