| Message ID | 20231006130428.11259-1-francesco@dolcini.it |
|---|---|
| Headers | show |
| Series | power: reset: gpio-poweroff: use sys-off handler API | expand |
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,
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(-)