Return-path: Received: from mail-iw0-f174.google.com ([209.85.214.174]:55161 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751178Ab0G2AG5 (ORCPT ); Wed, 28 Jul 2010 20:06:57 -0400 MIME-Version: 1.0 In-Reply-To: <1280360895.8891.19.camel@maxim-laptop> References: <20100726210651.GJ14855@tux> <1280179033.3721.15.camel@maxim-laptop> <20100726212543.GA5424@srcf.ucam.org> <20100726222113.GA6487@srcf.ucam.org> <20100726222909.GA6773@srcf.ucam.org> <20100726223326.GA6904@srcf.ucam.org> <20100726225057.GA7268@srcf.ucam.org> <1280223313.3721.83.camel@maxim-laptop> <1280360895.8891.19.camel@maxim-laptop> From: "Luis R. Rodriguez" Date: Wed, 28 Jul 2010 17:06:36 -0700 Message-ID: Subject: Re: [ath5k-devel] [PATCH v3] ath5k: disable ASPM To: Maxim Levitsky Cc: Matthew Garrett , "ath5k-devel@lists.ath5k.org" , "linux-wireless@vger.kernel.org" , David Quan , "Luis R. Rodriguez" , linux-kernel , "kernel-team@lists.ubuntu.com" , Luis Rodriguez , Jussi Kivilinna , "tim.gardner@canonical.com" Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, Jul 28, 2010 at 4:48 PM, Maxim Levitsky wrote: > On Tue, 2010-07-27 at 08:57 -0700, Luis R. Rodriguez wrote: >> On Tue, Jul 27, 2010 at 2:35 AM, Maxim Levitsky wrote: >> > On Mon, 2010-07-26 at 23:50 +0100, Matthew Garrett wrote: >> >> On Mon, Jul 26, 2010 at 03:43:04PM -0700, Luis R. Rodriguez wrote: >> >> >> >> > I see.. thanks Mathew... in that case since L1 works on all devices we >> >> > could just force enable L1 for all PCIE devices. What do you think? >> >> >> >> Works for me. >> >> >> > >> > On the second thought, there is no 'pci_enable_link_state' :-) >> > I afraid that if I add it, I might not do that right for all cases, thus >> > do more harm that good... >> >> I'm sorry, can you elaborate? > > I mean ASPM code doesn't have a function to undo effects of the > blacklist (due to pre 1.1 pcie device). > > Its not that simple to write such function. Ah good catch... pcie_aspm_sanity_check() will actually be used to adjust the device link capability... So even if we do try to insist it wouldn't work. I'm happy if we deal with this separately, its a reasonable compromise to fix issues with existing devices out there. Luis