Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755641Ab0GZWbu (ORCPT ); Mon, 26 Jul 2010 18:31:50 -0400 Received: from mail-pw0-f46.google.com ([209.85.160.46]:60758 "EHLO mail-pw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752953Ab0GZWbs (ORCPT ); Mon, 26 Jul 2010 18:31:48 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=qK6576hF1HMcDFq6ERkyMMOTxbkuoSKo2HVbfxCd/0x3BJ8J617PmIzuoB65OvCQgL iGh3fbwQvqZBJh0TMXxAcQ6yVny6TPzVDWw7VfWQKjUAMKxQmPrEI9ctAUT0qGOejuM1 DBX9fOiGxa/NEnOO8/c2tfKEXxmlGcfE4QDKM= MIME-Version: 1.0 In-Reply-To: <20100726222909.GA6773@srcf.ucam.org> References: <1276952554.3332.3.camel@maxim-laptop> <1276961564.5173.12.camel@maxim-laptop> <20100726201322.GI14855@tux> <1280177362.3721.7.camel@maxim-laptop> <20100726210651.GJ14855@tux> <1280179033.3721.15.camel@maxim-laptop> <20100726212543.GA5424@srcf.ucam.org> <20100726222113.GA6487@srcf.ucam.org> <20100726222909.GA6773@srcf.ucam.org> From: "Luis R. Rodriguez" Date: Mon, 26 Jul 2010 15:31:28 -0700 Message-ID: Subject: Re: [ath5k-devel] [PATCH v3] ath5k: disable ASPM To: Matthew Garrett Cc: Maxim Levitsky , "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-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1266 Lines: 26 On Mon, Jul 26, 2010 at 3:29 PM, Matthew Garrett wrote: > On Mon, Jul 26, 2010 at 03:26:37PM -0700, Luis R. Rodriguez wrote: > >> What I meant was that the PCI config space would already have L1 >> enabled if L1 worked, so I don't see why we would need to nitpick out >> specifics here. All Atheros PCIE chips should work with L1. The advise >> given is to disable L0s though. I believe AR2425 would be one which >> likely had L0s enabled but requires it to be disabled. Not sure of >> others. But this is why I am saying this can be done globally for all >> ath5k chipsets. > > If L1 is set but the chip is pre-PCIe 1.1 then we'll disable L1 unless > the driver tells us that it's functional. The .inf from the Windows > driver seemed to suggest that only a subset of the chips re-enabled L1 > there, but if it's ok in general then that's a straightforward one-line > patch. But why can't we just rely on what the device already has on its PCI config space and only ensure to disable L0s? Luis -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/