From: sashiko-bot@kernel.org
To: "Guoniu Zhou" <guoniu.zhou@oss.nxp.com>
Cc: conor+dt@kernel.org, Frank.Li@kernel.org, imx@lists.linux.dev,
robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v8 1/2] media: dt-bindings: Add CSI Pixel Formatter DT bindings
Date: Mon, 25 May 2026 08:20:51 +0000 [thread overview]
Message-ID: <20260525082051.833E51F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260525-csi_formatter-v8-1-6b646231224b@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The dt-binding example will fail `dt_binding_check` due to an invalid `reg` property length and unit address mismatch in the parent `syscon` node.
- [Low] Misleading indentation of the closing braces for the `endpoint` node within `port@0` in the dt-binding example.
--
commit 6a7b1f87ea2dd192a60ffaf87f2da35cb030c9a0
Author: Guoniu Zhou <guoniu.zhou@nxp.com>
media: dt-bindings: Add CSI Pixel Formatter DT bindings
This commit adds the device tree bindings for the i.MX95 CSI pixel
formatting module. The module reformats packet info and data from the
CSI-2 host controller to match 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..bc2f5d448fe58
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/fsl,imx95-csi-formatter.yaml
[ ... ]
> +examples:
> + - |
> + #include <dt-bindings/clock/nxp,imx95-clock.h>
> +
> + syscon@4ac10000 {
> + compatible = "nxp,imx95-camera-csr", "syscon";
> + reg = <0x0 0x4ac10000 0x0 0x10000>;
[Severity: Low]
Will this example successfully pass dt_binding_check?
The syscon node uses a 4-cell reg property, which requires a parent node
configured with #address-cells = <2> and #size-cells = <2>. Since this node
is placed at the root of the example, the implicit root node defaults to 1
for both cells, which can trigger a dtc warning due to an invalid property
length.
> + #address-cells = <1>;
> + #size-cells = <1>;
[ ... ]
> + port@0 {
> + reg = <0>;
> +
> + endpoint {
> + remote-endpoint = <&mipi_csi_0_out>;
> + };
> + };
[Severity: Low]
This isn't a bug, but the closing braces for the endpoint and port@0 nodes
have misleading indentation.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260525-csi_formatter-v8-0-6b646231224b@oss.nxp.com?part=1
next prev parent reply other threads:[~2026-05-25 8:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 8:12 [PATCH v8 0/2] media: nxp: Add CSI Pixel Formatter support Guoniu Zhou
2026-05-25 8:12 ` [PATCH v8 1/2] media: dt-bindings: Add CSI Pixel Formatter DT bindings Guoniu Zhou
2026-05-25 8:20 ` sashiko-bot [this message]
2026-05-25 10:43 ` Rob Herring (Arm)
2026-05-26 9:13 ` Krzysztof Kozlowski
2026-05-26 9:33 ` [EXT] " G.N. Zhou
2026-05-26 9:44 ` Laurent Pinchart
2026-05-27 9:37 ` Krzysztof Kozlowski
2026-05-27 9:39 ` Krzysztof Kozlowski
2026-05-27 11:45 ` Laurent Pinchart
2026-05-25 8:12 ` [PATCH v8 2/2] media: nxp: Add i.MX95 CSI pixel formatter v4l2 driver Guoniu Zhou
2026-05-25 8:46 ` 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=20260525082051.833E51F00A3A@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