Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 15 4月, 2014 1 次提交
  3. 14 2月, 2014 1 次提交
  5. 23 10月, 2013 1 次提交
  7. 25 3月, 2013 1 次提交
  9. 11 12月, 2012 2 次提交
  11. 28 11月, 2012 1 次提交
  13. 27 11月, 2012 3 次提交
    • E
      wlcore: update events enum/struct to new fw api · c50a2825
      由 Eliad Peller 提交于 
      The event mailbox in wl18xx has a different
(non-compatible) structure.

Create common functions in wlcore to handle the
events, and call them from the chip-specific
event mailbox parsers.

This way, each driver (wl12xx/wl18xx) extracts
the event mailbox by itself according to its
own structure, and then calls the common
wlcore functions to handle it.
Signed-off-by: NEliad Peller <eliad@wizery.com>
Signed-off-by: NLuciano Coelho <coelho@ti.com>
      c50a2825
    • E
      wlcore: split 18xx and 12xx scan mechanism · 78e28062
      由 Eliad Peller 提交于 
      The scan APIs of 12xx and 18xx are totally different.
Use some common functions as much as possible (e.g.
for setting scan channels), but split scan.c into
chip-specific scan.c files, each implementing its
own scan mechanism.

(in other words - move most of the current wlcore's
scan.c into wl12xx, and implement a similar mechanism
in 18xx, according to the new api)

New wlcore ops are introduced in order to call the
chip-specific scan functions.

The template indices used for each scan (regular/scheduled)
are also different between the chips, so set the correct
indices used for each scan type after identifying the chip.
Signed-off-by: NEliad Peller <eliad@wizery.com>
Signed-off-by: NLuciano Coelho <coelho@ti.com>
      78e28062
    • E
      wlcore: implement .remain_on_channel() callback · dabf37db
      由 Eliad Peller 提交于 
      implement the reamin_on_channel() callback by starting
a dev role (already associated with the current vif)
on the requested channel/band.

This channel is usually different from the channel
of the sta role, so pass it to wl12xx_roc() as well,
and notify mac80211 (async) when the fw is ready
on the new channel.

Now, in case of offchannel tx, we should use the dev
role hlid, instead of the sta hlid.
Signed-off-by: NEliad Peller <eliad@wizery.com>
Reviewed-by: NArik Nemtsov <arik@wizery.com>
Signed-off-by: NLuciano Coelho <coelho@ti.com>
      dabf37db
  15. 22 6月, 2012 3 次提交
  17. 07 6月, 2012 1 次提交
  19. 05 6月, 2012 1 次提交
    • A
      wlcore: fixes for connection_loss_work · 6b8bf5bc
      由 Arik Nemtsov 提交于 
      We can't use cancel_delayed_work_sync() from functions that take the
wl->mutex, since connection_loss_work also takes the mutex. This might
result in a deadlock. Restructure the code so the work is synchronously
canceled before taking the mutex.
Avoid a bug where we would indefinitely delay the connection loss
indication by re-queuing the connection loss work on consecutive beacon
loss events.

Cc: bartosz.markowski <bartosz.markowski@tieto.com>
Signed-off-by: NArik Nemtsov <arik@wizery.com>
Signed-off-by: NLuciano Coelho <coelho@ti.com>
      6b8bf5bc
  21. 16 5月, 2012 1 次提交
  23. 12 4月, 2012 6 次提交
  25. 10 4月, 2012 2 次提交
  27. 15 2月, 2012 3 次提交
  29. 21 12月, 2011 1 次提交
    • E
      wl12xx: mark no sched scan only after FW event · ee91d185
      由 Eyal Shapira 提交于 
      stop sched scan isn't an immediate operation
and we need to wait for PERIODIC_SCAN_COMPLETE_EVENT_ID
after sending a stop before changing internal state
and notifying upper layers.
Not doing this caused problems when canceling an existing sched
scan and immediately requesting to start a new one
with a different configuration as the FW was still
in the middle of the previous sched scan.
Signed-off-by: NEyal Shapira <eyal@wizery.com>
Signed-off-by: NLuciano Coelho <coelho@ti.com>
      ee91d185
  31. 08 11月, 2011 1 次提交
  33. 11 10月, 2011 8 次提交
  35. 07 10月, 2011 3 次提交