On Mon, Sep 30, 2019 at 02:12:53PM +0000, Oleksandr Suvorov wrote: > Add 'force-mode' property to allow the driver to load even if > someone has registered the pm_power_off hook earlier. > > Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@xxxxxxxxxxx> > > --- > > Changes in v2: None > > .../devicetree/bindings/power/reset/gpio-poweroff.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/devicetree/bindings/power/reset/gpio-poweroff.txt b/Documentation/devicetree/bindings/power/reset/gpio-poweroff.txt > index 3e56c1b34a4c..2056e299a472 100644 > --- a/Documentation/devicetree/bindings/power/reset/gpio-poweroff.txt > +++ b/Documentation/devicetree/bindings/power/reset/gpio-poweroff.txt > @@ -31,6 +31,9 @@ Optional properties: > - inactive-delay-ms: Delay (default 100) to wait after driving gpio inactive > - timeout-ms: Time to wait before asserting a WARN_ON(1). If nothing is > specified, 3000 ms is used. > +- force-mode: Force replacing pm_power_off kernel hook. > + If this optional property is not specified, the driver will fail to > + load if someone has registered the pm_power_off hook earlier. What if the init order changes? This is too tied to a specific OS implementation to go in DT. Rob
