Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Andrew Gigena" <mail@andrewgigena.dev>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
	media-ci@linuxtv.org
Subject: Re: [PATCH v2 5/5] arm64: dts: qcom: sm8150: Add CAMSS and CCI nodes
Date: Fri, 06 Nov 2026 03:41:12 +0000	[thread overview]
Message-ID: <sashiko-outbox-200659@kernel.org> (raw)
In-Reply-To: <20261106-sm8150-v7.4-rc1-camss-v2-5-39ee37787b00@andrewgigena.dev>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] arm64: dts: qcom: sm8150: inverted CLK/DATA comments in CCI pinctrl nodes
--

commit 338e8b9406e2ae8eb1e75907ca56f8da311da07c
Author: Andrew Gigena <mail@andrewgigena.dev>

arm64: dts: qcom: sm8150: Add CAMSS and CCI nodes

This commit adds the CAMSS and CCI controller nodes to the SM8150 SoC
devicetree, along with the corresponding TLMM pinctrl states for the CCI0
and CCI1 I2C buses.

> diff --git a/arch/arm64/boot/dts/qcom/sm8150.dtsi b/arch/arm64/boot/dts/qcom/sm8150.dtsi
> index 293fcbacff346..a1fd3a4ed2e5e 100644
> --- a/arch/arm64/boot/dts/qcom/sm8150.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8150.dtsi
> @@ -2736,6 +2736,86 @@ wake-pins {
>  					bias-pull-up;
>  				};
>  			};
> +
> +			cci0_default: cci0-default-state {
> +				cci0_i2c0_default: cci0-i2c0-default-pins {
> +					/* CLK, DATA */
> +					pins = "gpio17", "gpio18";
> +					function = "cci_i2c";
> +
> +					bias-pull-up;
> +					drive-strength = <2>; /* 2 mA */
> +				};
> +
> +				cci0_i2c1_default: cci0-i2c1-default-pins {
> +					/* CLK, DATA */
> +					pins = "gpio19", "gpio20";
> +					function = "cci_i2c";
> +
> +					bias-pull-up;
> +					drive-strength = <2>; /* 2 mA */
> +				};
> +			};
> +
> +			cci0_sleep: cci0-sleep-state {
> +				cci0_i2c0_sleep: cci0-i2c0-sleep-pins {
> +					/* CLK, DATA */
> +					pins = "gpio17", "gpio18";
> +					function = "cci_i2c";
> +
> +					drive-strength = <2>; /* 2 mA */
> +					bias-pull-down;
> +				};
> +
> +				cci0_i2c1_sleep: cci0-i2c1-sleep-pins {
> +					/* CLK, DATA */
> +					pins = "gpio19", "gpio20";
> +					function = "cci_i2c";
> +
> +					drive-strength = <2>; /* 2 mA */
> +					bias-pull-down;
> +				};
> +			};
> +
> +			cci1_default: cci1-default-state {
> +				cci1_i2c0_default: cci1-i2c0-default-pins {
> +					/* CLK, DATA */
> +					pins = "gpio31", "gpio32";
> +					function = "cci_i2c";
> +
> +					bias-pull-up;
> +					drive-strength = <2>; /* 2 mA */
> +				};
> +
> +				cci1_i2c1_default: cci1-i2c1-default-pins {
> +					/* CLK, DATA */
> +					pins = "gpio33", "gpio34";
> +					function = "cci_i2c";
> +
> +					bias-pull-up;
> +					drive-strength = <2>; /* 2 mA */
> +				};
> +			};
> +
> +			cci1_sleep: cci1-sleep-state {
> +				cci1_i2c0_sleep: cci1-i2c0-sleep-pins {
> +					/* CLK, DATA */
> +					pins = "gpio31", "gpio32";
> +					function = "cci_i2c";
> +
> +					bias-pull-down;
> +					drive-strength = <2>; /* 2 mA */
> +				};
> +
> +				cci1_i2c1_sleep: cci1-i2c1-sleep-pins {
> +					/* CLK, DATA */
> +					pins = "gpio33", "gpio34";
> +					function = "cci_i2c";
> +
> +					bias-pull-down;
> +					drive-strength = <2>; /* 2 mA */
> +				};
> +			};

[Severity: Low]
Are the /* CLK, DATA */ comments inverted across the cci0_default,
cci0_sleep, cci1_default, and cci1_sleep pinctrl subnodes?

Looking at the TLMM GPIO line names in
arch/arm64/boot/dts/qcom/sm8150-sony-xperia-kumano.dtsi:

    &tlmm {
        gpio-line-names =
            ...
            "CCI_I2C_SDA0",
            "CCI_I2C_SCL0",
            "CCI_I2C_SDA1",
            "CCI_I2C_SCL1", /* GPIO_20 */
            ...
            "CCI_I2C_SDA2",
            "CCI_I2C_SCL2",
            "CCI_I2C_SDA3",
            "CCI_I2C_SCL3",
            ...

gpio17, gpio19, gpio31, and gpio33 are the SDA (DATA) lines, while gpio18,
gpio20, gpio32, and gpio34 are the SCL (CLK) lines. Should these comments
say /* SDA, SCL */ or /* DATA, CLK */ instead?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261106-sm8150-v7.4-rc1-camss-v2-0-39ee37787b00@andrewgigena.dev?part=5

      reply	other threads:[~2026-11-06  3:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06  3:24 [PATCH v2 0/5] media: qcom: camss: Add SM8150 CAMSS support Andrew Gigena via B4 Relay
2026-11-06  3:24 ` [PATCH v2 1/5] dt-bindings: i2c: qcom-cci: Document SM8150 compatible Andrew Gigena via B4 Relay
2026-11-06 12:09   ` Krzysztof Kozlowski
2026-11-06  3:24 ` [PATCH v2 2/5] dt-bindings: media: qcom,sm8150-camss: Add SM8150 CAMSS Andrew Gigena via B4 Relay
2026-11-06  3:36   ` sashiko-bot
2026-11-06 11:20   ` Vladimir Zapolskiy
2026-11-06 11:46     ` Bryan O'Donoghue
2026-11-06 11:34   ` Bryan O'Donoghue
2026-11-06 12:15   ` Krzysztof Kozlowski
2026-11-06  3:24 ` [PATCH v2 3/5] media: qcom: camss: Match VFE lite clocks by name prefix Andrew Gigena via B4 Relay
2026-11-06  3:36   ` sashiko-bot
2026-11-06 11:26   ` Bryan O'Donoghue
2026-11-06  3:24 ` [PATCH v2 4/5] media: qcom: camss: Add support for SM8150 Andrew Gigena via B4 Relay
2026-11-06 11:27   ` Bryan O'Donoghue
2026-11-06  3:24 ` [PATCH v2 5/5] arm64: dts: qcom: sm8150: Add CAMSS and CCI nodes Andrew Gigena via B4 Relay
2026-11-06  3:41   ` 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=sashiko-outbox-200659@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=mail@andrewgigena.dev \
    --cc=media-ci@linuxtv.org \
    --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