Re: [linux-usb-devel] BM_STS and usb

2001-03-07 Thread David Brownell
e - Original Message - From: "Brad Parker" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 07, 2001 3:38 AM Subject: Re: [linux-usb-devel] BM_STS and usb > > David Brownell wrote: > >> > ACPI defines processor power-saving states C0,

Re: [linux-usb-devel] BM_STS and usb

2001-03-07 Thread Brad Parker
David Brownell wrote: >> > ACPI defines processor power-saving states C0, C1, C2 and C3. We cannot >> > enter C3 if there is busmastering activity, and so we check BM_STS. If thi >s >> > is high when it should not be, and we are therefore not using C3, we are >> > losing battery life. >> >> USB

Re: [linux-usb-devel] BM_STS and usb

2001-03-06 Thread David Brownell
> > ACPI defines processor power-saving states C0, C1, C2 and C3. We cannot > > enter C3 if there is busmastering activity, and so we check BM_STS. If this > > is high when it should not be, and we are therefore not using C3, we are > > losing battery life. > > USB causes continuous bus mastering

Re: [linux-usb-devel] BM_STS and usb

2001-03-06 Thread Alan Cox
> ACPI defines processor power-saving states C0, C1, C2 and C3. We cannot > enter C3 if there is busmastering activity, and so we check BM_STS. If this > is high when it should not be, and we are therefore not using C3, we are > losing battery life. USB causes continuous bus mastering. > 1. The

[linux-usb-devel] BM_STS and usb

2001-03-06 Thread Grover, Andrew
Hi all, Problem: We are seeing the BM_STS bit stuck at 1, when the USB driver is enabled on Linux. Why this is important: ACPI defines processor power-saving states C0, C1, C2 and C3. We cannot enter C3 if there is busmastering activity, and so we check BM_STS. If this is high when it should not