From: Fenglin Wu <quic_fenglinw@quicinc.com>
To: Robert Marko <robimarko@gmail.com>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
<quic_tdas@quicinc.com>, <quic_aiquny@quicinc.com>
Cc: <kernel@quicinc.com>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: ipq6018: add #power-domain-cells for gcc node
Date: Thu, 4 Jan 2024 18:40:53 +0800 [thread overview]
Message-ID: <a8012b92-6072-406d-8aab-ecb167ea44d2@quicinc.com> (raw)
In-Reply-To: <685f45d9-48e8-49c6-9de0-6771777ba62e@gmail.com>
On 1/4/2024 6:32 PM, Robert Marko wrote:
>
> On 04. 01. 2024. 11:16, Konrad Dybcio wrote:
>> On 4.01.2024 11:13, Fenglin Wu wrote:
>>>
>>> On 1/4/2024 5:53 PM, Dmitry Baryshkov wrote:
>>>> On Thu, 4 Jan 2024 at 10:06, Fenglin Wu via B4 Relay
>>>> <devnull+quic_fenglinw.quicinc.com@kernel.org> wrote:
>>>>> From: Fenglin Wu <quic_fenglinw@quicinc.com>
>>>>>
>>>>> Property '#power-domain-cells' is required as per defined in
>>>>> qcom,gcc.yaml
>>>>> so add it for ipq6018 gcc device node to eliminate following
>>>>> warning in
>>>>> dtbs_check:
>>>>>
>>>>> arch/arm64/boot/dts/qcom/ipq6018-cp01-c1.dtb: gcc@1800000:
>>>>> '#power-domain-cells' is a required property
>>>>> from schema $id:
>>>>> http://devicetree.org/schemas/clock/qcom,gcc-ipq6018.yaml#
>>>> But ipq6018 doesn't implement GDSC support. So for the sake of fixing
>>>> the warning you are adding a bogus property.
>>>>
>>> I agree. However, there are also some gcc drivers not implementing
>>> GDSC support but the bindings are adding '#power-domain-cells' in the
>>> DT example, such as: qcom,gcc-apq8064.yaml, qcom,gcc-ipq4019.yaml,
>>> qcom,gcc-ipq6018.yaml, qcom,gcc-ipq8064.yaml, qcom,gcc-msm8660.yaml.
>>>
>>> Actually I thought that maybe we should do a clean up by removing
>>> '#power-domain-cells' out of the qcom,gcc.yaml binding and only
>>> adding it into individual qcom,gcc-xxx.yaml for the driver which has
>>> implemented GDSC support. I checked this with Taniya offline, but she
>>> prefers only fixing it in ipq6018.dtsi as it doesn't hurt anything by
>>> adding the property, and she expects the GDSC support should be
>>> existing in most of qcom,gcc drivers especially the newer Qcom chipsets.
>> Before we start changing anything, we should assess whether these
>> platforms actually have GDSCs within this clock controller block,
>> even if they are (currently) not described in the clk driver.
> Hi,
> IPQ6018 has GDSC-s, at least for the USB-s.
> I tried configuring them a while ago, but the USB2.0 GDSC seems to
> either have a HW bug or
> it uses some special configuration as its status bits never show that
> its ON [1].
>
> [1]
> https://patchwork.kernel.org/project/linux-arm-msm/patch/20231025104457.628109-2-robimarko@gmail.com/
>
Thanks for the link! I checked the spec internal, and I did see GDSC
device for USB0/USB1 controller is present in GCC clock controller.
So considering there is a patch ongoing to add GDSC device for ipq6018
gcc driver, can the DT commit which adds '#power-domain-cells' be accepted?
> Regards,
> Robert
>
>>
>> Konrad
next prev parent reply other threads:[~2024-01-04 10:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 8:06 [PATCH] arm64: dts: qcom: ipq6018: add #power-domain-cells for gcc node Fenglin Wu via B4 Relay
2024-01-04 9:53 ` Dmitry Baryshkov
2024-01-04 10:07 ` Krzysztof Kozlowski
2024-01-04 10:13 ` Fenglin Wu
2024-01-04 10:16 ` Konrad Dybcio
2024-01-04 10:27 ` Fenglin Wu
2024-01-04 10:30 ` Dmitry Baryshkov
2024-01-04 10:32 ` Robert Marko
2024-01-04 10:40 ` Fenglin Wu [this message]
2024-01-04 10:49 ` Dmitry Baryshkov
2024-01-04 10:55 ` Fenglin Wu
2024-01-04 12:07 ` Krzysztof Kozlowski
2024-01-04 10:34 ` Dmitry Baryshkov
2024-02-16 17:58 ` Bjorn Andersson
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=a8012b92-6072-406d-8aab-ecb167ea44d2@quicinc.com \
--to=quic_fenglinw@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_aiquny@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=robimarko@gmail.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