From: Fabio Estevam <festevam@gmail.com>
To: daniel.lezcano@linaro.org
Cc: rafael@kernel.org, amitk@kernel.org, rui.zhang@intel.com,
linux-pm@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
robh+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, Fabio Estevam <festevam@denx.de>
Subject: [PATCH v3 2/3] reboot: Introduce hw_protection_reboot()
Date: Mon, 28 Aug 2023 16:59:01 -0300 [thread overview]
Message-ID: <20230828195902.1645169-2-festevam@gmail.com> (raw)
In-Reply-To: <20230828195902.1645169-1-festevam@gmail.com>
From: Fabio Estevam <festevam@denx.de>
Introduce hw_protection_reboot() to trigger an emergency reboot.
It is a counterpart of hw_protection_shutdown() with the difference
that it will force a reboot instead of shutdown.
The motivation for doing this is to allow the thermal subystem
to trigger a reboot when the temperature reaches the critical
temperature.
Signed-off-by: Fabio Estevam <festevam@denx.de>
---
Changes since v2:
- None
include/linux/reboot.h | 1 +
kernel/reboot.c | 34 ++++++++++++++++++++++++++++++++++
2 files changed, 35 insertions(+)
diff --git a/include/linux/reboot.h b/include/linux/reboot.h
index 2b6bb593be5b..4a319bc24f6a 100644
--- a/include/linux/reboot.h
+++ b/include/linux/reboot.h
@@ -174,6 +174,7 @@ void ctrl_alt_del(void);
extern void orderly_poweroff(bool force);
extern void orderly_reboot(void);
+void hw_protection_reboot(const char *reason, int ms_until_forced);
void hw_protection_shutdown(const char *reason, int ms_until_forced);
/*
diff --git a/kernel/reboot.c b/kernel/reboot.c
index 3bba88c7ffc6..05333ae8bc6b 100644
--- a/kernel/reboot.c
+++ b/kernel/reboot.c
@@ -952,6 +952,40 @@ static void hw_failure_emergency_poweroff(int poweroff_delay_ms)
msecs_to_jiffies(poweroff_delay_ms));
}
+/**
+ * hw_protection_reboot - Trigger an emergency system reboot
+ *
+ * @reason: Reason of emergency reboot to be printed.
+ * @ms_until_forced: Time to wait for orderly reboot before tiggering a
+ * forced reboot. Negative value disables the forced
+ * reboot.
+ *
+ * Initiate an emergency system reboot in order to protect hardware from
+ * further damage. Usage examples include a thermal protection.
+ *
+ * NOTE: The request is ignored if protection reboot is already pending even
+ * if the previous request has given a large timeout for forced reboot.
+ * Can be called from any context.
+ */
+void hw_protection_reboot(const char *reason, int ms_until_forced)
+{
+ static atomic_t allow_proceed = ATOMIC_INIT(1);
+
+ pr_emerg("HARDWARE PROTECTION reboot (%s)\n", reason);
+
+ /* Reboot should be initiated only once. */
+ if (!atomic_dec_and_test(&allow_proceed))
+ return;
+
+ /*
+ * Queue a backup emergency reboot in the event of
+ * orderly_reboot failure
+ */
+ hw_failure_emergency_poweroff(ms_until_forced);
+ orderly_reboot();
+}
+EXPORT_SYMBOL_GPL(hw_protection_reboot);
+
/**
* hw_protection_shutdown - Trigger an emergency system poweroff
*
--
2.34.1
next prev parent reply other threads:[~2023-08-28 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 19:59 [PATCH v3 1/3] dt-bindings: thermal-zones: Document critical-action Fabio Estevam
2023-08-28 19:59 ` Fabio Estevam [this message]
2023-08-28 19:59 ` [PATCH v3 3/3] thermal: thermal_core: Allow rebooting after critical temp Fabio Estevam
2023-08-29 6:41 ` [PATCH v3 1/3] dt-bindings: thermal-zones: Document critical-action Krzysztof Kozlowski
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=20230828195902.1645169-2-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=amitk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@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).