From: Marcel Holtmann <marcel@holtmann.org>
To: Oliver Neukum <oliver@neukum.org>
Cc: Pavel Machek <pavel@suse.cz>, Stefan Seyfried <seife@suse.de>,
linux-bluetooth@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [rfc/rft]power management for btusb
Date: Wed, 20 Aug 2008 17:25:14 +0200 [thread overview]
Message-ID: <1219245914.7591.338.camel@violet.holtmann.net> (raw)
In-Reply-To: <200808201600.56584.oliver@neukum.org>
Hi Oliver,
> > > > > > > > > > > > I tried to run this on my Quad G5, but I never see suspend() or resume()
> > > > > > > > > > > > called. Do I have to do something to make autosuspend work?
> > > > > > > > > > >
> > > > > > > > > > > echo "auto" > $(directry in sysfs for device)/power/level
> > > > > > > > > > > And you'll see power events in syslog only if you compile with
> > > > > > > > > > > CONFIG_USB_DEBUG
> > > > > > > > > >
> > > > > > > > > > I only seem to see power/wakeup entries. I don't have power/level. Am I
> > > > > > > > > > missing some configuration option?
> > > > > > > > >
> > > > > > > > > Probably CONFIG_USB_SUSPEND
> > > > > > > >
> > > > > > > > that one is on of course. Do you think it makes a difference that it is
> > > > > > > > PowerPC system I am testing this with?
> > > > > > >
> > > > > > > If it does make a difference, that's a bug. Runtime PM should work
> > > > > > > anyway.
> > > > > >
> > > > > > I really don't see any calls to suspend() and I am missing the
> > > > > > power/level option. This is the latest 2.6.27-rc3-git tree from Linus.
> > > > >
> > > > > Odd. Send /proc/config.gz please.
> > > >
> > > > there you go. It is a nice Quad G5 machine.
> > >
> > > That should work. Did you perhaps forget to remake your initrd?
> >
> > no initrd on this system.
>
> It should work. Are you perhaps looking at the interface level as opposed
> to the device level?
finally I found the device and setting it to auto makes it actually
suspend. Why is this not default? The driver has to enable it anyway.
Regards
Marcel
next prev parent reply other threads:[~2008-08-20 15:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 9:42 [rfc/rft]power management for btusb Oliver Neukum
2008-08-20 10:18 ` Marcel Holtmann
2008-08-20 12:05 ` Oliver Neukum
2008-08-20 12:34 ` Marcel Holtmann
2008-08-20 12:42 ` Oliver Neukum
2008-08-20 13:00 ` Marcel Holtmann
2008-08-20 13:03 ` Felipe Balbi
2008-08-20 13:05 ` Oliver Neukum
2008-08-20 13:05 ` Marcel Holtmann
2008-08-20 13:11 ` Oliver Neukum
2008-08-20 13:13 ` Marcel Holtmann
2008-08-20 13:23 ` Oliver Neukum
2008-08-20 13:24 ` Marcel Holtmann
2008-08-20 13:34 ` Oliver Neukum
2008-08-20 13:39 ` Marcel Holtmann
2008-08-20 14:00 ` Oliver Neukum
2008-08-20 15:25 ` Marcel Holtmann [this message]
2008-08-20 15:33 ` Oliver Neukum
2008-08-20 15:35 ` Alan Stern
2008-08-20 15:41 ` Marcel Holtmann
2008-08-20 15:55 ` Alan Stern
2008-08-20 16:04 ` Oliver Neukum
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=1219245914.7591.338.camel@violet.holtmann.net \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=pavel@suse.cz \
--cc=seife@suse.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