From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
Robert Foss <rfoss@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: i2c: qcom-cci: Document sm6150 compatible
Date: Mon, 22 Dec 2025 09:58:09 +0100 [thread overview]
Message-ID: <43efa6fd-53c3-4680-8aca-7b37089ca295@kernel.org> (raw)
In-Reply-To: <20251222-sm6150_evk-v1-1-4d260a31c00d@oss.qualcomm.com>
On 22/12/2025 09:44, Wenmeng Liu wrote:
> Add the sm6150 CCI device string compatible.
>
> Signed-off-by: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
> ---
> .../devicetree/bindings/i2c/qcom,i2c-cci.yaml | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml b/Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml
> index a3fe1eea6aece9685674feaa5ec53765c1ce23d8..cb5e6fd5b2ad1de79a9b29d54869d093c952d778 100644
> --- a/Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml
> +++ b/Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml
> @@ -33,6 +33,7 @@ properties:
> - qcom,sc8280xp-cci
> - qcom,sdm670-cci
> - qcom,sdm845-cci
> + - qcom,sm6150-cci
> - qcom,sm6350-cci
> - qcom,sm8250-cci
> - qcom,sm8450-cci
> @@ -263,6 +264,23 @@ allOf:
> - const: cpas_ahb
> - const: cci
>
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - qcom,sm6150-cci
> + then:
> + properties:
> + clocks:
> + minItems: 3
> + maxItems: 3
> + clock-names:
> + items:
> + - const: soc_ahb
Isn't this just camnoc_axi for this device (pay attention: to this device)?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-22 8:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 8:44 [PATCH 0/3] Add CCI and imx577 sensor support for Talos evk Wenmeng Liu
2025-12-22 8:44 ` [PATCH 1/3] dt-bindings: i2c: qcom-cci: Document sm6150 compatible Wenmeng Liu
2025-12-22 8:58 ` Krzysztof Kozlowski [this message]
2025-12-22 9:13 ` Wenmeng Liu
2025-12-22 9:49 ` Konrad Dybcio
2025-12-22 11:02 ` Wenmeng Liu
2025-12-22 11:58 ` Krzysztof Kozlowski
2025-12-22 12:12 ` Wenmeng Liu
2025-12-22 8:44 ` [PATCH 2/3] arm64: dts: qcom: talos: Add CCI definitions Wenmeng Liu
2025-12-29 13:21 ` Konrad Dybcio
2025-12-29 13:22 ` Konrad Dybcio
2025-12-22 8:44 ` [PATCH 3/3] arm64: dts: qcom: talos-evk-camera: Add DT overlay Wenmeng Liu
2025-12-22 11:19 ` Vladimir Zapolskiy
2025-12-22 11:41 ` Wenmeng Liu
2025-12-22 15:45 ` Vladimir Zapolskiy
2025-12-23 2:16 ` Wenmeng Liu
2025-12-23 16:36 ` Vladimir Zapolskiy
2025-12-24 2:12 ` Wenmeng Liu
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=43efa6fd-53c3-4680-8aca-7b37089ca295@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=wenmeng.liu@oss.qualcomm.com \
/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