linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Mohammed Shafi Shajakhan <mshajakhan@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	Paul.Shaw@atheros.com, lrodriguez@atheros.com
Subject: Re: [PATCH] ath9k: Add support for Adaptive Power Management
Date: Tue, 23 Nov 2010 16:53:45 +0100	[thread overview]
Message-ID: <4CEBE389.1020209@openwrt.org> (raw)
In-Reply-To: <1290525147-6927-1-git-send-email-mshajakhan@atheros.com>

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 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.

- Felix

  reply	other threads:[~2010-11-23 15:53 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 [this message]
2010-11-24  5:06   ` Mohammed Shafi
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=4CEBE389.1020209@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=Paul.Shaw@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=mshajakhan@atheros.com \
    /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).