mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Imre Kaloz <kaloz@kernel.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	Lee Jones <lee@kernel.org>, Sashiko <sashiko-bot@kernel.org>,
	mfd@lists.linux.dev
Subject: [PATCH v2 2/2] MIPS: SGI-IP30: shut down cleanly on a power button press
Date: Mon,  2 Nov 2026 10:41:05 +0100	[thread overview]
Message-ID: <20261102094106.21300-3-kaloz@kernel.org> (raw)
In-Reply-To: <20261102094106.21300-1-kaloz@kernel.org>

The power button raises a kickstart interrupt on the DS1687, and
rtc-ds1685 cuts power at once unless the platform supplies a
prepare_poweroff hook. Supply one that starts an orderly power-off,
cutting power directly on a second press or after 120 seconds.

Power-off drives the RTC's index/data register pair, so only the first
of several concurrent callers proceeds and the rest wait. The timeout
holds the device lock against an unbind of rtc-ds1685.

Reported-by: Sashiko <sashiko-bot@kernel.org>
Closes: https://lore.kernel.org/all/sashiko-outbox-169717@kernel.org/
Signed-off-by: Imre Kaloz <kaloz@kernel.org>
---
 arch/mips/include/asm/sgi/heart.h |  2 ++
 arch/mips/sgi-ip30/ip30-power.c   | 60 +++++++++++++++++++++++++++++++
 drivers/mfd/ioc3.c                |  6 ++++
 3 files changed, 68 insertions(+)

diff --git a/arch/mips/include/asm/sgi/heart.h b/arch/mips/include/asm/sgi/heart.h
index c224c2e3575a..736cabb7fdbb 100644
--- a/arch/mips/include/asm/sgi/heart.h
+++ b/arch/mips/include/asm/sgi/heart.h
@@ -317,6 +317,8 @@ struct ip30_heart_regs {		/* 0x0ff00000 */
 
 extern struct ip30_heart_regs __iomem *heart_regs;
 
+void ip30_prepare_poweroff(void);
+
 #define heart_read	____raw_readq
 #define heart_write	____raw_writeq
 
diff --git a/arch/mips/sgi-ip30/ip30-power.c b/arch/mips/sgi-ip30/ip30-power.c
index b1b33c9cfd76..cff8f4875429 100644
--- a/arch/mips/sgi-ip30/ip30-power.c
+++ b/arch/mips/sgi-ip30/ip30-power.c
@@ -7,6 +7,7 @@
  *               2009 Johannes Dickgreber <tanzy@gmx.de>
  */
 
+#include <linux/console.h>
 #include <linux/init.h>
 #include <linux/kernel.h>
 #include <linux/module.h>
@@ -17,6 +18,8 @@
 #include <linux/interrupt.h>
 #include <linux/platform_device.h>
 #include <linux/pm.h>
+#include <linux/reboot.h>
+#include <linux/workqueue.h>
 
 #include <asm/reboot.h>
 #include <asm/sgi/heart.h>
@@ -32,6 +35,8 @@ static void __noreturn ip30_machine_restart(char *cmd)
 	unreachable();
 }
 
+static atomic_t ip30_power_off_claimed = ATOMIC_INIT(0);
+
 static void ip30_machine_power_off(void)
 {
 	struct device *dev;
@@ -48,14 +53,69 @@ static void ip30_machine_power_off(void)
 		return;
 	}
 
+	/*
+	 * The RTC registers are reached through an index/data pair, so one
+	 * CPU at a time may drive them, and a second button press, the
+	 * timeout and pm_power_off can arrive together.  Interrupts go off
+	 * first so the claimant cannot be preempted by a waiter on its CPU;
+	 * the waiters spin until the power drops.
+	 */
+	local_irq_disable();
+	if (atomic_xchg(&ip30_power_off_claimed, 1))
+		for (;;)
+			cpu_relax();
+
 	/* Devices losing power may still interrupt; keep their handlers out. */
 	for (cpu = 0; cpu < HEART_MAX_CPUS; cpu++)
 		heart_write(HEART_CLR_ALL_MASK, &heart_regs->imr[cpu]);
 	heart_write(HEART_ACK_ALL_MASK, &heart_regs->clear_isr);
 
+	/*
+	 * Nothing schedules before the power drops, so the RTC's message must
+	 * be printed from this context, not left to the console thread.  The
+	 * emergency section is never left.
+	 */
+	nbcon_cpu_emergency_enter();
 	ds1685_rtc_poweroff(to_platform_device(dev));
 }
 
+#define IP30_POWERDOWN_TIMEOUT	120	/* seconds */
+
+static bool ip30_shutting_down;
+
+static void ip30_power_timeout(struct work_struct *work)
+{
+	struct device *dev;
+
+	dev = bus_find_device_by_name(&platform_bus_type, NULL, "rtc-ds1685");
+	if (!dev)
+		return;
+
+	/*
+	 * Unbinding rtc-ds1685 frees the RTC under the device lock, so hold
+	 * it across the drvdata check and the power-off.
+	 */
+	device_lock(dev);
+	ip30_machine_power_off();
+	device_unlock(dev);
+	put_device(dev);
+}
+
+static DECLARE_DELAYED_WORK(ip30_power_work, ip30_power_timeout);
+
+/* Called by the RTC driver when the power button is pressed. */
+void ip30_prepare_poweroff(void)
+{
+	/* A second press powers off at once. */
+	if (ip30_shutting_down)
+		ip30_machine_power_off();
+
+	/* Shut down through userspace, powering off anyway if it stalls. */
+	ip30_shutting_down = true;
+	orderly_poweroff(true);
+	schedule_delayed_work(&ip30_power_work, IP30_POWERDOWN_TIMEOUT * HZ);
+}
+
 static int __init ip30_reboot_setup(void)
 {
 	_machine_restart = ip30_machine_restart;
diff --git a/drivers/mfd/ioc3.c b/drivers/mfd/ioc3.c
index 5f8ac364b610..8f603651cc8e 100644
--- a/drivers/mfd/ioc3.c
+++ b/drivers/mfd/ioc3.c
@@ -24,6 +24,9 @@
 
 #include <asm/pci/bridge.h>
 #include <asm/sn/ioc3.h>
+#ifdef CONFIG_SGI_IP30
+#include <asm/sgi/heart.h>
+#endif
 
 #define IOC3_IRQ_SERIAL_A	6
 #define IOC3_IRQ_SERIAL_B	15
@@ -321,6 +324,9 @@ static struct ds1685_rtc_platform_data ip30_rtc_platform_data = {
 	.no_irq = false,
 	.uie_unsupported = true,
 	.access_type = ds1685_reg_indirect,
+#ifdef CONFIG_SGI_IP30
+	.plat_prepare_poweroff = ip30_prepare_poweroff,
+#endif
 };
 
 static const struct resource ioc3_rtc_ds1685_resources[] = {
-- 
2.47.3


  parent reply	other threads:[~2026-11-02  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02  9:41 [PATCH v2 0/2] MIPS: SGI-IP30: power off through the RTC Imre Kaloz
2026-11-02  9:41 ` [PATCH v2 1/2] MIPS: SGI-IP30: power off through the DS1687 RTC Imre Kaloz
2026-11-02  9:41 ` Imre Kaloz [this message]
     [not found]   ` <sashiko-outbox-193229@kernel.org>
2026-11-02 11:29     ` [PATCH v2 2/2] MIPS: SGI-IP30: shut down cleanly on a power button press Imre Kaloz

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=20261102094106.21300-3-kaloz@kernel.org \
    --to=kaloz@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=mfd@lists.linux.dev \
    --cc=sashiko-bot@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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

all inboxes | Powered by JetHome®