From: Andrew Lunn <andrew@lunn.ch>
To: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Jamie Lentin <jm@lentin.co.uk>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Igor Opaniuk <igor.opaniuk@toradex.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Sebastian Reichel <sre@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH 0/2] This patch introduces a feature to force gpio-poweroff module
Date: Mon, 30 Sep 2019 14:14:40 +0200 [thread overview]
Message-ID: <20190930121440.GC13301@lunn.ch> (raw)
In-Reply-To: <20190930103531.13764-1-oleksandr.suvorov@toradex.com>
On Mon, Sep 30, 2019 at 10:35:36AM +0000, Oleksandr Suvorov wrote:
> to register its own pm_power_off handler even if someone has registered
> this handler earlier.
> Useful to change a way to power off the system using DT files.
Hi Oleksandr
I'm not sure this is a good idea. What happens when there are two
drivers using forced mode? You then get which ever is register last.
Non deterministic behaviour.
What is the other driver which is causing you problems? How is it
getting probed? DT?
Thanks
Andrew
next prev parent reply other threads:[~2019-09-30 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 10:35 [PATCH 0/2] This patch introduces a feature to force gpio-poweroff module Oleksandr Suvorov
2019-09-30 10:35 ` [PATCH 1/2] power: reset: gpio-poweroff: add force mode Oleksandr Suvorov
2019-09-30 10:35 ` [PATCH 2/2] dt-bindings: power: reset: gpio-poweroff: Add 'force-mode' property Oleksandr Suvorov
2019-09-30 12:14 ` Andrew Lunn [this message]
2019-09-30 14:11 ` [PATCH 0/2] This patch introduces a feature to force gpio-poweroff module Oleksandr Suvorov
2019-09-30 16:32 ` Andrew Lunn
2019-09-30 19:42 ` Jamie Lentin
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=20190930121440.GC13301@lunn.ch \
--to=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=igor.opaniuk@toradex.com \
--cc=jm@lentin.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=mark.rutland@arm.com \
--cc=oleksandr.suvorov@toradex.com \
--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).