Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Alexander Stein" <alexander.stein@ew.tq-group.com>
Cc: imx@lists.linux.dev, devicetree@vger.kernel.org, robh@kernel.org,
	conor+dt@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v2 1/5] dt-bindings: firmware: imx: Add SCU controlled display pixel link nodes
Date: Wed, 14 Oct 2026 07:24:09 +0000	[thread overview]
Message-ID: <sashiko-outbox-170937@kernel.org> (raw)
In-Reply-To: <20261014071657.118378-2-alexander.stein@ew.tq-group.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: firmware: fsl,scu: enforces non-generic child node names
--

commit bc38a98038b8a49cd066c13a1783d4225b66e234
Author: Liu Ying <victor.liu@nxp.com>

dt-bindings: firmware: imx: Add SCU controlled display pixel link nodes

This commit documents the SCU controlled display pixel link child nodes 
in the fsl,scu firmware binding.

> diff --git a/Documentation/devicetree/bindings/firmware/fsl,scu.yaml b/Documentation/devicetree/bindings/firmware/fsl,scu.yaml
> index 307f1c6278532..cd6cda1192a89 100644
> --- a/Documentation/devicetree/bindings/firmware/fsl,scu.yaml
> +++ b/Documentation/devicetree/bindings/firmware/fsl,scu.yaml
> @@ -30,6 +30,26 @@ properties:
>        Clock controller node that provides the clocks controlled by the SCU
>      $ref: /schemas/clock/fsl,scu-clk.yaml
>  
> +  dc0-pixel-link0:
> +    description:
> +      Display pixel link0 in display controller subsystem0 controlled by the SCU
> +    $ref: /schemas/display/bridge/fsl,imx8qxp-pixel-link.yaml

[Severity: Low]
Does this naming scheme violate the Devicetree Specification Section 2.2
(Generic Names Recommendation)?

The specification recommends that node names reflect the general function
of the device and avoid hardware-specific programming models or block indices.
Enforcing exact node names like dc0-pixel-link0 prevents device tree sources
from using generic names.

Looking at the SCU firmware driver in drivers/firmware/imx/imx-scu.c, child
nodes are populated using devm_of_platform_populate(), and the downstream
bridge driver in drivers/gpu/drm/bridge/imx/imx8qxp-pixel-link.c binds using
the compatible string (fsl,imx8qxp-dc-pixel-link), not the node name. 

Since there is no driver or firmware ABI requirement dictating these fixed
node names, would it be better to use patternProperties, for example
^pixel-link(-[0-9]+)?$, to allow and validate generic naming?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261014071657.118378-1-alexander.stein@ew.tq-group.com?part=1

  reply	other threads:[~2026-10-14  7:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  7:16 [PATCH v2 0/5] LVDS support for TQMa8Xx Alexander Stein
2026-10-14  7:16 ` [PATCH v2 1/5] dt-bindings: firmware: imx: Add SCU controlled display pixel link nodes Alexander Stein
2026-10-14  7:24   ` sashiko-bot [this message]
2026-10-14  9:39     ` Alexander Stein
2026-10-14  7:16 ` [PATCH v2 2/5] arm64: dts: imx8qxp: Add display controller subsystem Alexander Stein
2026-10-14 13:55   ` Frank Li
2026-10-14  7:16 ` [PATCH v2 3/5] arm64: dts: imx8qxp: Add MIPI-LVDS combo subsystems Alexander Stein
2026-10-14  7:29   ` sashiko-bot
2026-10-14  9:25     ` Alexander Stein
2026-10-14 14:01   ` Frank Li
2026-10-14  7:16 ` [PATCH v2 4/5] arm64: dts: freescale: Add LVDS overlays for TQMa8Xx Alexander Stein
2026-10-14  7:16 ` [PATCH v2 5/5] arm64: dts: freescale: Add dual-channel LVDS overlay " Alexander Stein

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=sashiko-outbox-170937@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --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