From: David Brownell <david-b@pacbell.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <gregkh@suse.de>,
linux-pm@lists.osdl.org, Brice Goglin <brice@myri.com>
Subject: Re: /sys/devices/.../power/state broken?
Date: Tue, 12 Dec 2006 10:15:39 -0800 [thread overview]
Message-ID: <200612121015.41365.david-b@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0612121038210.2834-100000@iolanthe.rowland.org>
On Tuesday 12 December 2006 7:42 am, Alan Stern wrote:
> On Tue, 12 Dec 2006, Brice Goglin wrote:
>
> > Hi,
> >
> > I know that .../power/state files are deprecated, but I like using them
> > for basic testing of a driver's suspend/resume routines. Anyway, echoing
> > something in the .../power/state in current -git does not seem to work
> > anymore.
>
> It does work, but the results depend on the device you want to suspend.
> For instance, USB devices have no problem at all. PCI devices will ignore
> your writes because .../power/state can't handle the new multi-stage
> suspend and resume mechanism.
>
> I've been using the patch below to force my tests to work.
... relying on the fact that few drivers currently use the late_suspend()
or early_resume() methods. I know one such driver is in a 2.6.20 merge
queue, but drivers using those methods are still a bit uncommon.
Speaking of those new PM methods ... Greg, I tried refreshing my
patch that uses class suspend() and resume() methods with RTCs to
adjust the system clock properly on resume. But neither method
is getting called any more. Did that break with the class device
changes?
- Dave
next prev parent reply other threads:[~2006-12-12 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 10:17 /sys/devices/.../power/state broken? Brice Goglin
2006-12-12 15:42 ` Alan Stern
2006-12-12 18:15 ` David Brownell [this message]
2006-12-15 19:01 ` Greg KH
2006-12-18 3:27 ` class suspend()/resume() broken David Brownell
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=200612121015.41365.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=brice@myri.com \
--cc=gregkh@suse.de \
--cc=linux-pm@lists.osdl.org \
--cc=stern@rowland.harvard.edu \
/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