>> issue is more about letting the *bus* power down. How much we save will
>> depend on the specific bus layout on a given machine, and also whether
>> we can successfully autosuspend all of the drivers.
>
> Modern machines are full of (mostly empty) buses, so there is hope the
> gain will not be i
Matthew Garrett wrote:
> The
> issue is more about letting the *bus* power down. How much we save will
> depend on the specific bus layout on a given machine, and also whether
> we can successfully autosuspend all of the drivers.
Modern machines are full of (mostly empty) buses, so there is ho
On Wed, 2009-06-10 at 17:04 +0100, Matthew Garrett wrote:
> On Wed, Jun 10, 2009 at 09:15:30AM -0400, Jesse Keating wrote:
> > On Tue, 2009-06-09 at 19:32 +0100, Matthew Garrett wrote:
> > >
> > > Through F12 I'm going to be slowly enabling autosuspend on various
> > > pieces of USB hardware. The
On Wed, Jun 10, 2009 at 05:16:41PM +0200, Roberto Ragusa wrote:
> Matthew Garrett wrote:
> > The first part of this is an upload of libfprint which enables
> > autosuspend on fingerprint readers.
>
> Fingerprint readers and other "un-unpluggable" USB laptop stuff
> such as flash-readers, bluetoot
On Wed, Jun 10, 2009 at 09:15:30AM -0400, Jesse Keating wrote:
> On Tue, 2009-06-09 at 19:32 +0100, Matthew Garrett wrote:
> >
> > Through F12 I'm going to be slowly enabling autosuspend on various
> > pieces of USB hardware. The aim is to ensure that it's only enabled on
> > hardware that suppo
Matthew Garrett wrote:
> The first part of this is an upload of libfprint which enables
> autosuspend on fingerprint readers.
Fingerprint readers and other "un-unpluggable" USB laptop stuff
such as flash-readers, bluetooth adapters etc. are perfect candidates
for suspending.
Is there somewhere a
On Tue, 2009-06-09 at 19:32 +0100, Matthew Garrett wrote:
>
> Through F12 I'm going to be slowly enabling autosuspend on various
> pieces of USB hardware. The aim is to ensure that it's only enabled on
> hardware that supports it. This is going to be a combination of kernel
> modifications and
On Tue, Jun 9, 2009 at 8:32 PM, Matthew Garrett wrote:
> USB is an irritating protocol that requires USB controllers to remain
> active whenever a device is attached, even if that device is doing
> nothing.
Is this somewhat addressed in the USB3 specs?
--
Gianluca Sforna
http://morefedora.blog
On Tue, Jun 09, 2009 at 01:18:31PM -0800, Jeff Spaleta wrote:
> As you move forward with this across the devicescape, how are you
> going to selectively enable devices to apply autosuspend to? Is this
> done by a whitelisting of specific device ids? Or is this going to be
> done based on a detecte
On Tue, Jun 9, 2009 at 10:32 AM, Matthew Garrett wrote:
> Through F12 I'm going to be slowly enabling autosuspend on various
> pieces of USB hardware. The aim is to ensure that it's only enabled on
> hardware that supports it.
As you move forward with this across the devicescape, how are you
going
USB is an irritating protocol that requires USB controllers to remain
active whenever a device is attached, even if that device is doing
nothing. This consumes unnecessary power and can prevent the system
going into deep idle states under some circumstances. The kernel
supports USB autosuspend,
11 matches
Mail list logo
