[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a228d38d-9fb9-4e61-9a02-e70593c69dac@kernel.org>
Date: Tue, 6 Jan 2026 20:18:32 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Vijay Kumar Tumati <vijay.tumati@....qualcomm.com>,
Hangxiang Ma <hangxiang.ma@....qualcomm.com>
Cc: Loic Poulain <loic.poulain@....qualcomm.com>,
Robert Foss <rfoss@...nel.org>, Andi Shyti <andi.shyti@...nel.org>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Todor Tomov <todor.too@...il.com>,
Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Bryan O'Donoghue <bryan.odonoghue@...aro.org>, linux-i2c@...r.kernel.org,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
jeyaprakash.soundrapandian@....qualcomm.com
Subject: Re: [PATCH 7/7] arm64: dts: qcom: sm8750: Add support for camss
On 06/01/2026 19:40, Vijay Kumar Tumati wrote:
>
> On 11/27/2025 12:12 AM, Krzysztof Kozlowski wrote:
>> On Wed, Nov 26, 2025 at 01:38:40AM -0800, Hangxiang Ma wrote:
>> +
>>> + cci1_1_default: cci1-1-default-state {
>>> + sda-pins {
>>> + pins = "gpio111";
>>> + function = "cci_i2c_sda";
>>> + drive-strength = <2>;
>>> + bias-pull-up;
>>> + };
>>> +
>>> + scl-pins {
>>> + pins = "gpio164";
>>> + function = "cci_i2c_scl";
>>> + drive-strength = <2>;
>>> + bias-pull-up;
>>> + };
>>> + };
>>> +
>>> + cci1_1_sleep: cci1-1-sleep-state {
>>> + sda-pins {
>>> + pins = "gpio111";
>>> + function = "cci_i2c_sda";
>>> + drive-strength = <2>;
>>> + bias-pull-down;
>>> + };
>>> +
>>> + scl-pins {
>>> + pins = "gpio164";
>>> + function = "cci_i2c_scl";
>>> + drive-strength = <2>;
>>> + bias-pull-down;
>>> + };
>>> + };
>>> +
>>> + cci2_0_default: cci2-0-default-state {
>>> + sda-pins {
>>> + pins = "gpio112";
>>> + function = "cci_i2c_sda";
>>> + drive-strength = <2>;
>>> + bias-pull-up;
>>> + };
>>> +
>>> + scl-pins {
>>> + pins = "gpio153";
>>> + function = "cci_i2c_scl";
>>> + drive-strength = <2>;
>>> + bias-pull-up;
>>> + };
>>> + };
>>> +
>>> + cci2_0_sleep: cci2-0-sleep-state {
>>> + sda-pins {
>>> + pins = "gpio112";
>>> + function = "cci_i2c_sda";
>>> + drive-strength = <2>;
>>> + bias-pull-down;
>>> + };
>>> +
>>> + scl-pins {
>>> + pins = "gpio153";
>>> + function = "cci_i2c_scl";
>>> + drive-strength = <2>;
>>> + bias-pull-down;
>>> + };
>>> + };
>>> +
>>> + cci2_1_default: cci2-1-default-state {
>>> + sda-pins {
>>> + pins = "gpio119";
>>> + function = "cci_i2c_sda";
>>> + drive-strength = <2>;
>>> + bias-pull-up;
>>> + };
>>> +
>>> + scl-pins {
>>> + pins = "gpio120";
>>> + function = "cci_i2c_scl";
>>> + drive-strength = <2>;
>>> + bias-pull-up;
>>> + };
>>> + };
>>> +
>>> + cci2_1_sleep: cci2-1-sleep-state {
>>> + sda-pins {
>>> + pins = "gpio119";
>>> + function = "cci_i2c_sda";
>>> + drive-strength = <2>;
>>> + bias-pull-down;
>>> + };
>>> +
>>> + scl-pins {
>>> + pins = "gpio120";
>>> + function = "cci_i2c_scl";
>>> + drive-strength = <2>;
>>> + bias-pull-down;
>>> + };
>>> + };
>>> + };
>>> +
>>> + cci0: cci@...b000 {
>> Looks completely mis-ordered/sorted. What are the nodes above and below?
> Hi Krzysztof, sorry, not sure how you mean exactly. The ones above are
> the pinctrl nodes. Each CCI has two masters using two GPIOs each, one
Why would pinctrl nodes matter anyhow? Please read how DTS syntax works.
> for clk and one for data. The ones below are the actual CCI HW nodes
> that make use of the pinctrls. I believe this is inline with previous
> generations. Have I missed something? Thanks.
I wrote what is wrong. Is this maintaining proper sorting? Did you read
DTS coding style?
Best regards,
Krzysztof
Powered by blists - more mailing lists