From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Sergei Antonov <saproj@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Gabor Juhos <juhosg@openwrt.org>
Subject: Re: USB rt2x00 driver regression
Date: Fri, 17 Jan 2014 11:06:14 +0100 [thread overview]
Message-ID: <20140117100613.GD1425@redhat.com> (raw)
In-Reply-To: <CABikg9yZrXX=qfqeR+V77u+Ndegx50D1_POAYMeq63qJuEzv=w@mail.gmail.com>
On Tue, Jan 14, 2014 at 07:28:39PM +0100, Sergei Antonov wrote:
> Hello!
> I use a USB Wi-Fi adapter identified as follows.
>
> usb 2-4: new high-speed USB device number 5 using ehci-pci
> usb 2-4: New USB device found, idVendor=148f, idProduct=5370
> usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 2-4: Product: 802.11 n WLAN
> usb 2-4: Manufacturer: Ralink
> usb 2-4: SerialNumber: 1.0
> usb 2-4: reset high-speed USB device number 5 using ehci-pci
> ieee80211 phy3: rt2x00_set_rt: Info - RT chipset 5390, rev 0502 detected
> ieee80211 phy3: rt2x00_set_rf: Info - RF chipset 5370 detected
>
> It worked well with older kernels and does not with newer kernels.
> Specifically it fails to find any AP when scanning.
> The first bad commit is:
>
> commit 76773f301f2210dcc20c466aebda7118062673eb
> Author: Gabor Juhos <juhosg@openwrt.org>
> Date: Sat Aug 17 14:09:30 2013 +0200
>
> rt2x00: rt2800lib: use a MCU command for frequency adjustment on USB devices
>
> According to the Ralink driver, there is an MCU
> command which can be used to send the frequency
> offset value directly to the USB device without
> going through the RFCSR writing sequence.
>
> Based on the DPO_RT5572_LinuxSTA_2.6.0.1_20120629
> driver.
>
> Reference:
> RTMPAdjustFrequencyOffset function in common/rt_rf.c
>
> Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
>
> After I removed this special USB handling (see the patch) the adapter
> works again.
Thanks for bisecting! Could you check if following patch fixes the
issue?
Thanks
Stanislaw
diff --git a/drivers/net/wireless/rt2x00/rt2800lib.c b/drivers/net/wireless/rt2x00/rt2800lib.c
index 776aff3..5c06836 100644
--- a/drivers/net/wireless/rt2x00/rt2800lib.c
+++ b/drivers/net/wireless/rt2x00/rt2800lib.c
@@ -1902,13 +1902,13 @@ static void rt2800_adjust_freq_offset(struct rt2x00_dev *rt2x00dev)
if (rfcsr == prev_rfcsr)
return;
+ prev_freq_offset = rt2x00_get_field8(prev_rfcsr, RFCSR17_CODE);
if (rt2x00_is_usb(rt2x00dev)) {
rt2800_mcu_request(rt2x00dev, MCU_FREQ_OFFSET, 0xff,
- freq_offset, prev_rfcsr);
+ freq_offset, prev_freq_offset);
return;
}
- prev_freq_offset = rt2x00_get_field8(prev_rfcsr, RFCSR17_CODE);
while (prev_freq_offset != freq_offset) {
if (prev_freq_offset < freq_offset)
prev_freq_offset++;
next prev parent reply other threads:[~2014-01-17 10:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 18:28 USB rt2x00 driver regression Sergei Antonov
2014-01-17 10:06 ` Stanislaw Gruszka [this message]
2014-01-19 10:57 ` Sergei Antonov
2014-01-19 12:19 ` Igor Gnatenko
2014-01-19 15:34 ` Sergei Antonov
2014-01-19 18:20 ` Gabor Juhos
2014-01-20 11:20 ` Sergei Antonov
2014-01-20 18:50 ` Stanislaw Gruszka
2014-01-22 11:27 ` Sergei Antonov
2014-01-22 16:25 ` Stanislaw Gruszka
2014-01-29 17:45 ` Sergei Antonov
2014-01-31 12:16 ` Stanislaw Gruszka
2014-02-07 10:11 ` Sergei Antonov
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=20140117100613.GD1425@redhat.com \
--to=sgruszka@redhat.com \
--cc=juhosg@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=saproj@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).