[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169716259646.1002132.13986378548211553065.b4-ty@collabora.com>
Date: Fri, 13 Oct 2023 04:03:16 +0200
From: Sebastian Reichel <sebastian.reichel@...labora.com>
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>,
Francesco Dolcini <francesco@...cini.it>
Cc: Francesco Dolcini <francesco.dolcini@...adex.com>,
linux-pm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/4] power: reset: gpio-poweroff: use sys-off
handler API
On Fri, 06 Oct 2023 10:04:24 -0300, Francesco Dolcini wrote:
> 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
>
> [...]
Applied, thanks!
[1/4] power: reset: gpio-poweroff: use a struct to store the module variables
commit: 13b4c6964665cadb9b06c085029710c43a0c662e
[2/4] power: reset: gpio-poweroff: use sys-off handler API
commit: b16d9f49735f3d26e23f0ba4a2cf21668fc6b66b
[3/4] dt-bindings: power: reset: gpio-poweroff: Add priority property
commit: 4ee17bd30788496a279ceaabc7ecaaf39f61cfc4
[4/4] power: reset: gpio-poweroff: make sys handler priority configurable
commit: d03d2a8cdefe86f04cfb53934a708620e7dfbfcb
Best regards,
--
Sebastian Reichel <sebastian.reichel@...labora.com>
Powered by blists - more mailing lists