From: David Brownell <david-b@pacbell.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH/RFC: usbcore wakeup updates (3/4)
Date: Thu, 7 Oct 2004 08:35:53 -0700 [thread overview]
Message-ID: <200410070835.53261.david-b@pacbell.net> (raw)
In-Reply-To: <20041006105155.GE4723@openzaurus.ucw.cz>
Hi Pavel,
On Wednesday 06 October 2004 3:51 am, Pavel Machek wrote:
> > There were already some hooks in usbcore, but they were only
> > configurable for root hubs ... but not keyboards, mice, Ethernet
> > adapters, or other devices.
>
> That "when asked about D1 enter D3" bit worries me a bit, because
> it is (ugly) workaround to core problems, but I can survive it.
I'm not sure what a better fix would be though ... I think WIndows
doesn't bother entering a low power state at all in such cases.
Which seems particularly pointless for the typical USB controller,
which is probably idle at that point already, and which can't take
all that much longer to resume from D3hot than from D1.
But that part is peripheral to the thrust of this set of patches.
Do you think adding those two bits to per-device PM state
is basically a good way to introduce their wakeup capabilities
to the PM core? Suggestions on the next step?
> Introducing enums where PCI suspend level is stored in u32
> would be welcome...
I'm not averse to enums, especially once sparse does good things
with them, but I still think that sort of change would just be nibbling
around the edges of a larger problem. (Which should be addressed
by different patches making device power states/policies, like G0/D1
or "idle yourself", be types that are fully distinct from system power
states like G1/S3, and for which abuse creates compiler errors.)
- Dave
>
> Pavel
> --
> 64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
>
>
next prev parent reply other threads:[~2004-10-07 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 21:07 PATCH/RFC: usbcore wakeup updates (3/4) David Brownell
2004-10-06 10:51 ` Pavel Machek
2004-10-07 15:35 ` David Brownell [this message]
2004-10-07 21:19 ` Pavel Machek
2004-10-08 0:58 ` David Brownell
2004-10-08 14:19 ` Pavel Machek
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=200410070835.53261.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.