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 1/4] dt-bindings: i2c: qcom-cci: Document SM8150 compatible
Date: Wed, 04 Nov 2026 20:59:16 +0000 [thread overview]
Message-ID: <sashiko-outbox-198033@kernel.org> (raw)
In-Reply-To: <20261104-sm8150-v7-4-rc1-camss-v1-1-7a9534a9a22f@andrewgigena.dev>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: i2c: qcom-cci: missing allOf clock constraints for sm8150
--
commit aefd954e17156282727d64e6f6e3ba7607d36440
Author: Andrew Gigena <mail@andrewgigena.dev>
dt-bindings: i2c: qcom-cci: Document SM8150 compatible
This commit adds qcom,sm8150-cci to the list of CCI v2 compatible strings
with qcom,msm8996-cci as a fallback.
> diff --git a/Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml b/Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml
> index 1e8def25ec0ec..b545fd2378dae 100644
> --- a/Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml
> +++ b/Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml
> @@ -39,6 +39,7 @@ properties:
> - qcom,shikra-cci
> - qcom,sm6150-cci
> - qcom,sm6350-cci
> + - qcom,sm8150-cci
[Severity: Low]
Should qcom,sm8150-cci also be added to the 5-clock conditional under allOf
in Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml?
At the top level, clocks and clock-names only specify minItems: 2 and
maxItems: 6 without listing the allowed clock-names items. The
qcom,msm8996-cci rule under allOf uses const: qcom,msm8996-cci rather than
contains, so it only matches when qcom,msm8996-cci is used alone and does
not apply when paired with qcom,sm8150-cci.
Without adding qcom,sm8150-cci to the allOf conditional block alongside
qcom,sc7280-cci, qcom,sm8250-cci, and qcom,sm8450-cci:
- if:
properties:
compatible:
contains:
enum:
- qcom,sc7280-cci
- qcom,sm8250-cci
- qcom,sm8450-cci
then:
properties:
clocks:
minItems: 5
maxItems: 5
clock-names:
items:
- const: camnoc_axi
- const: slow_ahb_src
- const: cpas_ahb
- const: cci
- const: cci_src
dtbs_check will not constrain the clock count or clock-names list for
qcom,sm8150-cci nodes.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261104-sm8150-v7-4-rc1-camss-v1-0-7a9534a9a22f@andrewgigena.dev?part=1
next prev parent reply other threads:[~2026-11-04 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 20:54 [PATCH 0/4] media: qcom: camss: Add SM8150 CAMSS support Andrew Gigena via B4 Relay
2026-11-04 20:54 ` [PATCH 1/4] dt-bindings: i2c: qcom-cci: Document SM8150 compatible Andrew Gigena via B4 Relay
2026-11-04 20:59 ` sashiko-bot [this message]
2026-11-04 20:54 ` [PATCH 2/4] dt-bindings: media: qcom,sm8150-camss: Add SM8150 CAMSS Andrew Gigena via B4 Relay
2026-11-04 20:54 ` [PATCH 3/4] media: qcom: camss: Add support for SM8150 Andrew Gigena via B4 Relay
2026-11-04 20:54 ` [PATCH 4/4] arm64: dts: qcom: sm8150: Add CAMSS and CCI nodes Andrew Gigena via B4 Relay
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-198033@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