linux-toradex.git/drivers/net/wireless/rt2x00, branch v3.5.1

rt2800usb: 2001:3c17 is an RT3370 device

2012-08-09T15:22:37+00:00

commit 8fd9d059af12786341dec5a688e607bcdb372238 upstream.

D-Link DWA-123 rev A1

Signed-off-by: Albert Pool
Acked-by: Gertjan van Wingerde 
Signed-off-by: John W. Linville 
Signed-off-by: Greg Kroah-Hartman

rt2x00usb: fix indexes ordering on RX queue kick

2012-07-09T19:01:02+00:00

On rt2x00_dmastart() we increase index specified by Q_INDEX and on
rt2x00_dmadone() we increase index specified by Q_INDEX_DONE. So entries
between Q_INDEX_DONE and Q_INDEX are those we currently process in the
hardware. Entries between Q_INDEX and Q_INDEX_DONE are those we can
submit to the hardware.

According to that fix rt2x00usb_kick_queue(), as we need to submit RX
entries that are not processed by the hardware. It worked before only
for empty queue, otherwise was broken.

Note that for TX queues indexes ordering are ok. We need to kick entries
that have filled skb, but was not submitted to the hardware, i.e.
started from Q_INDEX_DONE and have ENTRY_DATA_PENDING bit set.

From practical standpoint this fixes RX queue stall, usually reproducible
in AP mode, like for example reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=828824

Reported-and-tested-by: Franco Miceli 
Reported-and-tested-by: Tom Horsley 
Cc: stable@vger.kernel.org
Signed-off-by: Stanislaw Gruszka 
Signed-off-by: John W. Linville

rt2x00: use atomic variable for seqno

2012-06-04T19:26:26+00:00

Remove spinlock as atomic_t can be used instead. Note we use only 16
lower bits, upper bits are changed but we impilcilty cast to u16.

This fix possible deadlock on IBSS mode reproted by lockdep:

=================================
[ INFO: inconsistent lock state ]
3.4.0-wl+ #4 Not tainted
---------------------------------
inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage.
kworker/u:2/30374 [HC0[0]:SC0[0]:HE1:SE1] takes:
 (&(&intf->seqlock)->rlock){+.?...}, at: [] rt2x00queue_create_tx_descriptor+0x380/0x490 [rt2x00lib]
{IN-SOFTIRQ-W} state was registered at:
  [] __lock_acquire+0x47b/0x1050
  [] lock_acquire+0x84/0xf0
  [] _raw_spin_lock+0x33/0x40
  [] rt2x00queue_create_tx_descriptor+0x380/0x490 [rt2x00lib]
  [] rt2x00queue_write_tx_frame+0x1a/0x300 [rt2x00lib]
  [] rt2x00mac_tx+0x7f/0x380 [rt2x00lib]
  [] __ieee80211_tx+0x1b3/0x300 [mac80211]
  [] ieee80211_tx+0x105/0x130 [mac80211]
  [] ieee80211_xmit+0xad/0x100 [mac80211]
  [] ieee80211_subif_start_xmit+0x2d9/0x930 [mac80211]
  [] dev_hard_start_xmit+0x307/0x660
  [] sch_direct_xmit+0xa1/0x1e0
  [] dev_queue_xmit+0x183/0x730
  [] neigh_resolve_output+0xfa/0x1e0
  [] ip_finish_output+0x24a/0x460
  [] ip_output+0xb7/0x100
  [] ip_local_out+0x20/0x60
  [] igmpv3_sendpack+0x4f/0x60
  [] igmp_ifc_timer_expire+0x29f/0x330
  [] run_timer_softirq+0x15c/0x2f0
  [] __do_softirq+0xae/0x1e0
irq event stamp: 18380437
hardirqs last  enabled at (18380437): [] __slab_alloc.clone.3+0x67/0x5f0
hardirqs last disabled at (18380436): [] __slab_alloc.clone.3+0x33/0x5f0
softirqs last  enabled at (18377616): [] __do_softirq+0x123/0x1e0
softirqs last disabled at (18377611): [] do_softirq+0x9d/0xe0

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&(&intf->seqlock)->rlock);
  
    lock(&(&intf->seqlock)->rlock);

 *** DEADLOCK ***

4 locks held by kworker/u:2/30374:
 #0:  (wiphy_name(local->hw.wiphy)){++++.+}, at: [] process_one_work+0x109/0x3f0
 #1:  ((&sdata->work)){+.+.+.}, at: [] process_one_work+0x109/0x3f0
 #2:  (&ifibss->mtx){+.+.+.}, at: [] ieee80211_ibss_work+0x1b/0x470 [mac80211]
 #3:  (&intf->beacon_skb_mutex){+.+...}, at: [] rt2x00queue_update_beacon+0x24/0x50 [rt2x00lib]

stack backtrace:
Pid: 30374, comm: kworker/u:2 Not tainted 3.4.0-wl+ #4
Call Trace:
 [] print_usage_bug+0x1f6/0x220
 [] mark_lock+0x2c2/0x300
 [] ? check_usage_forwards+0xc0/0xc0
 [] __lock_acquire+0x4bc/0x1050
 [] ? __kmalloc_track_caller+0x1c0/0x1d0
 [] ? copy_skb_header+0x26/0x90
 [] lock_acquire+0x84/0xf0
 [] ? rt2x00queue_create_tx_descriptor+0x380/0x490 [rt2x00lib]
 [] _raw_spin_lock+0x33/0x40
 [] ? rt2x00queue_create_tx_descriptor+0x380/0x490 [rt2x00lib]
 [] rt2x00queue_create_tx_descriptor+0x380/0x490 [rt2x00lib]
 [] rt2x00queue_update_beacon_locked+0x5f/0xb0 [rt2x00lib]
 [] rt2x00queue_update_beacon+0x2d/0x50 [rt2x00lib]
 [] rt2x00mac_bss_info_changed+0x1ca/0x200 [rt2x00lib]
 [] ? rt2x00mac_remove_interface+0x70/0x70 [rt2x00lib]
 [] ieee80211_bss_info_change_notify+0xe0/0x1d0 [mac80211]
 [] __ieee80211_sta_join_ibss+0x3b8/0x610 [mac80211]
 [] ? mark_held_locks+0x64/0xc0
 [] ? virt_efi_query_capsule_caps+0x12/0x50
 [] ieee80211_sta_join_ibss+0xf9/0x140 [mac80211]
 [] ieee80211_ibss_work+0x416/0x470 [mac80211]
 [] ? trace_hardirqs_on+0xb/0x10
 [] ? skb_dequeue+0x4b/0x70
 [] ieee80211_iface_work+0x13f/0x230 [mac80211]
 [] ? process_one_work+0x109/0x3f0
 [] process_one_work+0x185/0x3f0
 [] ? process_one_work+0x109/0x3f0
 [] ? ieee80211_teardown_sdata+0xa0/0xa0 [mac80211]
 [] worker_thread+0x116/0x270
 [] ? manage_workers+0x1e0/0x1e0
 [] kthread+0x84/0x90
 [] ? __init_kthread_worker+0x60/0x60
 [] kernel_thread_helper+0x6/0x10

Cc: stable@vger.kernel.org
Signed-off-by: Stanislaw Gruszka 
Acked-by: Helmut Schaa 
Acked-by: Gertjan van Wingerde 
Signed-off-by: John W. Linville

Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net

2012-05-24T18:54:29+00:00

Pull more networking updates from David Miller:
 "Ok, everything from here on out will be bug fixes."

1) One final sync of wireless and bluetooth stuff from John Linville.
   These changes have all been in his tree for more than a week, and
   therefore have had the necessary -next exposure.  John was just away
   on a trip and didn't have a change to send the pull request until a
   day or two ago.

2) Put back some defines in user exposed header file areas that were
   removed during the tokenring purge.  From Stephen Hemminger and Paul
   Gortmaker.

3) A bug fix for UDP hash table allocation got lost in the pile due to
   one of those "you got it..  no I've got it.." situations.  :-)

   From Tim Bird.

4) SKB coalescing in TCP needs to have stricter checks, otherwise we'll
   try to coalesce overlapping frags and crash.  Fix from Eric Dumazet.

5) RCU routing table lookups can race with free_fib_info(), causing
   crashes when we deref the device pointers in the route.  Fix by
   releasing the net device in the RCU callback.  From Yanmin Zhang.

* git://git.kernel.org/pub/scm/linux/kernel/git/davem/net: (293 commits)
  tcp: take care of overlaps in tcp_try_coalesce()
  ipv4: fix the rcu race between free_fib_info and ip_route_output_slow
  mm: add a low limit to alloc_large_system_hash
  ipx: restore token ring define to include/linux/ipx.h
  if: restore token ring ARP type to header
  xen: do not disable netfront in dom0
  phy/micrel: Fix ID of KSZ9021
  mISDN: Add X-Tensions USB ISDN TA XC-525
  gianfar:don't add FCB length to hard_header_len
  Bluetooth: Report proper error number in disconnection
  Bluetooth: Create flags for bt_sk()
  Bluetooth: report the right security level in getsockopt
  Bluetooth: Lock the L2CAP channel when sending
  Bluetooth: Restore locking semantics when looking up L2CAP channels
  Bluetooth: Fix a redundant and problematic incoming MTU check
  Bluetooth: Add support for Foxconn/Hon Hai AR5BBU22 0489:E03C
  Bluetooth: Fix EIR data generation for mgmt_device_found
  Bluetooth: Fix Inquiry with RSSI event mask
  Bluetooth: improve readability of l2cap_seq_list code
  Bluetooth: Fix skb length calculation
  ...

Merge tag 'usb-3.5-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb

2012-05-22T22:50:46+00:00

Pull USB 3.5-rc1 changes from Greg Kroah-Hartman:
"Here is the big USB 3.5-rc1 pull request for the 3.5-rc1 merge window.

It's touches a lot of different parts of the kernel, all USB drivers,
due to some API cleanups (getting rid of the ancient err() macro) and
some changes that are needed for USB 3.0 power management updates.

There are also lots of new drivers, pimarily gadget, but others as
well. We deleted a staging driver, which was nice, and finally
dropped the obsolete usbfs code, which will make Al happy to never
have to touch that again.

There were some build errors in the tree that linux-next found a few
days ago, but those were fixed by the most recent changes (all were
due to us not building with CONFIG_PM disabled.)

Signed-off-by: Greg Kroah-Hartman "

* tag 'usb-3.5-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb: (477 commits)
xhci: Fix DIV_ROUND_UP compile error.
xhci: Fix compile with CONFIG_USB_SUSPEND=n
USB: Fix core compile with CONFIG_USB_SUSPEND=n
brcm80211: Fix compile error for .disable_hub_initiated_lpm.
Revert "USB: EHCI: work around bug in the Philips ISP1562 controller"
MAINTAINERS: Add myself as maintainer to the USB PHY Layer
USB: EHCI: fix command register configuration lost problem
USB: Remove races in devio.c
USB: ehci-platform: remove update_device
USB: Disable hub-initiated LPM for comms devices.
xhci: Add Intel U1/U2 timeout policy.
xhci: Add infrastructure for host-specific LPM policies.
USB: Add macros for interrupt endpoint types.
xhci: Reserve one command for USB3 LPM disable.
xhci: Some Evaluate Context commands must succeed.
USB: Disable USB 3.0 LPM in critical sections.
USB: Add support to enable/disable USB3 link states.
USB: Allow drivers to disable hub-initiated LPM.
USB: Calculate USB 3.0 exit latencies for LPM.
USB: Refactor code to set LPM support flag.
...

Conflicts:
arch/arm/mach-exynos/mach-nuri.c
arch/arm/mach-exynos/mach-universal_c210.c
drivers/net/wireless/ath/ath6kl/usb.c

USB: Disable hub-initiated LPM for comms devices.

2012-05-18T22:42:55+00:00

Hub-initiated LPM is not good for USB communications devices.  Comms
devices should be able to tell when their link can go into a lower power
state, because they know when an incoming transmission is finished.
Ideally, these devices would slam their links into a lower power state,
using the device-initiated LPM, after finishing the last packet of their
data transfer.

If we enable the idle timeouts for the parent hubs to enable
hub-initiated LPM, we will get a lot of useless LPM packets on the bus
as the devices reject LPM transitions when they're in the middle of
receiving data.  Worse, some devices might blindly accept the
hub-initiated LPM and power down their radios while they're in the
middle of receiving a transmission.

The Intel Windows folks are disabling hub-initiated LPM for all USB
communications devices under a xHCI USB 3.0 host.  In order to keep
the Linux behavior as close as possible to Windows, we need to do the
same in Linux.

Set the disable_hub_initiated_lpm flag for for all USB communications
drivers.  I know there aren't currently any USB 3.0 devices that
implement these class specifications, but we should be ready if they do.

Signed-off-by: Sarah Sharp 
Cc: Marcel Holtmann 
Cc: Gustavo Padovan 
Cc: Johan Hedberg 
Cc: Hansjoerg Lipp 
Cc: Tilman Schmidt 
Cc: Karsten Keil 
Cc: Peter Korsgaard 
Cc: Jan Dumon 
Cc: Petko Manolov 
Cc: Steve Glendinning 
Cc: "John W. Linville" 
Cc: Kalle Valo 
Cc: "Luis R. Rodriguez" 
Cc: Jouni Malinen 
Cc: Vasanthakumar Thiagarajan 
Cc: Senthil Balasubramanian 
Cc: Christian Lamparter 
Cc: Brett Rudley 
Cc: Roland Vossen 
Cc: Arend van Spriel 
Cc: "Franky (Zhenhui) Lin" 
Cc: Kan Yan 
Cc: Dan Williams 
Cc: Jussi Kivilinna 
Cc: Ivo van Doorn 
Cc: Gertjan van Wingerde 
Cc: Helmut Schaa 
Cc: Herton Ronaldo Krzesinski 
Cc: Hin-Tak Leung 
Cc: Larry Finger 
Cc: Chaoming Li 
Cc: Daniel Drake 
Cc: Ulrich Kunitz 
Signed-off-by: Sarah Sharp

rt2x00:Add RT539b chipset support

2012-05-16T16:46:37+00:00

Signed-off-by: Zero.Lin 
Acked-by: Gertjan van Wingerde 
Signed-off-by: John W. Linville

rt2x00: Add debugfs access for rfcsr register

2012-05-09T01:53:46+00:00

RFCSR is only used in rt2800. For other chipsets, the debug struct
for rfcsr should be zeroed, which isn't be an issue, since the code
can now cope with that.

Signed-off-by: Anisse Astier 
Acked-by: Ivo van Doorn 
Signed-off-by: John W. Linville

rt2x00: debugfs support - allow a register to be empty

2012-05-09T01:53:45+00:00

Allow a register to be unspecified, therefore not creating its debugfs
file entry.

Signed-off-by: Anisse Astier 
Acked-by: Ivo van Doorn 
Signed-off-by: John W. Linville

rt2800: add chipset revision RT5390R support

2012-04-23T19:37:42+00:00

About 70% of the chips with revision RT5390R initialize incorrectly, using
the auxiliary antenna instead of the main one. The net result is that
signal reception is very poor (no AP further than 1M).

This chipset differs from RT5390 and RT5390F by its support of hardware
antenna diversity. Therefore antenna selection should be done
differently, by disabling software features and previously selected
antenna.

This changeset does just that, and makes all RT5390R work properly.

This is based on Ralink's 2012_03_22_RT5572_Linux_STA_v2.6.0.0_DPO
driver.

Signed-off-by: Anisse Astier 
Signed-off-by: John W. Linville