[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230928123204.20345-1-francesco@dolcini.it>
Date: Thu, 28 Sep 2023 14:32:00 +0200
From: Francesco Dolcini <francesco@...cini.it>
To: Sebastian Reichel <sre@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: Francesco Dolcini <francesco.dolcini@...adex.com>,
linux-pm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH v1 0/4] power: reset: gpio-poweroff: use sys-off handler API
From: Francesco Dolcini <francesco.dolcini@...adex.com>
Use the new sys-off handler API for gpio-poweroff. This allows us to have more
than one power-off handler and to have a priority for the handler. Also, add a
priority property so we can use gpio-poweroff even when registering another
poweroff handler or using the legacy pm_power_off method.
Stefan Eichenberger (4):
power: reset: gpio-poweroff: use a struct to store the module
variables
power: reset: gpio-poweroff: use sys-off handler API
dt-bindings: power: reset: gpio-poweroff: Add priority property
power: reset: gpio-poweroff: make sys handler priority configurable
.../bindings/power/reset/gpio-poweroff.yaml | 4 +
drivers/power/reset/gpio-poweroff.c | 82 ++++++++++---------
2 files changed, 48 insertions(+), 38 deletions(-)
--
2.25.1
Powered by blists - more mailing lists