From patchwork Thu Dec 19 07:31:21 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ahmad Fatoum X-Patchwork-Id: 13914593 Received: from metis.whiteo.stw.pengutronix.de (metis.whiteo.stw.pengutronix.de [185.203.201.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D122921858D for ; Thu, 19 Dec 2024 07:32:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.203.201.7 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734593522; cv=none; b=EwHGRQxH1Oc5SAdV0Ed1AP/TH2fY/a/VLyVq6K03WamCVvVxD6GhP75FuwXhWI8+dGz3MpjzX6Prlvyrtg+4zPH8atFrzPmMxlecdTz0cbgP0saDaoub4sRoewpaDkwlseQ2/lhbgyBd6Nf6prMnsD65lyg6JhKk2rNBMj8LIEE= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734593522; c=relaxed/simple; bh=7RTxGMyJEufyqyVhoa0s2MPskpvrfhslVr1jsWa99KE=; h=From:Subject:Date:Message-Id:MIME-Version:Content-Type:To:Cc; b=a5oJiP0Zi24yNdzARpTrCZVQLGUKLhrYR/lXjQBFjP40N1bv7d1n1No6fYGVISXFr0N2SxyAZfYSykRB7bWc0S4Y2lCJunnSctICp9TORNamsDGnead2yQ0s8lBlYHlAYBlNN4OCl30sH2WQCjQUH26CgwqFeHNzCgNV9K8sBxQ= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=pengutronix.de; spf=pass smtp.mailfrom=pengutronix.de; arc=none smtp.client-ip=185.203.201.7 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=pengutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=pengutronix.de Received: from drehscheibe.grey.stw.pengutronix.de ([2a0a:edc0:0:c01:1d::a2]) by metis.whiteo.stw.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tOB0O-00088T-1S; Thu, 19 Dec 2024 08:31:32 +0100 Received: from dude05.red.stw.pengutronix.de ([2a0a:edc0:0:1101:1d::54]) by drehscheibe.grey.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tOB0L-004APo-1p; Thu, 19 Dec 2024 08:31:30 +0100 Received: from localhost ([::1] helo=dude05.red.stw.pengutronix.de) by dude05.red.stw.pengutronix.de with esmtp (Exim 4.96) (envelope-from ) id 1tOB0M-00GkbH-0j; Thu, 19 Dec 2024 08:31:30 +0100 From: Ahmad Fatoum Subject: [PATCH 00/11] reboot: support runtime configuration of emergency hw_protection action Date: Thu, 19 Dec 2024 08:31:21 +0100 Message-Id: <20241219-hw_protection-reboot-v1-0-263a0c1df802@pengutronix.de> Precedence: bulk X-Mailing-List: chrome-platform@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-B4-Tracking: v=1; b=H4sIAMnLY2cC/x2MQQ5AMBAAvyJ71kRbSn1FRKjFXlS2DRLxd43jJ DPzQEAmDNBmDzCeFMjvCWSegdvGfUVBc2JQhSqlko3YruFgH9HFZArGyfsorLGVLq2ulRkhpQf jQve/7fr3/QCZth26ZgAAAA== X-Change-ID: 20241218-hw_protection-reboot-96953493726a To: Daniel Lezcano , Fabio Estevam , "Rafael J. Wysocki" , Zhang Rui , Lukasz Luba , Jonathan Corbet , Serge Hallyn , Liam Girdwood , Mark Brown , Matti Vaittinen , Benson Leung , Tzung-Bi Shih , Guenter Roeck , Rob Herring , Krzysztof Kozlowski , Conor Dooley Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, linux-doc@vger.kernel.org, linux-security-module@vger.kernel.org, chrome-platform@lists.linux.dev, devicetree@vger.kernel.org, kernel@pengutronix.de, Ahmad Fatoum , Matteo Croce X-Mailer: b4 0.14.2 X-SA-Exim-Connect-IP: 2a0a:edc0:0:c01:1d::a2 X-SA-Exim-Mail-From: a.fatoum@pengutronix.de X-SA-Exim-Scanned: No (on metis.whiteo.stw.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: chrome-platform@lists.linux.dev We currently leave the decision of whether to shutdown or reboot to protect hardware in an emergency situation to the individual drivers. This works out in some cases, where the driver detecting the critical failure has inside knowledge: It binds to the system management controller for example or is guided by hardware description that defines what to do. This is inadequate in the general case though as a driver reporting e.g. an imminent power failure can't know whether a shutdown or a reboot would be more appropriate for a given hardware platform. To address this, this series adds a hw_protection kernel parameter and sysfs toggle that can be used to change the action from the shutdown default to reboot. A new hw_protection_trigger API then makes use of this default action. My particular use case is unattended embedded systems that don't have support for shutdown and that power on automatically when power is supplied: - A brief power cycle gets detected by the driver - The kernel powers down the system and SoC goes into shutdown mode - Power is restored - The system remains oblivious to the restored power - System needs to be manually power cycled for a duration long enough to drain the capacitors With this series, such systems can configure the kernel with hw_protection=reboot to have the boot firmware worry about critical conditions. --- Ahmad Fatoum (11): reboot: replace __hw_protection_shutdown bool action parameter with an enum reboot: reboot, not shutdown, on hw_protection_reboot timeout docs: thermal: sync hardware protection doc with code reboot: rename now misleading hw_protection symbols reboot: indicate whether it is a HARDWARE PROTECTION reboot or shutdown reboot: add support for configuring emergency hardware protection action regulator: allow user configuration of hardware protection action platform/chrome: cros_ec_lpc: prepare for hw_protection_shutdown removal dt-bindings: thermal: give OS some leeway in absence of critical-action thermal: core: allow user configuration of hardware protection action reboot: retire hw_protection_reboot and hw_protection_shutdown helpers Documentation/ABI/testing/sysfs-kernel-reboot | 8 ++ Documentation/admin-guide/kernel-parameters.txt | 6 + .../devicetree/bindings/thermal/thermal-zones.yaml | 5 +- Documentation/driver-api/thermal/sysfs-api.rst | 25 +++-- drivers/platform/chrome/cros_ec_lpc.c | 2 +- drivers/regulator/core.c | 4 +- drivers/regulator/irq_helpers.c | 16 +-- drivers/thermal/thermal_core.c | 17 +-- drivers/thermal/thermal_core.h | 1 + drivers/thermal/thermal_of.c | 7 +- include/linux/reboot.h | 25 +++-- include/uapi/linux/capability.h | 1 + kernel/reboot.c | 122 ++++++++++++++++----- 13 files changed, 173 insertions(+), 66 deletions(-) --- base-commit: 78d4f34e2115b517bcbfe7ec0d018bbbb6f9b0b8 change-id: 20241218-hw_protection-reboot-96953493726a Best regards,