On 23/08/2023 19:33, Fabio Estevam wrote: > From: Fabio Estevam <festevam@xxxxxxx> > > Currently, after the board reaches the critical temperature, the system > goes through a poweroff mechanism. > > In some cases, such behavior does not suit well, as the board may be > unattended in the field and rebooting may be a better approach. > > The bootloader may also check the temperature and only allow the boot to > proceed when the temperature is below a certain threshold. > > Introduce the 'nxp,reboot-on-critical' property to indicate that the > board will go through a reboot after the critical temperature is reached. > > When this property is absent, the default behavior of forcing a shutdown > is kept. > > Signed-off-by: Fabio Estevam <festevam@xxxxxxx> > --- > .../devicetree/bindings/thermal/imx8mm-thermal.yaml | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/thermal/imx8mm-thermal.yaml b/Documentation/devicetree/bindings/thermal/imx8mm-thermal.yaml > index d2c1e4573c32..9ac70360fd35 100644 > --- a/Documentation/devicetree/bindings/thermal/imx8mm-thermal.yaml > +++ b/Documentation/devicetree/bindings/thermal/imx8mm-thermal.yaml > @@ -32,6 +32,12 @@ properties: > clocks: > maxItems: 1 > > + nxp,reboot-on-critical: > + description: Property to indicate that the system will go through a reboot > + after the critical temperature is reached. If absent, the system will > + go through shutdown after the critical temperature is reached. And if Linux changes the behavior of critical temperature to be "reboot" instead of "poweroff", what happens with this property? You add now property for a SW policy depending on one given implementation. Not suitable for bindings, sorry. Best regards, Krzysztof
