[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240528170000.GA903992-robh@kernel.org>
Date: Tue, 28 May 2024 12:00:00 -0500
From: Rob Herring <robh@...nel.org>
To: Alexandre Bailon <abailon@...libre.com>
Cc: rafael@...nel.org, daniel.lezcano@...aro.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
rui.zhang@...el.com, lukasz.luba@....com, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 4/6] dt-bindings: thermal: Add a property to select
the aggregation type
On Fri, May 24, 2024 at 04:31:48PM +0200, Alexandre Bailon wrote:
> This adds a new property named "aggregation" that could be used to
> select the aggregation type when there are multiple sensors assigned
> to a thermal zone.
>
> Signed-off-by: Alexandre Bailon <abailon@...libre.com>
> ---
> .../devicetree/bindings/thermal/thermal-zones.yaml | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/thermal/thermal-zones.yaml b/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
> index fa7a72e2ba44..e6e4b46773e3 100644
> --- a/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
> +++ b/Documentation/devicetree/bindings/thermal/thermal-zones.yaml
> @@ -111,6 +111,14 @@ patternProperties:
> coefficients are ordered and are matched with sensors by means of the
> sensor ID. Additional coefficients are interpreted as constant offset.
>
> + aggregation:
> + $ref: /schemas/types.yaml#/definitions/string
> + enum:
> + - avg
> + - max
> + description:
> + Aggregation type to use compute a temperature from multiple sensors.
This is optional, so what's the default? I suppose you could make it
required if more than 1 sensor.
A boolean could work here as well unless you think there might be a 3rd
algorithm.
> +
> sustainable-power:
> $ref: /schemas/types.yaml#/definitions/uint32
> description:
> --
> 2.44.1
>
Powered by blists - more mailing lists