From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Zhang Rui" <rui.zhang@intel.com>,
"Lukasz Luba" <lukasz.luba@arm.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Lee Jones" <lee@kernel.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Peter Griffin" <peter.griffin@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>,
"Kees Cook" <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
willmcvicker@google.com, jyescas@google.com,
shin.son@samsung.com, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH 1/8] dt-bindings: thermal: Add Google GS101 TMU
Date: Mon, 19 Jan 2026 14:45:07 +0200 [thread overview]
Message-ID: <10cb51ae-9cec-49a9-96c4-757cd1410d8a@linaro.org> (raw)
In-Reply-To: <20260115-ultramarine-wildebeest-of-completion-ea1bc0@quoll>
On 1/15/26 3:32 PM, Krzysztof Kozlowski wrote:
> On Wed, Jan 14, 2026 at 02:16:29PM +0000, Tudor Ambarus wrote:
>> Add device tree bindings for the Google GS101 Thermal Management Unit
>> (TMU).
>>
>> The GS101 TMU is a hybrid thermal solution:
>> 1. Configuration (thresholds, hysteresis) is handled via the Alive
>> Clock and Power Manager (ACPM) firmware protocol.
>> 2. Interrupt handling is handled by the kernel via direct register
>> access.
>>
>> This binding documents the required resources, including the APB clock
>> for register access and the phandle to the associated syscon node.
>>
>> Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
>> ---
>> .../bindings/thermal/google,gs101-tmu-top.yaml | 64 ++++++++++++++++++++++
>> 1 file changed, 64 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/thermal/google,gs101-tmu-top.yaml b/Documentation/devicetree/bindings/thermal/google,gs101-tmu-top.yaml
>> new file mode 100644
>> index 0000000000000000000000000000000000000000..ecf4a315ecf1ea0649c4e96a207d531c696282f4
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/thermal/google,gs101-tmu-top.yaml
>> @@ -0,0 +1,64 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/thermal/google,gs101-tmu-top.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Google GS101 Thermal Management Unit (TMU)
>> +
>> +maintainers:
>> + - Tudor Ambarus <tudor.ambarus@linaro.org>
>> +
>> +description: |
>> + The Google GS101 TMU is a thermal sensor block managed via the ACPM
>> + (Active Core Power Management) firmware. While the firmware handles
>> + the thermal algorithm and thresholds, the kernel requires direct
>> + access to the interrupt pending registers via a syscon interface to
>> + acknowledge and clear thermal interrupts.
>> +
>> +properties:
>> + compatible:
>> + const: google,gs101-tmu-top
>> +
>> + clocks:
>> + maxItems: 1
>> + description: |
>> + Phandle to the APB peripheral clock (PCLK) required to access
>> + the TMU registers.
>
> Drop all the redundancies, so:
> items:
> - description: APB peripheral clock (PCLK) for TMU register access
>
ack
>
>> +
>> + interrupts:
>> + maxItems: 1
>> + description: |
>> + The combined thermal interrupt signal (Level High).
>
> Drop description
>
ack
>> +
>> + syscon:
>
> I feel like suddenly you sent something completely different than what
> have you been working for the past 4 years.
>
>> + $ref: /schemas/types.yaml#/definitions/phandle
>> + description: |
>> + Phandle to the device node representing the TMU System Controller
>> + (compatible with "google,gs101-tmu-syscon"). This node provides the
>> + regmap for INTPEND and INTCLEAR registers.
>> +
>> + "#thermal-sensor-cells":
>> + const: 1
>> +
>
> No supply?
It seems not. Nothing specified downstream. Couldn't find anything in the
schematics that I have either.
I addressed the rest of the feedback in v2.
Thanks,
ta
next prev parent reply other threads:[~2026-01-19 12:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 14:16 [PATCH 0/8] thermal: samsung: Add support for Google GS101 TMU Tudor Ambarus
2026-01-14 14:16 ` [PATCH 1/8] dt-bindings: thermal: Add " Tudor Ambarus
2026-01-15 13:32 ` Krzysztof Kozlowski
2026-01-19 12:45 ` Tudor Ambarus [this message]
2026-01-19 12:57 ` Krzysztof Kozlowski
2026-01-14 14:16 ` [PATCH 2/8] dt-bindings: firmware: google,gs101-acpm-ipc: Add TMU child node Tudor Ambarus
2026-01-14 14:16 ` [PATCH 3/8] dt-bindings: mfd: Add Google GS101 TMU Syscon Tudor Ambarus
2026-01-15 13:36 ` Krzysztof Kozlowski
2026-01-15 14:53 ` Tudor Ambarus
2026-01-15 15:34 ` Krzysztof Kozlowski
2026-01-15 16:10 ` Tudor Ambarus
2026-01-16 8:50 ` Tudor Ambarus
2026-01-16 9:14 ` Krzysztof Kozlowski
2026-01-16 9:18 ` Tudor Ambarus
2026-01-14 14:16 ` [PATCH 4/8] firmware: samsung: acpm: Add TMU protocol support Tudor Ambarus
2026-01-14 14:16 ` [PATCH 5/8] thermal: samsung: Add support for GS101 TMU Tudor Ambarus
2026-01-14 14:16 ` [PATCH 6/8] MAINTAINERS: Add entry for Samsung Exynos ACPM thermal driver Tudor Ambarus
2026-01-14 14:16 ` [PATCH 7/8] arm64: dts: exynos: gs101: Add thermal management unit Tudor Ambarus
2026-01-14 14:16 ` [PATCH 8/8] arm64: defconfig: enable Exynos ACPM thermal support Tudor Ambarus
2026-01-15 13:21 ` Tudor Ambarus
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=10cb51ae-9cec-49a9-96c4-757cd1410d8a@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=bzolnier@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gustavoars@kernel.org \
--cc=jyescas@google.com \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=peter.griffin@linaro.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
--cc=shin.son@samsung.com \
--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