From: Francesco Dolcini <francesco@dolcini.it>
To: Sebastian Reichel <sre@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/4] power: reset: gpio-poweroff: use sys-off handler API
Date: Fri, 6 Oct 2023 10:04:24 -0300 [thread overview]
Message-ID: <20231006130428.11259-1-francesco@dolcini.it> (raw)
From: Francesco Dolcini <francesco.dolcini@toradex.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.
v1->v2:
- Add $ref to restart-handler.yaml in gpio-poweroff.yaml
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 | 6 ++
drivers/power/reset/gpio-poweroff.c | 82 ++++++++++---------
2 files changed, 50 insertions(+), 38 deletions(-)
--
2.25.1
next reply other threads:[~2023-10-06 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 13:04 Francesco Dolcini [this message]
2023-10-06 13:04 ` [PATCH v2 3/4] dt-bindings: power: reset: gpio-poweroff: Add priority property Francesco Dolcini
2023-10-09 8:54 ` Krzysztof Kozlowski
2023-10-13 2:03 ` [PATCH v2 0/4] power: reset: gpio-poweroff: use sys-off handler API Sebastian Reichel
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=20231006130428.11259-1-francesco@dolcini.it \
--to=francesco@dolcini.it \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sre@kernel.org \
/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).