Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Guoniu Zhou" <guoniu.zhou@oss.nxp.com>
Cc: devicetree@vger.kernel.org, Frank.Li@kernel.org,
	conor+dt@kernel.org, imx@lists.linux.dev, robh@kernel.org
Subject: Re: [PATCH v9 2/3] media: dt-bindings: Add CSI Pixel Formatter DT bindings
Date: Tue, 26 May 2026 09:18:47 +0000	[thread overview]
Message-ID: <20260526091847.CFCB31F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260526-csi_formatter-v9-2-ca3d8c334c39@oss.nxp.com>

Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [Low] Unit address mismatch in the example's syscon parent node.
- [Low] Missing 'ranges' property in the parent syscon node in the example.
- [Low] Poor formatting in the device tree example block.
--

commit 1b3ddadbdea2fb3bc19aa036199bd1e0ef56413b
Author: Guoniu Zhou <guoniu.zhou@nxp.com>

media: dt-bindings: Add CSI Pixel Formatter DT bindings

This commit adds the device tree binding schema for the i.MX95 CSI pixel
formatter module. It defines the constraints and ports required to interface
the CSI-2 host controller with the Pixel Link definition.

> diff --git a/Documentation/devicetree/bindings/media/fsl,imx95-csi-formatter.yaml b/Documentation/devicetree/bindings/media/fsl,imx95-csi-formatter.yaml
> new file mode 100644
> index 0000000000000..61068ea0a69a0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/fsl,imx95-csi-formatter.yaml
[ ... ]
> +examples:
> +  - |
> +    #include <dt-bindings/clock/nxp,imx95-clock.h>
> +
> +    syscon@4c100000 {
> +        compatible = "nxp,imx95-camera-csr", "syscon";
> +        reg = <0x4ac10000 0x10000>;

[Severity: Low]
This isn't a bug, but the unit address in the node name (4c100000) does not
match the base address specified in the reg property (0x4ac10000). Should the
node be named syscon@4ac10000 to match the reg property and avoid unit_address
validation warnings?

> +        #address-cells = <1>;
> +        #size-cells = <1>;
> +        #clock-cells = <1>;
> +        clocks = <&scmi_clk 62>;
> +        power-domains = <&scmi_devpd 3>;

[Severity: Low]
Does this syscon parent node need a ranges property?

Because it specifies address and size cells and contains a memory-mapped
child node (formatter@20), omitting the ranges property prevents correct
address translation for the child node and typically results in dtc warnings.

> +
> +        formatter@20{

[Severity: Low]
This isn't a bug, but there is a missing space before the opening brace.

> +            compatible = "fsl,imx95-csi-formatter";
> +            reg = <0x20 0x100>;
[ ... ]
> +                port@0 {
> +                    reg = <0>;
> +
> +                    endpoint {
> +                        remote-endpoint = <&mipi_csi_0_out>;
> +                    };
> +
> +               };

[Severity: Low]
This isn't a bug, but the closing brace here is indented incorrectly compared
to the rest of the block.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260526-csi_formatter-v9-0-ca3d8c334c39@oss.nxp.com?part=2

  reply	other threads:[~2026-05-26  9:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26  8:57 [PATCH v9 0/3] media: nxp: Add CSI Pixel Formatter support Guoniu Zhou
2026-05-26  8:57 ` [PATCH v9 1/3] dt-bindings: clock: imx95-blk-ctl: Allow child nodes Guoniu Zhou
2026-05-26  9:11   ` sashiko-bot
2026-05-26  8:57 ` [PATCH v9 2/3] media: dt-bindings: Add CSI Pixel Formatter DT bindings Guoniu Zhou
2026-05-26  9:18   ` sashiko-bot [this message]
2026-05-26  8:57 ` [PATCH v9 3/3] media: nxp: Add i.MX95 CSI pixel formatter v4l2 driver Guoniu Zhou
2026-05-26  9:42   ` sashiko-bot

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=20260526091847.CFCB31F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=guoniu.zhou@oss.nxp.com \
    --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