1. 27 9月, 2012 1 次提交
  2. 11 7月, 2012 2 次提交
    • A
      wlcore: don't set SDIO_FAILED flag when driver state is off · 4455556d
      Arik Nemtsov 提交于
      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
    • I
      wlcore: Prevent processing of work items during op_stop · c24ec83b
      Ido Yariv 提交于
      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
  3. 23 6月, 2012 1 次提交
    • A
      wlcore: don't allow SDIO read/writes after failure · 1d23396d
      Arik Nemtsov 提交于
      Set a flag and after the first read/write failure is encountered.
      This flag will disallow further SDIO read/writes until op_stop() is
      executed, which will clear all flags.
      
      This prevents further errors from occurring, since one error usually
      indicates that IO operations won't work anymore until the chip is
      rebooted.  By blocking more calls, we avoid extra timeouts and having
      to wait for them to occur.
      
      [Added second paragraph explaining why the change is needed. -- Luca]
      Signed-off-by: NArik Nemtsov <arik@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      1d23396d
  4. 22 6月, 2012 10 次提交
  5. 12 4月, 2012 5 次提交
  6. 15 2月, 2012 1 次提交
    • L
      wl12xx: move partition table definition to io.c · 0becb14a
      Luciano Coelho 提交于
      Up till now we only needed to access the partition table in boot.c.
      But to add support for reading the MAC address from the FUSE in
      testmode, we will have to change the partition in testmode.c.
      
      Thus, we move the partition table to io.c and export it via io.h.  It
      makes more sense to have it in the io part anyway.
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      0becb14a
  7. 11 10月, 2011 2 次提交
  8. 22 8月, 2011 1 次提交
  9. 27 6月, 2011 1 次提交
    • I
      wl12xx: Support routing FW logs to the host · 95dac04f
      Ido Yariv 提交于
      A recently added feature to the firmware enables the driver to retrieve
      firmware logs via the host bus (SDIO or SPI).
      
      There are two modes of operation:
      1. On-demand: The FW collects its log in an internal ring buffer. This
         buffer can later be read, for example, upon recovery.
      2. Continuous: The FW pushes the FW logs as special packets in the RX
         path.
      
      Reading the internal ring buffer does not involve the FW. Thus, as long
      as the HW is not in ELP, it should be possible to read the logs, even if
      the FW crashes.
      
      A sysfs binary file named "fwlog" was added to support this feature,
      letting a monitor process read the FW messages. The log is transferred
      from the FW only when available, so the reading process might block.
      Signed-off-by: NIdo Yariv <ido@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      95dac04f
  10. 07 6月, 2011 1 次提交
  11. 19 4月, 2011 3 次提交
    • O
      wl12xx: fix roaming · c5745187
      Ohad Ben-Cohen 提交于
      The wl12xx device normally drops all frames coming from BSSID
      it is not joined with.
      
      This behavior is configured today by the wl12xx driver in response
      to a handful of ieee80211_bss_change and ieee80211_conf_changed
      notification flags, such as BSS_CHANGED_ASSOC, BSS_CHANGED_BSSID,
      IEEE80211_CONF_CHANGE_IDLE, etc..
      
      This breaks when we roam to a new BSSID, where authentication frames
      are sent before any BSS_CHANGED/CONF_CHANGED flags are received.
      When this happens the hardware silently drops the authentication
      responses, and the roaming fails.
      
      Ideally this aggressive filtering behavior of the device should be disabled
      upon a notification from mac80211. Such notification will take place
      after multi-channel support will be added: mac80211 will likely send a
      remain-on-channel notification to drivers when entering sensitive
      states (like authentication), otherwise the firmware might jump to
      different channels (to serve a different role).
      
      Until those notifications materialize, disable the hw BSSID filter
      when authentication requests are sent, so roaming would work.
      Signed-off-by: NOhad Ben-Cohen <ohad@wizery.com>
      Reviewed-by: NLuciano Coelho <coelho@ti.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      c5745187
    • S
      wl12xx: 1281/1283 support - Add dummy packet support · ae47c45f
      Shahar Levi 提交于
      Support sending dummy packet to wl128x FW as results of
      dummy packet event. That is part of dynamic TX mem blocks mechanism.
      
      Only send dummy packet when not in AP mode.
      
      [Even though the DUMMY_PACKET_EVENT_ID and the
      STA_REMOVE_COMPLETE_EVENT_ID events are defined to the same value, we
      need to treat them separately in the code.  Keep the check and enable
      STA_REMOVE_COMPLETE_EVENT_ID for AP mode and DUMMY_PACKET_EVENT_ID for
      STA.  Moved one warning to a cleaner place.  Use WL1271_TID_MGMT for
      dummy packets -- Luca]
      Signed-off-by: NShahar Levi <shahar_levi@ti.com>
      Reviewed-by: NLuciano Coelho <coelho@ti.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      ae47c45f
    • S
      wl12xx: 1281/1283 support - Add acx commands · 48a61477
      Shahar Levi 提交于
      New acx command that sets: Rx fifo enable reduced bus transactions
      in RX path. Tx bus transactions padding to SDIO block size that
      improve preference in Tx and essential for working with SDIO HS (48Mhz).
      The max SDIO block size is 256 when working with Tx bus transactions
      padding to SDIO block.
      
      Add new ops to SDIO & SPI that handles the win size change in case of
      transactions padding (relevant only for SDIO).
      
      [Fix endianess issues; simplify sdio-specific block_size handling;
      minor changes in comments; use "aligned_len" in one calculation
      instead of "pad" to avoid confusion -- Luca]
      Signed-off-by: NShahar Levi <shahar_levi@ti.com>
      Reviewed-by: NLuciano Coelho <coelho@ti.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      48a61477
  12. 31 3月, 2011 1 次提交
  13. 03 3月, 2011 1 次提交
    • I
      wl12xx: Switch to a threaded interrupt handler · a620865e
      Ido Yariv 提交于
      To achieve maximal throughput, it is very important to react to
      interrupts as soon as possible. Currently the interrupt handler wakes up
      a worker for handling interrupts in process context. A cleaner and more
      efficient design would be to request a threaded interrupt handler.  This
      handler's priority is very high, and can do blocking operations such as
      SDIO/SPI transactions.
      
      Some work can be deferred, mostly calls to mac80211 APIs
      (ieee80211_rx_ni and ieee80211_tx_status). By deferring such work to a
      different worker, we can keep the irq handler thread more I/O
      responsive. In addition, on multi-core systems the two threads can be
      scheduled on different cores, which will improve overall performance.
      
      The use of WL1271_FLAG_IRQ_PENDING & WL1271_FLAG_IRQ_RUNNING was
      changed. For simplicity, always query the FW for more pending
      interrupts. Since there are relatively long bursts of interrupts, the
      extra FW status read overhead is negligible. In addition, this enables
      registering the IRQ handler with the ONESHOT option.
      Signed-off-by: NIdo Yariv <ido@wizery.com>
      Reviewed-by: NLuciano Coelho <coelho@ti.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      a620865e
  14. 22 11月, 2010 1 次提交
  15. 21 9月, 2010 1 次提交
  16. 08 5月, 2010 1 次提交
  17. 24 3月, 2010 2 次提交
  18. 10 3月, 2010 5 次提交