From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.atheros.com ([12.19.149.2]:53921 "EHLO mail.atheros.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756512Ab1BJRl2 convert rfc822-to-8bit (ORCPT ); Thu, 10 Feb 2011 12:41:28 -0500 Received: from mail.atheros.com ([10.10.20.105]) by sidewinder.atheros.com for ; Thu, 10 Feb 2011 09:41:08 -0800 Date: Thu, 10 Feb 2011 09:41:27 -0800 From: "Luis R. Rodriguez" To: Mohammed Shajakhan CC: Richard =?iso-8859-1?Q?Sch=FCtz?= , "linville@tuxdriver.com" , "linux-wireless@vger.kernel.org" , Luis Rodriguez Subject: Re: [RFC] ath9k: Fix ath9k prevents CPU to enter C3 states Message-ID: <20110210174127.GA16737@tux> References: <1297262007-15128-1-git-send-email-mshajakhan@atheros.com> <4D52C54A.2010709@t-online.de> <4D53F3DE.4030707@atheros.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" In-Reply-To: <4D53F3DE.4030707@atheros.com> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Feb 10, 2011 at 06:19:10AM -0800, Mohammed Shajakhan wrote: > On Wednesday 09 February 2011 10:18 PM, Richard Schütz wrote: > >> From: Mohammed Shafi Shajakhan > >> > >> The DMA latency issue is observed only in Intel pinetrail platforms but > >> in the driver we had a default PM-QOS value of 55. This caused > >> unnecessary power consumption and battery drain in other platforms. > >> Address this issue by disabling PM-QOS by default by setting it's value > >> as '0' and making code changes appropriately.This addresses the bug: > >> https://bugzilla.kernel.org/show_bug.cgi?id=27532 > >> If the user sees some DMA latency issue he can still use the pmqos as a > >> module parameter to trade power for throughput as below: > >> sudo modprobe ath9k pmqos=55 > >> > >> Signed-off-by: Mohammed Shafi Shajakhan > >> > > Acked-By: Richard Schütz > > > Thanks, but we got to consider user space approach which Luis had mentioned. Richard, can you test the userspace app as a replacement? Or did your board not exerpience the issue? Luis