From: Fabio Estevam <festevam@denx.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: daniel.lezcano@linaro.org, linux-pm@vger.kernel.org,
rafael@kernel.org, amitk@kernel.org, rui.zhang@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] thermal: imx8mm: Allow reboot after critical temperature
Date: Thu, 24 Aug 2023 12:25:31 -0300 [thread overview]
Message-ID: <cb7cd8c8eb68320848b3274390a5c373@denx.de> (raw)
In-Reply-To: <20230824143652.529624-1-festevam@gmail.com>
Hi Daniel,
On 24/08/2023 11:36, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
>
> Currently, after the SoC reaches the critical temperature, the board
> 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 a 'reboot_on_crit' sysfs entry to indicate that the board
> will go through a reboot after the critical temperature is reached.
>
> By default, the original shutdown behavior is preserved.
>
> Tested on a imx8mm-evk board by issuing the command below:
>
> echo 1 >
> /sys/devices/platform/soc@0/30000000.bus/30260000.tmu/reboot_on_crit
>
> Confirmed that it goes through a reboot after the critical temperature
> is reached.
>
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> ---
> Changes since v3:
> - Add a sysfs entry.
After thinking more about this, I am happier with the previous v3.
The decision to reboot or shutdown is not something that needs to be
changed in runtime.
If the module_param() approach from v3 could be accepted, I think it
would be
a better solution.
Thanks
prev parent reply other threads:[~2023-08-24 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 14:36 [PATCH v4] thermal: imx8mm: Allow reboot after critical temperature Fabio Estevam
2023-08-24 15:25 ` Fabio Estevam [this message]
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=cb7cd8c8eb68320848b3274390a5c373@denx.de \
--to=festevam@denx.de \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.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