From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vijay Kumar Tumati <vijay.tumati@oss.qualcomm.com>,
Bryan O'Donoghue <bod@kernel.org>,
Luca Weiss <luca.weiss@fairphone.com>
Cc: Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: media: camss: Add qcom,sm6350-camss
Date: Wed, 18 Feb 2026 21:10:44 +0100 [thread overview]
Message-ID: <002d0b53-8fd6-4d40-9c4c-4c79a7704fce@kernel.org> (raw)
In-Reply-To: <b3e76e9f-a820-43ee-9089-7b7eaa876ebe@oss.qualcomm.com>
On 17/02/2026 23:18, Vijay Kumar Tumati wrote:
>>>> + vdd-csiphy3-1p25-supply:
>>>> + description:
>>>> + Phandle to a 1.25V regulator supply to CSIPHY3.
>>>
>>> I assume that we abandon the idea of separate CSI PHY devices. It was
>>> discssed way too long time ago.
>>
>> No just waiting for 6.20/7.0 to drop however, I think its fine to add
>> new definitions until we merge that series.
>>> With domains changed:
> Please correct me if I misunderstood but if we are not blocking the new
> patches over PHY node separation anymore, can you re-review SM8750
> patches please, Krzysztof? Thank you.
>
> https://lore.kernel.org/all/20260119-add-support-for-camss-on-sm8750-v2-0-3e06583a0a81@oss.qualcomm.com/
I replied there, one more thing to fix.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-18 20:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 13:15 [PATCH v3 0/3] Add CAMSS support for SM6350 Luca Weiss
2026-02-13 13:15 ` [PATCH v3 1/3] dt-bindings: media: camss: Add qcom,sm6350-camss Luca Weiss
2026-02-14 8:37 ` Krzysztof Kozlowski
2026-02-14 13:05 ` Bryan O'Donoghue
2026-02-17 22:18 ` Vijay Kumar Tumati
2026-02-18 20:10 ` Krzysztof Kozlowski [this message]
2026-02-18 20:47 ` Vijay Kumar Tumati
2026-02-26 9:44 ` Krzysztof Kozlowski
2026-02-13 13:15 ` [PATCH v3 2/3] media: qcom: camss: Add SM6350 support Luca Weiss
2026-02-14 13:08 ` Bryan O'Donoghue
2026-02-15 12:46 ` David Heidelberg
2026-02-16 10:02 ` Bryan O'Donoghue
2026-02-13 13:15 ` [PATCH v3 3/3] arm64: dts: qcom: sm6350: Add CAMSS node Luca Weiss
2026-02-16 11:04 ` [PATCH v3 0/3] Add CAMSS support for SM6350 Konrad Dybcio
2026-02-17 11:56 ` Imran Shaik
2026-02-17 12:01 ` Konrad Dybcio
2026-02-18 18:12 ` Imran Shaik
2026-02-24 13:43 ` Konrad Dybcio
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=002d0b53-8fd6-4d40-9c4c-4c79a7704fce@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=bod@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-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=mchehab@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--cc=vijay.tumati@oss.qualcomm.com \
--cc=vladimir.zapolskiy@linaro.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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