From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Jagadeesh Kona <quic_jkona@quicinc.com>,
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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Ajit Pandey <quic_ajipan@quicinc.com>,
Imran Shaik <quic_imrashai@quicinc.com>,
Taniya Das <quic_tdas@quicinc.com>,
Satya Priya Kakitapalli <quic_skakitap@quicinc.com>
Subject: Re: [PATCH 1/3] arm64: dts: qcom: sa8775p: Add support to scale DDR/L3
Date: Fri, 18 Oct 2024 00:52:26 +0200 [thread overview]
Message-ID: <f9191c4d-a41b-463b-959d-14152cce080e@oss.qualcomm.com> (raw)
In-Reply-To: <20241017-sa8775p-cpufreq-l3-ddr-scaling-v1-1-074e0fb80b33@quicinc.com>
On 17.10.2024 11:28 AM, Jagadeesh Kona wrote:
> Add support to scale DDR and L3 based on CPU frequencies
> on SA8775P platform.
>
> Signed-off-by: Jagadeesh Kona <quic_jkona@quicinc.com>
> ---
> arch/arm64/boot/dts/qcom/sa8775p.dtsi | 33 +++++++++++++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sa8775p.dtsi b/arch/arm64/boot/dts/qcom/sa8775p.dtsi
> index 06bf2ba556b89b643da901857a9aa7cdc7ba90cc..d8b90bd4b1f05604185f015929a1f296799ad6a4 100644
> --- a/arch/arm64/boot/dts/qcom/sa8775p.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sa8775p.dtsi
> @@ -4,6 +4,7 @@
> */
>
> #include <dt-bindings/interconnect/qcom,icc.h>
> +#include <dt-bindings/interconnect/qcom,osm-l3.h>
> #include <dt-bindings/interrupt-controller/arm-gic.h>
> #include <dt-bindings/clock/qcom,rpmh.h>
> #include <dt-bindings/clock/qcom,sa8775p-gcc.h>
> @@ -47,6 +48,10 @@ CPU0: cpu@0 {
> next-level-cache = <&L2_0>;
> capacity-dmips-mhz = <1024>;
> dynamic-power-coefficient = <100>;
> + interconnects = <&gem_noc MASTER_APPSS_PROC QCOM_ICC_TAG_ACTIVE_ONLY
> + &mc_virt SLAVE_EBI1 QCOM_ICC_TAG_ACTIVE_ONLY>,
Please align the '&'s and squash with patch 2. This one doesn't cause
much difference on its own, which makes the commit message misleading
Konrad
next prev parent reply other threads:[~2024-10-17 22:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 9:28 [PATCH 0/3] Add support to scale DDR and L3 on SA8775P Jagadeesh Kona
2024-10-17 9:28 ` [PATCH 1/3] arm64: dts: qcom: sa8775p: Add support to scale DDR/L3 Jagadeesh Kona
2024-10-17 22:52 ` Konrad Dybcio [this message]
2024-11-11 13:10 ` Jagadeesh Kona
2024-10-17 9:28 ` [PATCH 2/3] arm64: dts: qcom: sa8775p: Add CPU OPP tables " Jagadeesh Kona
2024-10-17 15:42 ` Brian Masney
2024-11-11 13:09 ` Jagadeesh Kona
2024-11-14 22:48 ` Dmitry Baryshkov
2024-11-30 14:32 ` Konrad Dybcio
2024-12-03 15:03 ` Jagadeesh Kona
2024-12-04 3:13 ` Dmitry Baryshkov
2024-12-04 8:45 ` Jagadeesh Kona
2024-12-04 11:00 ` Dmitry Baryshkov
2024-12-03 15:03 ` Jagadeesh Kona
2024-10-17 9:28 ` [PATCH 3/3] arm64: dts: qcom: sa8775p: Add LMH interrupts support Jagadeesh Kona
2024-10-26 12:27 ` Konrad Dybcio
2024-11-11 13:10 ` Jagadeesh Kona
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=f9191c4d-a41b-463b-959d-14152cce080e@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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=quic_ajipan@quicinc.com \
--cc=quic_imrashai@quicinc.com \
--cc=quic_jkona@quicinc.com \
--cc=quic_skakitap@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=robh@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