From: Thomas Huehn <thomas@net.t-labs.tu-berlin.de>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: jirislaby@gmail.com, ath5k-devel@lists.ath5k.org,
linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [ath5k-devel] [PATCH 3/4] ath5k: Preserve tx power level requested from above on phy_init
Date: Sun, 29 Jul 2012 13:11:45 +0200 [thread overview]
Message-ID: <50151A71.9010306@net.t-labs.tu-berlin.de> (raw)
In-Reply-To: <CAFtRNNzPnh_C2JqC4WjKrChn=QPcC4UG-8PigyGp4WLXuCb5GQ@mail.gmail.com>
Hi Nick,
> Anyway if readability is the issue we can just do something like
>
> int txpower_halfdb = 0;
>
> [...]
>
> if(ah->power_level) {
> txpower_halfdb = ah->power_level * 2;
> } else {
> txpower_halfdb = AR5K_TUNE_MAX_TXPOWER;
> }
>
> and then it'll look like this
>
> ret = ath5k_hw_txpower(ah, channel, txpower_halfdb);
I like this way you proposed here. But it is quite personal and compact
wise the other version is in lead.
> >
> (wouldn't it be weird if someone from above asked us
> what tx power was requested and we reply with max tx power ?).
you mean in case someone from above did never requested something but
ask us what was requested and we tell him that nothing was requested
thats why we use max tx_power ... makes more sense ? :)
I think once the reporting from the driver to mac80211 about the current
tx_power is there, it will be solved anyway.
Greetings Thomas
next prev parent reply other threads:[~2012-07-29 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 14:32 [PATCH 1/4] ath5k: Use correct value for min_pwr and cur_pwr Nick Kossifidis
2012-07-28 14:32 ` [PATCH 2/4] ath5k: Fix range scaling when setting rate power table Nick Kossifidis
2012-07-28 14:32 ` [PATCH 3/4] ath5k: Preserve tx power level requested from above on phy_init Nick Kossifidis
2012-07-28 15:26 ` Thomas Huehn
2012-07-28 15:33 ` Thomas Huehn
2012-07-28 20:47 ` Nick Kossifidis
2012-07-29 11:11 ` Thomas Huehn [this message]
2012-07-29 20:51 ` [ath5k-devel] " Nick Kossifidis
2012-07-30 11:45 ` Thomas Huehn
2012-07-28 14:32 ` [PATCH 4/4] ath5k: Put power_level where it belongs and rename it Nick Kossifidis
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=50151A71.9010306@net.t-labs.tu-berlin.de \
--to=thomas@net.t-labs.tu-berlin.de \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mickflemm@gmail.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).