From: Imran Shaik <quic_imrashai@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Ajit Pandey <quic_ajipan@quicinc.com>,
Taniya Das <quic_tdas@quicinc.com>,
Jagadeesh Kona <quic_jkona@quicinc.com>,
Satya Priya Kakitapalli <quic_skakitap@quicinc.com>,
<linux-pm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: qcs8300: Add cpufreq scaling node
Date: Thu, 17 Apr 2025 12:09:04 +0530 [thread overview]
Message-ID: <b592a51d-41f3-4a2b-a9f3-0f45c9bef967@quicinc.com> (raw)
In-Reply-To: <ce00f7e3-86a1-4fdd-9274-c1a9896c0f12@oss.qualcomm.com>
On 4/14/2025 4:36 PM, Konrad Dybcio wrote:
> On 3/13/25 7:03 AM, Imran Shaik wrote:
>> Add cpufreq-hw node to support cpufreq scaling on QCS8300.
>>
>> Signed-off-by: Imran Shaik <quic_imrashai@quicinc.com>
>> ---
>
> [...]
>
>> + cpufreq_hw: cpufreq@18591000 {
>> + compatible = "qcom,qcs8300-cpufreq-epss", "qcom,cpufreq-epss";
>> + reg = <0x0 0x18591000 0x0 0x1000>,
>> + <0x0 0x18594000 0x0 0x1000>,
>> + <0x0 0x18593000 0x0 0x1000>;
>> + reg-names = "freq-domain0", "freq-domain1", "freq-domain2";
>
> Please turn these into vertical lists> +
>> + interrupts = <GIC_SPI 31 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 86 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 32 IRQ_TYPE_LEVEL_HIGH>;
>> + interrupt-names = "dcvsh-irq-0", "dcvsh-irq-1", "dcvsh-irq-2";
>
> Since these labels don't match the hardware anyway, please sort them by address
>
Sure, I will take care of the above comments and post another series.
Thanks,
Imran
> Konrad
>
>> +
>> + clocks = <&rpmhcc RPMH_CXO_CLK>, <&gcc GCC_GPLL0>;
>> + clock-names = "xo", "alternate";
>> +
>> + #freq-domain-cells = <1>;
>> + };
>> +
>> remoteproc_gpdsp: remoteproc@20c00000 {
>> compatible = "qcom,qcs8300-gpdsp-pas", "qcom,sa8775p-gpdsp0-pas";
>> reg = <0x0 0x20c00000 0x0 0x10000>;
>>
prev parent reply other threads:[~2025-04-17 6:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 6:03 [PATCH 0/2] Add support for cpufreq scaling on QCS8300 Imran Shaik
2025-03-13 6:03 ` [PATCH 1/2] dt-bindings: cpufreq: cpufreq-qcom-hw: Add QCS8300 compatible Imran Shaik
2025-03-13 8:52 ` Krzysztof Kozlowski
2025-03-17 6:04 ` Viresh Kumar
2025-03-13 9:18 ` Krzysztof Kozlowski
2025-03-13 6:03 ` [PATCH 2/2] arm64: dts: qcom: qcs8300: Add cpufreq scaling node Imran Shaik
2025-04-14 11:06 ` Konrad Dybcio
2025-04-17 6:39 ` Imran Shaik [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=b592a51d-41f3-4a2b-a9f3-0f45c9bef967@quicinc.com \
--to=quic_imrashai@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_ajipan@quicinc.com \
--cc=quic_jkona@quicinc.com \
--cc=quic_skakitap@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=viresh.kumar@linaro.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