From: Bill Davidsen <davidsen@tmr.com>
To: "Brown, Len" <len.brown@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Variable ticks
Date: Tue, 26 Jul 2005 11:50:03 -0400 [thread overview]
Message-ID: <42E65BAB.7030806@tmr.com> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B300424AC59@hdsmsx401.amr.corp.intel.com>
Brown, Len wrote:
>
>
>>>>Question one, are there other actions to consider?
>>>
>>>
>>>Yes.
>>>Speaking for ACPI C3 state, note that DMA also
>>>wakes up the CPU -- even if there was no device interrupt.
>>>(aka, "the trouble with USB")
>>
>>Trouble? Why would USB do DMA unless there was a device activity?
>
>
> look here:
> http://www.google.com/search?hl=en&q=usb+selective+suspend
>
> Linux is working on it too, but it is in development.
Somehow I didn't ask that right... The stuff on selective disable is
interesting, but my question is why a USB device, call it a keyboard,
would do DMA unless I press a key, at which point response will be
better if the CPU wakes up out of C3.
I understand that specialty attachments may send what amounts to keep
alives, or gather data (webcam) you don't want, but the typical mouse
and KB would seem to be things which generate DMA at user initiation,
and would not be blocked for low power, only for suspend.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-07-26 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 21:19 Variable ticks Brown, Len
2005-07-25 21:25 ` Lee Revell
2005-07-27 8:13 ` Zwane Mwaikambo
2005-07-27 20:43 ` Lee Revell
2005-07-27 21:06 ` Valdis.Kletnieks
2005-07-27 22:03 ` Zwane Mwaikambo
2005-07-26 15:50 ` Bill Davidsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-26 16:08 Brown, Len
2005-07-25 19:10 Brown, Len
2005-07-25 21:05 ` Bill Davidsen
2005-07-25 18:59 Bill Davidsen
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=42E65BAB.7030806@tmr.com \
--to=davidsen@tmr.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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