public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
To: Pengyu Luo <mitltlatltl@gmail.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Martin Kepplinger-Novakovic <martink@posteo.de>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Hans Verkuil <hverkuil@kernel.org>,
	Martin Kepplinger <martin.kepplinger@puri.sm>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH 4/4] arm64: dts: qcom: sc8280xp: gaokun3: describe rear camera module information as musch as possible
Date: Tue, 5 May 2026 21:55:41 +0300	[thread overview]
Message-ID: <9da6d544-97f6-4915-8d53-e3fde7339695@linaro.org> (raw)
In-Reply-To: <CAH2e8h4TYEMhjP9Vx7yYpKHAOR627Ovy2QZMT574oZPVDJX1oA@mail.gmail.com>

On 5/2/26 15:55, Pengyu Luo wrote:
> On Thu, Apr 30, 2026 at 7:00 PM Vladimir Zapolskiy
> <vladimir.zapolskiy@linaro.org> wrote:
>>
>> On 4/25/26 13:53, Pengyu Luo wrote:
>>> The rear sensor is S5K3L6, describing it but dropping compatible
>>> string, since there is no upstream driver. A funcitonal downstream
>>> driver is in comment.
>>>
>>> The VCM is dw9714, describe it.
>>>
>>> Signed-off-by: Pengyu Luo <mitltlatltl@gmail.com>
>>> ---
>>> Please take this patch as a RFC, I am not sure, how much I am allowed
>>> to add without a sensor driver.
>>> ---
>>>    .../boot/dts/qcom/sc8280xp-huawei-gaokun3.dts | 129 +++++++++++++++++-
>>>    1 file changed, 123 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/arch/arm64/boot/dts/qcom/sc8280xp-huawei-gaokun3.dts b/arch/arm64/boot/dts/qcom/sc8280xp-huawei-gaokun3.dts
>>> index 39e559e91289..76b1ecb3819d 100644
>>> --- a/arch/arm64/boot/dts/qcom/sc8280xp-huawei-gaokun3.dts
>>> +++ b/arch/arm64/boot/dts/qcom/sc8280xp-huawei-gaokun3.dts
>>> @@ -22,12 +22,18 @@
>>>    #include "sc8280xp.dtsi"
>>>    #include "sc8280xp-pmics.dtsi"
>>>
>>> +/* remove due to gpio pins collision, skip 2nd instance won't break things */
>>> +/delete-node/ &cci1_i2c1;
>>> +/delete-node/ &cci1_i2c1_default;
>>> +/delete-node/ &cci1_i2c1_sleep;
>>
>> Instead of removal 'cci1_default' and 'cci1_sleep' nodes shall be rewritten
>> by excluding 'cci1_i2c1_default' and 'cci1_i2c1_sleep' from them.
>>
> 
> Should we register an unused node?
> 

I believe unused nodes are found everywhere marked by status = "disabled"
or if they do not produce a conflict for resources. I understand that a CCI
IP with two ports are special, but likely (not always though) it should be
acceptable to keep its device tree node as is.

-- 
Best wishes,
Vladimir

      reply	other threads:[~2026-05-05 18:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-25 10:52 [PATCH 0/4] support camera found on Gaokun3 Pengyu Luo
2026-04-25 10:52 ` [PATCH 1/4] media: hi846: fix hi846_write_reg_16 handling Pengyu Luo
2026-04-25 10:52 ` [PATCH 2/4] media: hi846: Add 6MP and 8MP mode support Pengyu Luo
2026-04-25 10:52 ` [PATCH 3/4] arm64: dts: qcom: sc8280xp: gaokun3: add front camera sensor node Pengyu Luo
2026-04-27 13:00   ` Konrad Dybcio
2026-04-29  6:36     ` Pengyu Luo
2026-04-29 10:08       ` Konrad Dybcio
2026-04-29 11:23         ` Pengyu Luo
2026-04-30 10:49   ` Vladimir Zapolskiy
2026-05-02 12:48     ` Pengyu Luo
2026-05-05 18:50       ` Vladimir Zapolskiy
2026-04-25 10:53 ` [PATCH 4/4] arm64: dts: qcom: sc8280xp: gaokun3: describe rear camera module information as musch as possible Pengyu Luo
2026-04-30 11:00   ` Vladimir Zapolskiy
2026-05-02 12:55     ` Pengyu Luo
2026-05-05 18:55       ` Vladimir Zapolskiy [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=9da6d544-97f6-4915-8d53-e3fde7339695@linaro.org \
    --to=vladimir.zapolskiy@linaro.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil@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=martin.kepplinger@puri.sm \
    --cc=martink@posteo.de \
    --cc=mchehab@kernel.org \
    --cc=mitltlatltl@gmail.com \
    --cc=robh@kernel.org \
    --cc=sakari.ailus@linux.intel.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