From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] arm64: dts: qcom: sc7180: move QUP and QSPI opp tables out of SoC node
Date: Mon, 12 Dec 2022 10:24:33 +0100 [thread overview]
Message-ID: <f6c9c9f1-fc10-d9d8-fef1-c43c04d209a8@linaro.org> (raw)
In-Reply-To: <6df8fc01-9fa1-d63d-25fb-ffa6683f4cb6@linaro.org>
On 12/12/2022 10:18, Konrad Dybcio wrote:
>
>
> On 12.12.2022 10:17, Krzysztof Kozlowski wrote:
>> On 12/12/2022 10:15, Konrad Dybcio wrote:
>>>>>> +
>>>>>> + qup_opp_table: opp-table-qup {
>>>>>> + compatible = "operating-points-v2";
>>>>>> +
>>>>>> + opp-75000000 {
>>>>>> + opp-hz = /bits/ 64 <75000000>;
>>>>>> + required-opps = <&rpmhpd_opp_low_svs>;
>>>>>> + };
>>>>>> +
>>>>>> + opp-100000000 {
>>>>>> + opp-hz = /bits/ 64 <100000000>;
>>>>>> + required-opps = <&rpmhpd_opp_svs>;
>>>>>> + };
>>>>>> +
>>>>>> + opp-128000000 {
>>>>>> + opp-hz = /bits/ 64 <128000000>;
>>>>>> + required-opps = <&rpmhpd_opp_nom>;
>>>>>> + };
>>>>>> + };
>>>>>> +
>>>>>> memory@80000000 {
>>>>> Sidenote: memory@ should be moved above opp-*, alphabetically
>>>>>
>>>>> For this:
>>>>>
>>>>> Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>>>>
>>>> You sure? Because before there is already opp for cpu...
>>> Which are called opp-table-cpuN and not cpuN-opp-table, 'm' comes
>>> before 'o'.
>>
>> So you want to have broken order?
>> opp-table-cpu
>> memory
>> opp-table-qup
>> ?
>>
>> They are at least all together in my patch.
> No, I meant:
>
> memory
> opp-table-cpu
> opp-table-qup
OK, I'll correct the opp-table-cpu/memory order in separate patch.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-12-12 9:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 11:57 [PATCH 1/4] arm64: dts: qcom: sc7180: move QUP and QSPI opp tables out of SoC node Krzysztof Kozlowski
2022-12-10 11:57 ` [PATCH 2/4] arm64: dts: qcom: sdm845: move DSI/QUP/QSPI " Krzysztof Kozlowski
2022-12-10 12:28 ` Konrad Dybcio
2022-12-10 11:57 ` [PATCH 3/4] arm64: dts: qcom: sdm845: move sound node out of soc Krzysztof Kozlowski
2022-12-10 12:27 ` Konrad Dybcio
2022-12-10 11:57 ` [PATCH 4/4] arm64: dts: qcom: sm8250: move sound and codec nodes " Krzysztof Kozlowski
2022-12-10 12:31 ` Konrad Dybcio
2022-12-11 20:13 ` Krzysztof Kozlowski
2022-12-11 21:15 ` Dmitry Baryshkov
2022-12-12 8:43 ` Krzysztof Kozlowski
2022-12-12 9:12 ` Konrad Dybcio
2022-12-10 12:29 ` [PATCH 1/4] arm64: dts: qcom: sc7180: move QUP and QSPI opp tables out of SoC node Konrad Dybcio
2022-12-11 20:14 ` Krzysztof Kozlowski
2022-12-12 9:15 ` Konrad Dybcio
2022-12-12 9:17 ` Krzysztof Kozlowski
2022-12-12 9:18 ` Konrad Dybcio
2022-12-12 9:24 ` Krzysztof Kozlowski [this message]
2022-12-28 4:36 ` (subset) " 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=f6c9c9f1-fc10-d9d8-fef1-c43c04d209a8@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=robh+dt@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).