From: Krzysztof Kozlowski <krzk@kernel.org>
To: webgeek1234@gmail.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
Subject: Re: [PATCH 2/3] arm64: dts: qcom: sm8550: add cpu interconnect nodes
Date: Sun, 8 Feb 2026 10:05:08 +0100 [thread overview]
Message-ID: <eb423286-c26b-4e03-9e9e-af6718e459cc@kernel.org> (raw)
In-Reply-To: <20260207-sm8550-ddr-bw-scaling-v1-2-d96c3f39ac4b@gmail.com>
On 08/02/2026 02:28, Aaron Kling via B4 Relay wrote:
> From: Aaron Kling <webgeek1234@gmail.com>
>
> Add the interconnect entry for each cpu, with 3 different paths:
> - CPU to Last Level Cache Controller (LLCC)
> - Last Level Cache Controller (LLCC) to DDR
> - L3 Cache from CPU to DDR interface
>
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---
> arch/arm64/boot/dts/qcom/sm8550.dtsi | 49 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 49 insertions(+)
>
This patch should be squashed. You add interconnect and use it,
otherwise it is pretty pointless or even negatively impacting (syncing
without interconnect paths).
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-08 9:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-08 1:28 [PATCH 0/3] arm64: qcom: sm8550: add DDR, LLCC & L3 CPU bandwidth scaling Aaron Kling via B4 Relay
2026-02-08 1:28 ` [PATCH 1/3] arm64: dts: qcom: sm8550: add OSM L3 node Aaron Kling via B4 Relay
2026-02-09 9:04 ` Konrad Dybcio
2026-02-11 22:36 ` Aaron Kling
2026-02-08 1:28 ` [PATCH 2/3] arm64: dts: qcom: sm8550: add cpu interconnect nodes Aaron Kling via B4 Relay
2026-02-08 9:05 ` Krzysztof Kozlowski [this message]
2026-02-08 1:28 ` [PATCH 3/3] arm64: dts: qcom: sm8550: add cpu OPP table with DDR, LLCC & L3 bandwidths Aaron Kling via B4 Relay
2026-02-09 16:56 ` Neil Armstrong
2026-02-12 11:59 ` Konrad Dybcio
2026-02-18 2:06 ` Aaron Kling
2026-02-18 11:09 ` Konrad Dybcio
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=eb423286-c26b-4e03-9e9e-af6718e459cc@kernel.org \
--to=krzk@kernel.org \
--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=robh@kernel.org \
--cc=webgeek1234@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