public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Machowinski <scotch-cGBD8117FJM@public.gmane.org>
To: Bob Lees <bob-l+PWtdWbHAsG2Il/BtU0GPXRex20P6io@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: C2, C3 and bus master activity
Date: Wed, 20 Jul 2005 21:56:43 +0200	[thread overview]
Message-ID: <42DEAC7B.7090103@tzi.de> (raw)
In-Reply-To: <200507202031.38488.bob-l+PWtdWbHAsG2Il/BtU0GPXRex20P6io@public.gmane.org>



Bob Lees wrote:
> I agree with Johan, I think it was the uhci-hcd driver which caused the 
> problem.  I must admit that I don't have wireless running when I shut 
> everything off so that may also be a problem.
> 
> Unfortunately its the uhci-hcd driver which allows me to use a usb mouse so I 
> would like to know how the usb driver could be used and still have C3/4 (C4 
> on the IBM)
Actually ff you use an USB device, you can never use the C3 or C4 mode 
of your CPU. USB devices just cause busmaster activity, and as long as 
the kernel detecs busmaster activity, it stops taking the CPU in 
anything behind C2.

If you want to know more please read ACPIspec3.0
8.1.4 Processor Power State C3
on page 253 (the number in the document / the pdfreader says it's page 273)

    Janosch
> 
> Bob
> 
> On Wednesday 20 July 2005 20:05, Johan Vromans wrote:
> 
>>


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

  parent reply	other threads:[~2005-07-20 19:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 18:50 C2, C3 and bus master activity pumpkin
     [not found] ` <200507192050.28343.pumpkin-Mmb7MZpHnFY@public.gmane.org>
2005-07-19 20:18   ` Bob Lees
     [not found]     ` <200507192118.37528.bob-l+PWtdWbHAsG2Il/BtU0GPXRex20P6io@public.gmane.org>
2005-07-19 21:59       ` pumpkin
     [not found]         ` <200507192359.56553.pumpkin-Mmb7MZpHnFY@public.gmane.org>
2005-07-19 23:00           ` Janosch Machowinski
     [not found]             ` <42DD85F3.9050300-cGBD8117FJM@public.gmane.org>
2005-07-20 17:21               ` pumpkin
     [not found]                 ` <200507201921.43576.pumpkin-Mmb7MZpHnFY@public.gmane.org>
2005-07-20 19:29                   ` pumpkin
     [not found]                     ` <42DEB3E8.6080601@tzi.de>
     [not found]                       ` <42DEB3E8.6080601-cGBD8117FJM@public.gmane.org>
2005-07-21 17:31                         ` pumpkin
2005-07-21 16:08                 ` Volker Braun
2005-07-20 19:05       ` Johan Vromans
     [not found]         ` <m23bq98fir.fsf-KjnUIgV0B0bak1Ioo/c9IoRWq/SkRNHw@public.gmane.org>
2005-07-20 19:31           ` Bob Lees
     [not found]             ` <200507202031.38488.bob-l+PWtdWbHAsG2Il/BtU0GPXRex20P6io@public.gmane.org>
2005-07-20 19:56               ` Janosch Machowinski [this message]
2005-07-21  5:24       ` 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=42DEAC7B.7090103@tzi.de \
    --to=scotch-cgbd8117fjm@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=bob-l+PWtdWbHAsG2Il/BtU0GPXRex20P6io@public.gmane.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