linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mohammed Shafi <mshajakhan@atheros.com>
To: Felix Fietkau <nbd@openwrt.org>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Paul Shaw <Paul.Shaw@Atheros.com>,
	Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Subject: Re: [PATCH] ath9k: Add support for Adaptive Power Management
Date: Wed, 24 Nov 2010 10:36:51 +0530	[thread overview]
Message-ID: <4CEC9D6B.1000506@atheros.com> (raw)
In-Reply-To: <4CEBE389.1020209@openwrt.org>

On Tuesday 23 November 2010 09:23 PM, Felix Fietkau wrote:
> On 2010-11-23 4:12 PM, Mohammed Shafi Shajakhan wrote:
>    
>> From: Mohammed Shafi Shajakhan<mshajakhan@atheros.com>
>>
>> This feature is to mitigate the problem of certain 3
>> stream chips that exceed the PCIe power requirements.An EEPROM flag
>> controls which chips have APM enabled which is basically read from
>> miscellaneous configuration element of the EEPROM header.
>>
>> This workaround will reduce power consumption by using 2 Tx chains for
>> Single and Double stream rates (5 GHz only).All self generated frames
>> (regardless of rate) are sent on 2 chains when this feature is
>> enabled(Chip Limitation).
>>
>> Cc: Paul Shaw<paul.shaw@atheros.com>
>> Signed-off-by: Mohammed Shafi Shajakhan<mshajakhan@atheros.com>
>> Tested-by: Mohammed Shafi Shajakhan<mshajakhan@atheros.com>I
>>      
> I think this code would get a lot more concise if you'd move it to
> ar9003_mac.c, since this issue is AR9003 specific anyway.
> It would also allow you to avoid adding yet another redundant ath_softc
> capability flag, as the driver part really doesn't need to be concerned
> with this.
>    
Thanks for reviewing the code and for your valuable comments.
1.I get a feeling when we add this to ar9003_mac.c this feature won't be 
much explicit  and might be hard to debug if any issue comes.You might 
have noticed we might be using APM only for non-PAPRD frames.
2.This feature may be applicable for future 3 stream chips (or) in case 
of Power Management we can even disable the third chain (1S and 2S 
rates) while trading of throughput slightly for all 3 stream chips.
3.Yes ath_softc flag might be reduntant I will look into it.
4.There were so many things directly available in xmit.c such as rate 
descriptor,band(5Ghz or 2 Ghz) we are using,whether its a PAPRD frame, 
to looking for single stream and double stream etc.I really dont know 
whether all these things will be available directly available in 
ar9003_mac.c but it would be very difficult to track them and do all the 
right things.
         I will surely look to concise the code in near future , but now 
I think we can have it in upstream.I had tested it and there were no 
issues in fucntionality.
thanks,
shafi

> - Felix
> .
>
>    

  reply	other threads:[~2010-11-24  5:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 15:12 [PATCH] ath9k: Add support for Adaptive Power Management Mohammed Shafi Shajakhan
2010-11-23 15:53 ` Felix Fietkau
2010-11-24  5:06   ` Mohammed Shafi [this message]
2010-11-24 17:41     ` Felix Fietkau
2010-11-25  4:24       ` Mohammed Shafi
2010-11-25  5:33         ` Paul Shaw

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CEC9D6B.1000506@atheros.com \
    --to=mshajakhan@atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=Paul.Shaw@Atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=nbd@openwrt.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).