From: "John W. Linville" <linville@tuxdriver.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Fabien ADAM <id2ndr@crocobox.org>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com,
Paul Menzel <paulepanter@users.sourceforge.net>,
Gertjan van Wingerde <gwingerde@gmail.com>
Subject: Re: [PATCH 3.11 v2] rt2800: fix wrong TX power compensation
Date: Wed, 28 Aug 2013 11:10:05 -0400 [thread overview]
Message-ID: <20130828151005.GB1966@tuxdriver.com> (raw)
In-Reply-To: <20130827081340.GB2609@redhat.com>
I had already merged the first one, FWIW -- sorry...
On Tue, Aug 27, 2013 at 10:13:40AM +0200, Stanislaw Gruszka wrote:
> We should not do temperature compensation on devices without
> EXTERNAL_TX_ALC bit set (called DynamicTxAgcControl on vendor driver).
> Such devices can have totally bogus TSSI parameters on the EEPROM,
> but are still treated by us as valid and results in wrong TX power
> calculations.
>
> This fixes inability to connect to AP on slightly longer distance on
> some Ralink chips/devices without EXTERNAL_TX_ALC configured.
>
> Reference:
> http://thread.gmane.org/gmane.linux.drivers.rt2x00.user/2263
>
> Reported-and-tested-by: Fabien ADAM <id2ndr@crocobox.org>
> Cc: stable@vger.kernel.org
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> Acked-by: Gertjan van Wingerde <gwingerde@gmail.com>
> Acked-by: Paul Menzel <paulepanter@users.sourceforge.net>
> ---
> drivers/net/wireless/rt2x00/rt2800lib.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> v1 -> v2: fix changelog
>
> John,
>
> If possible this should go to 3.11, -next & cc -stable is also fine as
> usual.
>
> Note that in -next version of the patch rt2x00_eeprom_read() should
> be changed to rt2800_eeprom_read() do to commit
> 3e38d3daf881a78ac13e93504a8ac5777040797e
>
> diff --git a/drivers/net/wireless/rt2x00/rt2800lib.c b/drivers/net/wireless/rt2x00/rt2800lib.c
> index 1f80ea5..a0119d3 100644
> --- a/drivers/net/wireless/rt2x00/rt2800lib.c
> +++ b/drivers/net/wireless/rt2x00/rt2800lib.c
> @@ -2790,6 +2790,13 @@ static int rt2800_get_gain_calibration_delta(struct rt2x00_dev *rt2x00dev)
> int i;
>
> /*
> + * First check if temperature compensation is supported.
> + */
> + rt2x00_eeprom_read(rt2x00dev, EEPROM_NIC_CONF1, &eeprom);
> + if (!rt2x00_get_field16(eeprom, EEPROM_NIC_CONF1_EXTERNAL_TX_ALC))
> + return 0;
> +
> + /*
> * Read TSSI boundaries for temperature compensation from
> * the EEPROM.
> *
> --
> 1.7.11.7
>
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2013-08-28 15:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 13:18 [PATCH 3.11] rt2800: fix wrong TX power compensation Stanislaw Gruszka
2013-08-26 19:04 ` [rt2x00-users] " Gertjan van Wingerde
2013-08-26 20:19 ` Paul Menzel
2013-08-27 8:00 ` Stanislaw Gruszka
2013-08-27 8:13 ` [PATCH 3.11 v2] " Stanislaw Gruszka
2013-08-27 8:26 ` [rt2x00-users] " Paul Menzel
2013-08-27 9:13 ` Stanislaw Gruszka
2013-08-28 15:10 ` John W. Linville [this message]
2013-08-27 8:22 ` [rt2x00-users] [PATCH 3.11] " Daniel Golle
2013-08-27 8:22 ` Paul Menzel
2013-08-27 9:07 ` Stanislaw Gruszka
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=20130828151005.GB1966@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=gwingerde@gmail.com \
--cc=id2ndr@crocobox.org \
--cc=linux-wireless@vger.kernel.org \
--cc=paulepanter@users.sourceforge.net \
--cc=sgruszka@redhat.com \
--cc=users@rt2x00.serialmonkey.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).