From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: me@fromdisposition.org, Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@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 1/2] arm64: dts: qcom: sm8350: Add the EPSS L3 provider
Date: Fri, 16 Oct 2026 10:45:40 +0200 [thread overview]
Message-ID: <380b8aaf-33d2-4c9f-a746-10f080711f22@oss.qualcomm.com> (raw)
In-Reply-To: <20261016-sm8350-cpu-bw-v1-1-044ac6dc9565@fromdisposition.org>
On 10/16/26 8:01 AM, Demeter Barna via B4 Relay wrote:
> From: Demeter Barna <me@fromdisposition.org>
>
> Add the EPSS L3 block, already documented as qcom,sm8350-epss-l3, so
> that the CPUs can vote for the L3 frequency.
>
> Unlike on SM8250, the L3 is voted through the L3_VOTE register, as the
> downstream driver for this SoC does. The generic qcom,epss-l3 fallback
> selects that, so no driver change is needed.
This pargraph is mildly useful in the context of this commit
anywho
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2026-10-16 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 6:01 [PATCH 0/2] arm64: dts: qcom: sm8350: Scale L3 and memory bandwidth with the CPUs Demeter Barna via B4 Relay
2026-10-16 6:01 ` [PATCH 1/2] arm64: dts: qcom: sm8350: Add the EPSS L3 provider Demeter Barna via B4 Relay
2026-10-16 8:45 ` Konrad Dybcio [this message]
2026-10-16 6:01 ` [PATCH 2/2] arm64: dts: qcom: sm8350: Add CPU OPP tables with memory bandwidth Demeter Barna via B4 Relay
2026-10-16 8:45 ` 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=380b8aaf-33d2-4c9f-a746-10f080711f22@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abelvesa@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=me@fromdisposition.org \
--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
all inboxes | Powered by JetHome®