From: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Vikram Sharma <quic_vikramsa@quicinc.com>,
mchehab@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, andersson@kernel.org,
konradybcio@kernel.org, hverkuil-cisco@xs4all.nl,
cros-qcom-dts-watchers@chromium.org, catalin.marinas@arm.com,
will@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, quic_svankada@quicinc.com,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v4 2/2] arm64: dts: qcom: qcs8300: Add support for camss
Date: Thu, 16 Oct 2025 02:21:26 +0300 [thread overview]
Message-ID: <47b4dc34-ae75-437f-84ce-84558226cdeb@linaro.org> (raw)
In-Reply-To: <ca8189d0-a518-4716-8b28-e36571cbba5a@linaro.org>
On 10/15/25 22:58, Bryan O'Donoghue wrote:
> On 15/10/2025 19:49, Vladimir Zapolskiy wrote:
>>> + power-domains = <&camcc CAM_CC_TITAN_TOP_GDSC>;
>>> + power-domain-names = "top";
>>
>> 'power-domain-names' property is redundant, since there is just one
>> power domain.
>
> Its a required property of the yaml.
>
Technically it is not a property of the yaml, but I think I understand
what you mean here.
As usual since there is no users of the previously written device tree
node rules, I believe the documentation is still flexible to be updated
to a better shape.
--
Best wishes,
Vladimir
next prev parent reply other threads:[~2025-10-15 23:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 13:01 [PATCH v4 0/2] qcom: qcs8300: Add qcs8300 camss support Vikram Sharma
2025-10-15 13:01 ` [PATCH v4 1/2] dt-bindings: media: qcom,qcs8300-camss: Add missing power supplies Vikram Sharma
2025-10-15 13:30 ` Bryan O'Donoghue
2025-10-15 18:41 ` Vladimir Zapolskiy
2025-10-15 19:12 ` Bryan O'Donoghue
2025-10-15 19:20 ` Vladimir Zapolskiy
2025-10-15 13:01 ` [PATCH v4 2/2] arm64: dts: qcom: qcs8300: Add support for camss Vikram Sharma
2025-10-15 18:49 ` Vladimir Zapolskiy
2025-10-15 19:58 ` Bryan O'Donoghue
2025-10-15 23:21 ` Vladimir Zapolskiy [this message]
2025-10-16 5:59 ` Krzysztof Kozlowski
2025-10-16 9:52 ` Vladimir Zapolskiy
2025-10-16 10:39 ` Krzysztof Kozlowski
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=47b4dc34-ae75-437f-84ce-84558226cdeb@linaro.org \
--to=vladimir.zapolskiy@linaro.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_svankada@quicinc.com \
--cc=quic_vikramsa@quicinc.com \
--cc=robh@kernel.org \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).