From: sashiko-bot@kernel.org
To: "Laurent Pinchart" <laurent.pinchart@ideasonboard.com>
Cc: imx@lists.linux.dev, robh@kernel.org, devicetree@vger.kernel.org,
Frank.Li@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 7/7] ARM: dts: nxp: imx6qdl-wandboard: Replace clock-frequency in camera sensor node
Date: Mon, 10 Aug 2026 18:11:30 +0000 [thread overview]
Message-ID: <20260810181131.29A691F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260810180604.3034255-8-laurent.pinchart@ideasonboard.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch introduces a blank line in the device tree node, directly contradicting the "Changes since v1" section of the commit message which states "- Drop added blank line".
--
--- Patch [7]: [PATCH v3 7/7] ARM: dts: nxp: imx6qdl-wandboard: Replace clock-frequency in camera sensor node ---
commit c2dd0680ebe87860961c5447228271fe2e5bfa7b
Author: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
ARM: dts: nxp: imx6qdl-wandboard: Replace clock-frequency in camera sensor node
This commit replaces the deprecated clock-frequency property with
assigned-clocks and assigned-clock-rates for the camera sensor node
in the device tree.
> diff --git a/arch/arm/boot/dts/nxp/imx/imx6qdl-wandboard.dtsi b/arch/arm/boot/dts/nxp/imx/imx6qdl-wandboard.dtsi
> index 26489eccd5fbe..f3aaca039953b 100644
> --- a/arch/arm/boot/dts/nxp/imx/imx6qdl-wandboard.dtsi
> +++ b/arch/arm/boot/dts/nxp/imx/imx6qdl-wandboard.dtsi
> @@ -137,7 +137,9 @@ camera@3c {
> pinctrl-0 = <&pinctrl_ov5645>;
> reg = <0x3c>;
> clocks = <&clks IMX6QDL_CLK_CKO2>;
> - clock-frequency = <24000000>;
> + assigned-clocks = <&clks IMX6QDL_CLK_CKO2>;
> + assigned-clock-rates = <24000000>;
> +
[Severity: Low]
This isn't a bug, but the "Changes since v1" section of the commit message
states "- Drop added blank line". It looks like the blank line was still
accidentally included here in the camera@3c node. Should this line be removed
to match the changelog?
> vdddo-supply = <®_1p8v>;
> vdda-supply = <®_2p8v>;
> vddd-supply = <®_1p5v>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260810180604.3034255-1-laurent.pinchart@ideasonboard.com?part=7
prev parent reply other threads:[~2026-08-10 18:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 18:05 [PATCH v3 0/7] ARM: dts: Replace clock-frequency in camera sensor nodes Laurent Pinchart
2026-08-10 18:05 ` [PATCH v3 1/7] ARM: dts: samsung: exynos4210-i9100: Replace clock-frequency in camera sensor node Laurent Pinchart
2026-08-10 18:05 ` [PATCH v3 2/7] ARM: dts: samsung: exynos4412-midas: " Laurent Pinchart
2026-08-10 18:06 ` [PATCH v3 3/7] ARM: dts: ti: omap3-n950: " Laurent Pinchart
2026-08-10 18:06 ` [PATCH v3 4/7] ARM: dts: ti: omap3-n9: " Laurent Pinchart
2026-08-10 18:06 ` [PATCH v3 5/7] ARM: dts: ti: omap3-n900: " Laurent Pinchart
2026-08-10 18:06 ` [PATCH v3 6/7] ARM: dts: nxp: imx6qdl-pico: " Laurent Pinchart
2026-08-10 18:11 ` sashiko-bot
2026-08-10 18:55 ` Frank Li
2026-08-10 19:08 ` Laurent Pinchart
2026-08-10 18:06 ` [PATCH v3 7/7] ARM: dts: nxp: imx6qdl-wandboard: " Laurent Pinchart
2026-08-10 18:11 ` sashiko-bot [this message]
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=20260810181131.29A691F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--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