Re: [PATCH v3 1/6] dt-bindings: thermal: thermal-zones: add hardware-binning trip properties

From: Rob Herring

Date: Wed Nov 18 2026 - 15:51:05 EST


On Fri, Nov 13, 2026 at 02:13:44PM +0530, Gaurav Kohli wrote:
> From: Amit Kucheria <amit.kucheria@xxxxxxxxxxxxxxxx>
>
> Differences in SoC packaging can be used to provide multiple SoC SKUs at
> different thermal and performance characteristics. The underlying SoC
> remains the same except for how much heat the packaging can dissipate,
> thereby influencing the critical trip point at which an SoC SKU needs to
> be throttled. This SKU-specific data is typically burned into fuses
> during manufacturing and can be read back at runtime.
>
> Add two optional trip-point properties to describe this:
>
> - 'temperature-bin': an array of per-bin trip temperatures, used
> instead of 'temperature' when the trip depends on the hardware
> revision encoded in fuses.
>
> - 'thermal-hw-bin': one or more bitmask groups describing the hardware
> revisions for which a trip point is valid, modeled on the
> 'opp-supported-hw' property of the OPP framework.
>
> Signed-off-by: Amit Kucheria <amit.kucheria@xxxxxxxxxxxxxxxx>
> Signed-off-by: Gaurav Kohli <gaurav.kohli@xxxxxxxxxxxxxxxx>
> ---
> .../devicetree/bindings/thermal/thermal-zones.yaml | 60 +++++++++++++++++++++-
> 1 file changed, 59 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/thermal/thermal-zones.yaml b/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
> index 999ad40a20d5..cb9a8c96d053 100644
> --- a/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
> +++ b/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
> @@ -152,6 +152,58 @@ patternProperties:
> situation where the trip gets constantly triggered soon after
> cooling action is removed.
>
> + temperature-bin:

Use the standard unit suffix.

> + $ref: /schemas/types.yaml#/definitions/int32-array
> + items:
> + minimum: -273000
> + maximum: 200000

minItems: 2
maxItems: 32 ?