[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260115-ultramarine-wildebeest-of-completion-ea1bc0@quoll>
Date: Thu, 15 Jan 2026 14:32:36 +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 1/8] dt-bindings: thermal: Add Google GS101 TMU
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@...aro.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@...aro.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
> +
> + interrupts:
> + maxItems: 1
> + description: |
> + The combined thermal interrupt signal (Level High).
Drop description
> +
> + 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?
Best regards,
Krzysztof
Powered by blists - more mailing lists