From: Andrey Borzenkov <arvidjaar@mail.ru>
To: David Brownell <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] 2.6.17: dmesg flooded with "ohci_hcd 0000:00:02.0: wakeup"
Date: Mon, 19 Jun 2006 22:39:04 +0400 [thread overview]
Message-ID: <200606192239.06208.arvidjaar@mail.ru> (raw)
In-Reply-To: <200606181116.20815.david-b@pacbell.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 18 June 2006 22:16, David Brownell wrote:
> On Sunday 18 June 2006 10:29 am, Andrey Borzenkov wrote:
> > On Sunday 18 June 2006 20:29, David Brownell wrote:
> > > An alternative (but post-boot) workaround _should_ be
> > >
> > > echo disabled > /sys/bus/pci/devices/0000:00:02.0/power/wakeup
>
> Did that work?
>
No. But
echo -n disabled > /sys/devices/pci0000:00/0000:00:02.0/usb1/power/wakeup
did.
Now I noticed that when I boot 2.6.16 hub has only 'Self Powered' attribite
(0xc0) while in 2.6.17 it adds 'Remote Wakeup':
Bus 001 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
...
bmAttributes 0xe0
Self Powered
Remote Wakeup
It apparently makes OHCI believe controller can correctly do suspend/wakeup.
The suspend does not come from upper layer - it is ohci_hub itself attempting
to put controller in lower power mode:
ohci_hub_status_data (struct usb_hcd *hcd, char *buf)
{
...
int can_suspend =
device_may_wakeup(&hcd->self.root_hub->dev);
...
#ifdef CONFIG_PM
/* save power by suspending idle root hubs;
* INTR_RD wakes us when there's work
*/
if (can_suspend
&& !changed
&& !ohci->ed_rm_list
&& ((OHCI_CTRL_HCFS | OHCI_SCHED_ENABLES)
& ohci->hc_control)
== OHCI_USB_OPER
&& time_after (jiffies, ohci->next_statechange)
&& usb_trylock_device (hcd->self.root_hub) == 0
) {
ohci_vdbg (ohci, "autosuspend\n");
(void) ohci_bus_suspend (hcd);
usb_unlock_device (hcd->self.root_hub);
}
#endif
can_suspend is true while it was apparently false in 2.6.16.
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFElu9JR6LMutpd94wRAv5rAJwO/NZ13duktsD0WsksmFqLtUZufACgkBCS
cOb6y1BG+RjecKtCcua9sNY=
=Rm8d
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-06-19 18:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 15:19 2.6.17: dmesg flooded with "ohci_hcd 0000:00:02.0: wakeup" Andrey Borzenkov
2006-06-18 16:29 ` [linux-usb-devel] " David Brownell
2006-06-18 17:29 ` Andrey Borzenkov
2006-06-18 18:16 ` David Brownell
2006-06-18 19:22 ` Andrey Borzenkov
2006-06-19 18:39 ` Andrey Borzenkov [this message]
2006-06-19 20:12 ` David Brownell
2006-11-11 11:29 ` 2.6.19-rc5 regression: can't disable OHCI wakeup via sysfs Andrey Borzenkov
2006-11-12 16:31 ` [linux-usb-devel] " Alan Stern
2006-11-12 18:00 ` David Brownell
2006-11-12 21:59 ` Alan Stern
2006-11-12 23:21 ` David Brownell
2006-11-13 15:57 ` Alan Stern
2006-11-13 16:39 ` David Brownell
2006-11-13 17:15 ` Alan Stern
2006-11-14 21:18 ` David Brownell
2006-11-14 21:42 ` Alan Stern
2006-11-14 22:56 ` David Brownell
2006-11-13 19:58 ` Alan Stern
2006-11-14 20:48 ` Andrey Borzenkov
2006-11-14 20:54 ` [Bulk] " David Brownell
2006-09-22 18:53 ` [linux-usb-devel] 2.6.17: dmesg flooded with "ohci_hcd 0000:00:02.0: wakeup" Andrey Borzenkov
2006-09-22 20:52 ` Alan Stern
2006-11-11 11:27 ` Andrey Borzenkov
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=200606192239.06208.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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.