diff options
| author |   Ido Yariv <ido@wizery.com> | 2011-06-06 14:57:06 +0300 |
|---|---|---|
| committer |   Luciano Coelho <coelho@ti.com> | 2011-06-27 15:10:56 +0300 |
| commit | 95dac04f881322b510c45e5ae83f0dbee4f823a2 (patch) | |
| tree | 6b79761eb78627be7ef14c339a708fdf3b26231a /drivers/net/wireless/wl12xx/acx.h | |
| parent | wl12xx: Avoid recovery while one is already in progress (diff) | |
| download | linux-dev-95dac04f881322b510c45e5ae83f0dbee4f823a2.tar.xz linux-dev-95dac04f881322b510c45e5ae83f0dbee4f823a2.zip | |
wl12xx: Support routing FW logs to the host
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: Ido Yariv <ido@wizery.com>
Signed-off-by: Luciano Coelho <coelho@ti.com>
Diffstat (limited to 'drivers/net/wireless/wl12xx/acx.h')
| -rw-r--r-- | drivers/net/wireless/wl12xx/acx.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/net/wireless/wl12xx/acx.h b/drivers/net/wireless/wl12xx/acx.h index f1d553136173..d303265f163a 100644 --- a/drivers/net/wireless/wl12xx/acx.h +++ b/drivers/net/wireless/wl12xx/acx.h @@ -828,6 +828,8 @@ struct wl1271_acx_sta_config_memory { u8 tx_free_req; u8 rx_free_req; u8 tx_min; + u8 fwlog_blocks; + u8 padding[3]; } __packed; struct wl1271_acx_mem_map { |