Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Laurent Pinchart" <laurent.pinchart@ideasonboard.com>
Cc: robh@kernel.org, Frank.Li@kernel.org, devicetree@vger.kernel.org,
	imx@lists.linux.dev, conor+dt@kernel.org
Subject: Re: [PATCH v3 6/7] ARM: dts: nxp: imx6qdl-pico: Replace clock-frequency in camera sensor node
Date: Mon, 10 Aug 2026 18:11:56 +0000	[thread overview]
Message-ID: <20260810181157.095B71F00A3E@smtp.kernel.org> (raw)
In-Reply-To: <20260810180604.3034255-7-laurent.pinchart@ideasonboard.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch adds a blank line despite the changelog explicitly stating it was dropped in v2.
--

--- Patch [6]: [PATCH v3 6/7] ARM: dts: nxp: imx6qdl-pico: Replace clock-frequency in camera sensor node ---
commit 71890897809f09d8572aca4c1562adf06208b09e
Author: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

ARM: dts: nxp: imx6qdl-pico: Replace clock-frequency in camera sensor node

The clock-frequency property for camera sensors is deprecated. This commit
replaces it with assigned-clocks and assigned-clock-rates in the device tree
configuration.

> diff --git a/arch/arm/boot/dts/nxp/imx/imx6qdl-pico.dtsi b/arch/arm/boot/dts/nxp/imx/imx6qdl-pico.dtsi
> index ca4cb986efbc2..0cc05d084f9bf 100644
> --- a/arch/arm/boot/dts/nxp/imx/imx6qdl-pico.dtsi
> +++ b/arch/arm/boot/dts/nxp/imx/imx6qdl-pico.dtsi
> @@ -233,7 +233,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 patch changelog mentions dropping the added blank
line for v2. It appears the blank line still made it into this version. 
Was this left in by accident?

>  		vdddo-supply = <&reg_1p8v>;
>  		vdda-supply = <&reg_2p8v>;
>  		vddd-supply = <&reg_1p5v>;

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260810180604.3034255-1-laurent.pinchart@ideasonboard.com?part=6

  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 [this message]
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

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=20260810181157.095B71F00A3E@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