From: Krzysztof Kozlowski <krzk@kernel.org>
To: Peter Griffin <peter.griffin@linaro.org>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Lee Jones <lee@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
tudor.ambarus@linaro.org, andre.draszik@linaro.org,
willmcvicker@google.com, kernel-team@android.com
Subject: Re: [PATCH 2/4] dt-bindings: mfd: syscon: allow two reg regions for gs101-pmu
Date: Fri, 3 Jan 2025 18:14:23 +0100 [thread overview]
Message-ID: <ce9408aa-96a4-498d-8603-01534d9632a2@kernel.org> (raw)
In-Reply-To: <CADrjBPre_zjh+i=_YKYiptiMWT74eWC6LDCveA=dJaQQVwkS0g@mail.gmail.com>
On 30/12/2024 10:10, Peter Griffin wrote:
>
>>
>> Maybe you have here two devices, maybe only one. If it is only one, then
>> it is not a syscon anymore, IMO.
>
> I was going to suggest modelling PMU_INTR_GEN as its own sycon node,
> and then either: -
>
> 1) Updating exynos-pmu driver to additionally take a phandle to
> pmu-intr-gen syscon, and register the hotplug callbacks.
>
> or
>
> 2) Create a new driver named something like exynos-pm or exynos-cpupm
> which obtains the PMU regmap and also a phandle to PMU_INTR_GEN
> syscon, and register the call backs.
>
> Is there any preference from your side over approach 1 or 2, or maybe
> something else entirely?
No preference, choose whatever results in simpler or more readable code.
Option 1 assumes that exynos-pmu on GS101 will drop the "syscon"
compatible, although it still might expose syscon through drivers. Just
the standard binding syscon does not feel fit here.
I don't have the hardware/user manual, so I don't know what PMU_INTR_GEN
really is. GS downstream code has something like PMUCAL, which looks
like separate device.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-03 17:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 16:44 [PATCH 0/4] Fix Google Tensor GS101 CPU hotplug support Peter Griffin
2024-12-13 16:44 ` [PATCH 1/4] dt-bindings: soc: samsung: exynos-pmu: gs101: add pmu-intr-gen reg region Peter Griffin
2024-12-13 16:44 ` [PATCH 2/4] dt-bindings: mfd: syscon: allow two reg regions for gs101-pmu Peter Griffin
2024-12-13 18:26 ` Rob Herring (Arm)
2024-12-16 14:18 ` Rob Herring
2024-12-16 14:27 ` Rob Herring
2024-12-22 12:06 ` Krzysztof Kozlowski
2024-12-30 9:10 ` Peter Griffin
2025-01-03 17:14 ` Krzysztof Kozlowski [this message]
2025-01-06 13:41 ` Peter Griffin
2024-12-13 16:44 ` [PATCH 3/4] arm64: dts: exynos: gs101: add pmu-intr-gen regs to the PMU node Peter Griffin
2024-12-13 16:44 ` [PATCH 4/4] soc: samsung: exynos-pmu: enable CPU hotplug support for gs101 Peter Griffin
2024-12-22 12:17 ` Krzysztof Kozlowski
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=ce9408aa-96a4-498d-8603-01534d9632a2@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=lee@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=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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;
as well as URLs for NNTP newsgroup(s).