From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rob Herring" <robh@kernel.org>,
"Grant Likely" <grant.likely@linaro.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Thierry Reding" <treding@nvidia.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"open list" <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH] driver-core: platform: automatically mark wakeup devices
Date: Mon, 18 Jan 2016 16:41:32 +0100 [thread overview]
Message-ID: <1984537.Ed4NObzuHH@vostro.rjw.lan> (raw)
In-Reply-To: <CAPKp9ubgy0sxNb9FfO3Jtk94PRyVu-jPOHFnggzh4n50+t453w@mail.gmail.com>
On Monday, January 18, 2016 03:23:18 PM Sudeep Holla wrote:
> On Mon, Jan 18, 2016 at 2:47 PM, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> > On Sunday, January 17, 2016 06:11:38 PM Dmitry Torokhov wrote:
> >> When probing platform drivers let's check if corresponding devices have
> >> "wakeup-source" property defined (either in device tree, ACPI, or static
> >> platform properties) and automatically enable such devices as wakeup
> >> sources for the system. This will help us standardize on the name for this
> >> property and reduce amount of boilerplate code in the drivers.
> >
> > ACPI has other ways of telling the OS that the device is wakeup-capable,
> > but I guess the property in question can be used too (as long as it is
> > consistent with the other methods).
> >
>
> Just curious to know what you mean when you say this property can also
> be used with ACPI. Do you mean we could use "wakeup-source" DSD ?
Yes.
> If so, won't that go against rule for DSD (i.e we *should not* bypass the
> existing mechanisms defined by the ACPI, e.g. _SxW in this case)
Not necessarily.
What if the device doesn't use ACPI PM and still can wake up the system?
Thanks,
Rafael
next prev parent reply other threads:[~2016-01-18 15:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 2:11 Dmitry Torokhov
2016-01-18 5:11 ` Greg Kroah-Hartman
2016-01-18 6:14 ` Dmitry Torokhov
2016-01-18 15:35 ` Sudeep Holla
2016-01-18 14:47 ` Rafael J. Wysocki
2016-01-18 15:23 ` Sudeep Holla
2016-01-18 15:41 ` Rafael J. Wysocki [this message]
2016-01-18 15:58 ` Sudeep Holla
2016-01-18 17:09 ` Rafael J. Wysocki
2016-01-18 16:22 ` Dmitry Torokhov
2016-01-18 17:19 ` Rafael J. Wysocki
2016-01-18 17:55 ` Dmitry Torokhov
2016-01-18 22:18 ` Rafael J. Wysocki
2016-01-20 0:45 ` Dmitry Torokhov
2016-01-20 2:40 ` Rafael J. Wysocki
2016-01-20 13:51 ` Rafael J. Wysocki
2016-01-20 23:01 ` Rafael J. Wysocki
2016-01-21 0:23 ` Dmitry Torokhov
2016-01-26 16:47 ` Rafael J. Wysocki
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=1984537.Ed4NObzuHH@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=dmitry.torokhov@gmail.com \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=treding@nvidia.com \
--cc=u.kleine-koenig@pengutronix.de \
/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
Powered by JetHome