From: "Alexey Klimov" <alexey.klimov@linaro.org>
To: "Peter Griffin" <peter.griffin@linaro.org>,
"Alexey Klimov" <alexey.klimov@linaro.org>
Cc: "Sam Protsenko" <semen.protsenko@linaro.org>,
linux-samsung-soc@vger.kernel.org,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 7/8] soc: samsung: exynos-pmu: add Exynos850 CPU hotplug support
Date: Tue, 17 Mar 2026 14:11:27 +0000 [thread overview]
Message-ID: <DH549OXPHXQA.265AMHWFSNK5C@linaro.org> (raw)
In-Reply-To: <CADrjBPoLCDnvWocLYrg-zGRZNcBvPVYnUi4L7DA78m7QmkmQdQ@mail.gmail.com>
Hi Peter,
On Fri Mar 6, 2026 at 2:15 PM GMT, Peter Griffin wrote:
> On Thu, 26 Feb 2026 at 15:47, Alexey Klimov <alexey.klimov@linaro.org> wrote:
>>
>> Some Exynos-based SoCs require specific set of writes/updates to PMU
>> and PMU intr gen blocks in order to put a CPU or a group of CPUs into
>> a different sleep states or prepare these entities for a CPU_OFF.
>> The same is valid for a reverse procedures like wake-ups or CPU(s)
>> online. Without these writes/updates the CPU(s) wake-up or online
>> fails.
>> Add support for Exynos850-based SoCs for PMU and PMU intr gen write/update
>> sequences.
>> While at this, also add description of Exynos850 PMU registers.
>>
>> Signed-off-by: Alexey Klimov <alexey.klimov@linaro.org>
>> ---
>> drivers/soc/samsung/exynos-pmu.c | 86 +++++++++++++++++++++++++++--
>> include/linux/soc/samsung/exynos-regs-pmu.h | 5 ++
>> 2 files changed, 87 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/soc/samsung/exynos-pmu.c b/drivers/soc/samsung/exynos-pmu.c
>> index 0967fa56708a..7b9b8e22d91b 100644
>> --- a/drivers/soc/samsung/exynos-pmu.c
>> +++ b/drivers/soc/samsung/exynos-pmu.c
>> @@ -118,6 +118,10 @@ static const struct regmap_config regmap_pmu_intr = {
>> .use_raw_spinlock = true,
>> };
>>
>> +const struct exynos_pmu_data exynos850_pmu_data = {
>> + .pmu_cpuhp = true,
>> +};
>> +
>
> You may want to consider having an e850-pmu.c file to contain the e850
> specific data and hooks.
>
> Andre recently moved some of the gs101-specific parts into gs101-pmu.c
> (although not the actual gs101 online/offline hooks). Now that more
> SoCs are being added it could be a good time for exynos-pmu to contain
> only the generic code and the <soc>-pmu.c file having the
> peculiarities/hooks for the specific SoC.
Thanks. Yeah. That's why it was sent as an RFC to get pointers where
to place things properly. I'll update it.
[..]
>> - pmu_context->cpu_pmu_online = __gs101_cpu_pmu_online;
>> - pmu_context->cpu_pmu_offline = __gs101_cpu_pmu_offline;
>> + if (of_machine_is_compatible("google,gs101")) {
>> + pmu_context->cpu_pmu_online = __gs101_cpu_pmu_online;
>> + pmu_context->cpu_pmu_offline = __gs101_cpu_pmu_offline;
>> + }
>> +
>> + if (of_machine_is_compatible("samsung,exynos850")) {
>> + pmu_context->cpu_pmu_online = __exynos850_cpu_pmu_online;
>> + pmu_context->cpu_pmu_offline = __exynos850_cpu_pmu_offline;
>>
>
> There should be no compatibles inside probe (that rule applies to all
> drivers & subsystems). Instead use the driver match data
> (exynos_pmu_data).
Thanks. Yep, I'll update it.
BR,
Alexey
next prev parent reply other threads:[~2026-03-17 14:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 15:47 [PATCH RFC 0/8] Exynos850 CPU hotplug support and pmu_intr_gen cleanup Alexey Klimov
2026-02-26 15:47 ` [PATCH RFC 1/8] dt-bindings: soc: move and rename google,gs101-pmu-intr-gen schema under soc/samsung/ Alexey Klimov
2026-03-06 14:22 ` Peter Griffin
2026-03-07 17:03 ` Krzysztof Kozlowski
2026-03-23 15:42 ` Alexey Klimov
2026-03-23 16:03 ` Krzysztof Kozlowski
2026-03-23 16:33 ` Alexey Klimov
2026-02-26 15:47 ` [PATCH RFC 2/8] dt-bindings: soc: samsung: exynos850-pmu-intr-gen: add Exynos850 compatible Alexey Klimov
2026-02-26 15:47 ` [PATCH RFC 3/8] dt-bindings: soc: samsung: exynos-pmu: add samsung,pmu-intr-gen phandle Alexey Klimov
2026-02-26 15:47 ` [PATCH RFC 4/8] dt-bindings: soc: samsung: exynos-pmu: deprecate google,pmu-intr-gen-syscon Alexey Klimov
2026-02-26 15:47 ` [PATCH RFC 5/8] soc: samsung: exynos-pmu: rename GS101_INTR_* regs to EXYNOS_INTR_* Alexey Klimov
2026-02-26 15:47 ` [PATCH RFC 6/8] soc: samsung: exynos-pmu: generalise GS101 PMU intr gen for Exynos SoCs Alexey Klimov
2026-02-26 15:47 ` [PATCH RFC 7/8] soc: samsung: exynos-pmu: add Exynos850 CPU hotplug support Alexey Klimov
2026-03-06 14:15 ` Peter Griffin
2026-03-17 14:11 ` Alexey Klimov [this message]
2026-02-26 15:47 ` [PATCH RFC 8/8] arm64: dts: exynos850: add PMU interrupt generation node Alexey Klimov
2026-03-06 13:44 ` Peter Griffin
2026-03-17 14:07 ` Alexey Klimov
2026-03-07 17:08 ` Krzysztof Kozlowski
2026-03-23 15:37 ` Alexey Klimov
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=DH549OXPHXQA.265AMHWFSNK5C@linaro.org \
--to=alexey.klimov@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=tudor.ambarus@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