All of lore.kernel.org
 help / color / mirror / Atom feed
From: ranshalit@gmail.com (Ran Shalit)
To: kernelnewbies@lists.kernelnewbies.org
Subject: wakeup source - power management
Date: Mon, 8 Sep 2014 06:37:51 +0300	[thread overview]
Message-ID: <CAJ2oMh+Lg5cbsws+vgHQ6dqF7=yEdtSVjPpR9PV9sW_qBUeZmg@mail.gmail.com> (raw)
In-Reply-To: <CAGAs2AmE2cNm_wQMEq0BJrFJYbyekzKQVmUd3VZmXCr=nx1wnw@mail.gmail.com>

On Sun, Sep 7, 2014 at 11:36 PM, AYAN KUMAR HALDER <ayankumarh@gmail.com> wrote:
> On Mon, Sep 8, 2014 at 1:50 AM, Ran Shalit <ranshalit@gmail.com> wrote:
>>
>>
>> On Sun, Sep 7, 2014 at 11:14 PM, AYAN KUMAR HALDER <ayankumarh@gmail.com>
>> wrote:
>>> On Sat, Sep 6, 2014 at 9:56 PM, Ran Shalit <ranshalit@gmail.com> wrote:
>>>> Hello
>>>>
>>>> What does it mean device without wakeup source in terms of runtime PM ?
>>>>
>>> Can you give some source/reference where you came across this terminology.
>>> "device without wakeup source"

> If I am not mistaken, it takes about device without wakeup source in
> Suspend to Ram
> which is system power management and not runtime power management.
> In this respect it means, the device cannot wake-up the system from
> suspend state.
> Such devices are completely powered down/clock disabled in suspend state.
> Devices which have wakeup source like RTC are not powered down completely
> so as to generate a wakeup interrupt. This would try to wakeup the system.
>
> Sorry, I am not aware about "device without wakeup source" in terms of
> runtime pm.
>

Hi,

How should a wakeup source for a device be configured in code.
I could not find it documented anywhere.

Thanks very much,
Ran

  reply	other threads:[~2014-09-08  3:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-06 16:26 wakeup source - power management Ran Shalit
2014-09-07 20:14 ` AYAN KUMAR HALDER
2014-09-07 20:20   ` Ran Shalit
2014-09-07 20:36     ` AYAN KUMAR HALDER
2014-09-08  3:37       ` Ran Shalit [this message]
2014-09-08 18:43         ` AYAN KUMAR HALDER
2014-09-09 11:37           ` Ran Shalit
2014-09-09 17:48             ` AYAN KUMAR HALDER
2014-09-09 18:43               ` Ran Shalit

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='CAJ2oMh+Lg5cbsws+vgHQ6dqF7=yEdtSVjPpR9PV9sW_qBUeZmg@mail.gmail.com' \
    --to=ranshalit@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.