[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0176a63a-6b04-4e30-b718-847133882050@kernel.org>
Date: Fri, 16 Jan 2026 10:14:28 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Tudor Ambarus <tudor.ambarus@...aro.org>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>, Zhang Rui <rui.zhang@...el.com>,
Lukasz Luba <lukasz.luba@....com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Lee Jones <lee@...nel.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Peter Griffin <peter.griffin@...aro.org>,
André Draszik <andre.draszik@...aro.org>,
Bartlomiej Zolnierkiewicz <bzolnier@...il.com>, Kees Cook <kees@...nel.org>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>, willmcvicker@...gle.com,
jyescas@...gle.com, shin.son@...sung.com, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH 3/8] dt-bindings: mfd: Add Google GS101 TMU Syscon
On 16/01/2026 09:50, Tudor Ambarus wrote:
>
> Because of the hybrid approach I'm arguing the ACPM child node does not
> fully describe the hardware, and it's just a firmware abstraction.
> So option 2/ would be to have just the TMU IP block described with a
> phandle to the ACPM IPC:
>
> soc: soc@0 {
> tmu@...a0000 {
> compatible = "google,gs101-tmu-top";
> reg = <0x100a0000 0x800>;
> clocks = <&cmu_misc CLK_GOUT_MISC_TMU_TOP_PCLK>;
> interrupts = <GIC_SPI 769 IRQ_TYPE_LEVEL_HIGH 0>;
>
> /* The "Firmware Phandle" approach */
> samsung,acpm-ipc = <&acpm_ipc>;
>
> #thermal-sensor-cells = <1>;
Yes, this one, I think it's the best representation.
Best regards,
Krzysztof
Powered by blists - more mailing lists