From: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
To: "daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>
Cc: "josef@toxicpanda.com" <josef@toxicpanda.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"rppt@kernel.org" <rppt@kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"pmladek@suse.com" <pmladek@suse.com>,
linux-power <linux-power@fi.rohmeurope.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
"rui.zhang@intel.com" <rui.zhang@intel.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"kai.heng.feng@canonical.com" <kai.heng.feng@canonical.com>,
"mcroce@microsoft.com" <mcroce@microsoft.com>,
"amitk@kernel.org" <amitk@kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
"agross@kernel.org" <agross@kernel.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v7 2/9] reboot: thermal: Export hardware protection shutdown
Date: Sat, 17 Apr 2021 08:49:27 +0000 [thread overview]
Message-ID: <b039aa6253d38219c40fc36c8109f3b48bee4147.camel@fi.rohmeurope.com> (raw)
In-Reply-To: <7e231384-77c9-d32d-a0e0-63b735072b2d@linaro.org>
On Sat, 2021-04-17 at 06:57 +0200, Daniel Lezcano wrote:
> On 14/04/2021 07:52, Matti Vaittinen wrote:
> > Thermal core contains a logic for safety shutdown. System is
> > attempted to
> > be powered off if temperature exceeds safety limits.
> >
> > Currently this can be also utilized by regulator subsystem as a
> > final
> > protection measure if PMICs report dangerous over-voltage, over-
> > current or
> > over-temperature and if per regulator counter measures fail or do
> > not
> > exist.
> >
> > Move this logic to kernel/reboot.c and export the functionality for
> > other
> > subsystems to use. Also replace the mutex with a spinlock to allow
> > using
> > the function from any context.
> >
> > Also the EMIF bus code has implemented a safety shut-down. EMIF
> > does not
> > attempt orderly_poweroff at all. Thus the EMIF code is not
> > converted to use
> > this new function.
> >
> > Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> > ---
> > Changelog
> > v7:
> > - new patch
> >
> > Please note - this patch has received only a minimal amount of
> > testing.
> > (The new API call was tested to shut-down my system at driver probe
> > but
> > no odd corner-cases have been tested).
> >
> > Any testing for thermal shutdown is appreciated.
>
> You can test it easily by enabling the option
> CONFIG_THERMAL_EMULATION
>
> Then in any thermal zone:
>
> Assuming the critical temp is below the one specified in the command:
>
> echo 100000 > /sys/class/thermal/thermal_zone0/emul_temp
>
Thanks Daniel, I will see how that works when I create the next version
:)
Best Regards
Matti Vaittinen
next prev parent reply other threads:[~2021-04-17 8:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 5:51 [PATCH v7 0/9] Extend regulator notification support Matti Vaittinen
2021-04-14 5:51 ` [PATCH v7 1/9] dt_bindings: Add protection limit properties Matti Vaittinen
2021-04-14 5:52 ` [PATCH v7 2/9] reboot: thermal: Export hardware protection shutdown Matti Vaittinen
2021-04-17 4:57 ` Daniel Lezcano
2021-04-17 8:49 ` Vaittinen, Matti [this message]
2021-04-17 5:32 ` Daniel Lezcano
2021-04-17 8:49 ` Matti Vaittinen
2021-04-14 5:52 ` [PATCH v7 3/9] regulator: add warning flags Matti Vaittinen
2021-04-14 5:58 ` [PATCH v7 4/9] regulator: IRQ based event/error notification helpers Matti Vaittinen
2021-04-14 5:58 ` [PATCH v7 5/9] regulator: add property parsing and callbacks to set protection limits Matti Vaittinen
2021-04-14 5:59 ` [PATCH v7 6/9] dt-bindings: regulator: bd9576 add FET ON-resistance for OCW Matti Vaittinen
2021-04-14 5:59 ` [PATCH v7 7/9] regulator: bd9576: Support error reporting Matti Vaittinen
2021-04-14 5:59 ` [PATCH v7 8/9] regulator: bd9576: Fix the driver name in id table Matti Vaittinen
2021-04-14 6:00 ` [PATCH v7 9/9] MAINTAINERS: Add reviewer for regulator irq_helpers Matti Vaittinen
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=b039aa6253d38219c40fc36c8109f3b48bee4147.camel@fi.rohmeurope.com \
--to=matti.vaittinen@fi.rohmeurope.com \
--cc=agross@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=amitk@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=kai.heng.feng@canonical.com \
--cc=keescook@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-power@fi.rohmeurope.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mcroce@microsoft.com \
--cc=pmladek@suse.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robh+dt@kernel.org \
--cc=rppt@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;
as well as URLs for NNTP newsgroup(s).