Linux Power Management development
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Li Yang-R58472 <r58472@freescale.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: System suspend states and device driver suspend() callback
Date: Sat, 17 Aug 2013 01:53:36 +0200	[thread overview]
Message-ID: <35306580.ZCUI1aZasW@vostro.rjw.lan> (raw)
In-Reply-To: <02318724-F4F7-4D53-9926-872E9417F672@freescale.com>

On Friday, August 16, 2013 05:13:42 PM Li Yang-R58472 wrote:
> 
> 在 2013-8-16,下午7:22,"Rafael J. Wysocki" <rjw@sisk.pl> 写道:
> 
> > On Friday, August 16, 2013 04:06:26 PM Li Yang wrote:
> >> Hi Guys,
> >> 
> >> Is there a standard way for the device drivers to know if the system
> >> is going to “standby” mode or “mem” mode when the suspend() callbacks
> >> are called?
> > 
> > No, there's none.
> > 
> > What do you need that for?
> 
> Some chips like ours are putting the on-chip devices into different low
> power states when entering different system low power states.  When we enter
> system standby, on-chip devices are clock gated.  While entering suspend to
> ram, on-chip devices are power gated.  We want to driver to act differently
> too when entering different suspend states.

Can you possibly use platform suspend operations to implement that (in analogy
with ACPI suspend operations)?

Rafael

  reply	other threads:[~2013-08-16 23:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16  8:06 System suspend states and device driver suspend() callback Li Yang
2013-08-16 10:57 ` Arend van Spriel
2013-08-16 11:32 ` Rafael J. Wysocki
2013-08-16 17:13   ` Li Yang-R58472
2013-08-16 23:53     ` Rafael J. Wysocki [this message]
2013-08-26  8:50       ` Li Yang

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=35306580.ZCUI1aZasW@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=r58472@freescale.com \
    /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