提交 · 0fc1d2e9fe0820cc0c3247c5766c21b8de65a886 · openanolis / cloud-kernel

11 7月, 2012 14 次提交

wl12xx/wl18xx: use a dynamic PS timeout of 1.5sec · 0fc1d2e9

由 Arik Nemtsov 提交于 7月 03, 2012

It seems some parties have bad user experience when smaller values
are used. This should have little implications for power consumption,
since traffic is bursty in nature.
Signed-off-by: NArik Nemtsov <arik@wizery.com>

0fc1d2e9

wlcore: define number of supported bands internally · 091185d6

由 Arik Nemtsov 提交于 7月 03, 2012

Avoid using the IEEE80211_NUM_BANDS constant for arrays sizes etc, as
this can contain bands unsupported by the driver (e.g. 60Ghz). Use an
internal constant to determine the number of bands.
Signed-off-by: NArik Nemtsov <arik@wizery.com>

091185d6

wlcore: don't set SDIO_FAILED flag when driver state is off · 4455556d

由 Arik Nemtsov 提交于 7月 03, 2012

If some IO read/write fails while the FW is not loaded, a recovery
will not take place. This means the SDIO_FAILED flag will stay in place
forever and prevent further read/writes.

This can happen if a check for STATE_OFF was forgotten in some routine.

Take this opportunity to rename the flag to IO_FAILED, since we support
other buses as well.
Reported-by: NIdo Yariv <ido@wizery.com>
Signed-off-by: NArik Nemtsov <arik@wizery.com>

4455556d

wlcore: change the wait for event mechanism · c45ee4ff

由 Yoni Divinsky 提交于 6月 27, 2012

wlcore needs to wait for certain events for example
for roc complete event. Usually the events are received
from the FW very fast, therefore wlcore can poll with
a short delay and if after a second the event was
not received yet poll with a long (1-5 msec) delay.

This implementation is similar to the sending of
commands to the FW.

Empirically the change reduced the wait for roc event
from ~10-40msec to 100s of usecs.

[replace udelay/msleep with usleep_range - Arik]
Signed-off-by: NYoni Divinsky <yoni.divinsky@ti.com>
Signed-off-by: NArik Nemtsov <arik@wizery.com>

c45ee4ff

wlcore: Prevent processing of work items during op_stop · c24ec83b

由 Ido Yariv 提交于 6月 26, 2012

The interrupt line is disabled in op_stop using disable_irq. Since
pending interrupts are synchronized, the mutex has to be released before
disabling the interrupt to avoid a deadlock with the interrupt handler.

In addition, the internal state of the driver is only set to 'off'
after the interrupt is disabled. Otherwise, if an interrupt fires after
the state is set but before the interrupt line is disabled, the
interrupt handler will not be able to acknowledge the interrupt
resulting in an interrupt storm.

The driver's operations might be called during recovery. If these
acquire the mutex after it was released by op_stop, but before the
driver's state is changed, they may queue new work items instead of just
failing. This is especially problematic in the case of scans, in which a
new scan may be scheduled after all scan requests were cancelled.
Signed-off-by: NIdo Yariv <ido@wizery.com>
Signed-off-by: NArik Nemtsov <arik@wizery.com>

c24ec83b

wlcore: implement .flush callback · d8ae5a25

由 Eliad Peller 提交于 6月 25, 2012

implement the .flush() callback by simply calling wl1271_tx_flush().
Signed-off-by: NEliad Peller <eliad@wizery.com>
Signed-off-by: NLuciano Coelho <coelho@ti.com>

d8ae5a25

wl12xx/wlcore: increase FW filename version · 66ef60ad

由 Luciano Coelho 提交于 6月 27, 2012

We have some API changes and new features in the new firmwares that
are not compatible with older drivers.  Increase the version of the FW
filenames for wl12xx to 5.

Additionally, remove the duplicate definitions from wlcore_i.h and
remove the MODULE_FIRMWARE macro calls from the SDIO and SPI modules,
since they're irrelevant there.
Signed-off-by: NLuciano Coelho <coelho@ti.com>

66ef60ad

wlcore: add probe request templates for sched and one-shot scans · 3df74f46

由 Yoni Divinsky 提交于 6月 27, 2012

The driver configures the firmware template for probe requests during
the scan process.  If the same template is used for one-shot and sched
scans they will override each other when running scans simultaneously.

This fix works only on firmwares later than X.3.9.2.112 for single
role and X.3.9.2.23 for multi-role.

[Some cleaning-up and renaming of the quirk to something smaller --
Luca.]
Signed-off-by: NYoni Divinsky <yoni.divinsky@ti.com>
Signed-off-by: NLuciano Coelho <coelho@ti.com>

3df74f46

wlcore: always clear recovery flag during recovery_work · b034fd6f