[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikHLBBWrhCP_1f5Jv7zE9RKPvdsl5nSyfkeMfLl@mail.gmail.com>
Date: Tue, 22 Jun 2010 10:17:11 -0700
From: "Luis R. Rodriguez" <mcgrof@...il.com>
To: Matthew Garrett <mjg59@...f.ucam.org>
Cc: Jussi Kivilinna <jussi.kivilinna@...et.fi>,
Maxim Levitsky <maximlevitsky@...il.com>,
David Quan <David.Quan@...eros.com>,
Bob Copeland <me@...copeland.com>,
"Luis R. Rodriguez" <mcgrof@...badil.infradead.org>,
ath5k-devel@...ema.h4ckr.net, linux-wireless@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [ath5k-devel] [PATCH v2] ath5k: disable ASPM
On Tue, Jun 22, 2010 at 9:52 AM, Matthew Garrett <mjg59@...f.ucam.org> wrote:
> On Tue, Jun 22, 2010 at 09:48:40AM -0700, Luis R. Rodriguez wrote:
>
>> Sure, I agree with that, but it also will enable ASPM for *all*
>> devices which have the capability which IMHO is a terrible idea for
>> users when all they want to do is enable ASPM for one device. Instead
>> I recommend users to enable ASPM for their devices selectively and
>> from userspace.
>
> Why would you only want to enable ASPM for one device?
ASPM doesn't always work for all devices even if they do advertise
ASPM capability so turning it on selectively by device is what I
recommend since otherwise you may get hangs and you will then have to
do the selective enabling. Furthermore laptops tend to disable ASPM
for cards not built-in to it, an example is Cardbus slots or internal
PCI-E slots. This is often done because to enable ASPM for some cards
you often need to tune the host controller in addition to enabling
ASPM for the endpoint, so this will vary depending on vendor, chipset,
and host controller combination. This is documentation that the OEM /
ODM typically end up getting, but not end users.
So given the complexity its best to be selective about it on each
platform until you verify ASPM works well for all devices present.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists