Revision tags: v4.0-rc1, v3.19, v3.19-rc7, v3.19-rc6, v3.19-rc5, v3.19-rc4, v3.19-rc3 |
|
#
1cd91b2c |
| 29-Dec-2014 |
Guy Mishol <guym@ti.com> |
wlcore: add dfs region to reg domain update cmd
Add dfs region to the reg domain channel update command.
Signed-off-by: Guy Mishol <guym@ti.com> Signed-off-by: Eliad Peller <eliad@wizery.com> Signe
wlcore: add dfs region to reg domain update cmd
Add dfs region to the reg domain channel update command.
Signed-off-by: Guy Mishol <guym@ti.com> Signed-off-by: Eliad Peller <eliad@wizery.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
show more ...
|
#
4ce9fad3 |
| 29-Dec-2014 |
Eliad Peller <eliad@wizery.com> |
wlcore: allow using dfs channels
Since we are going to support dfs channels, there is no reason to mark them as NO_IR (having the DFS flag is enough anyway).
Additionally, when setting the regdomai
wlcore: allow using dfs channels
Since we are going to support dfs channels, there is no reason to mark them as NO_IR (having the DFS flag is enough anyway).
Additionally, when setting the regdomain configuration, enable usable dfs channels.
Signed-off-by: Eliad Peller <eliad@wizery.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
show more ...
|
#
750e9d15 |
| 29-Dec-2014 |
Eliad Peller <eliad@wizery.com> |
wl18xx: add radar detection implementation
Add support for CAC start/stop commands, and pass radar detection events from the fw to mac80211.
Bump fw name (to wl18xx-fw-4.bin) and min fw version (to
wl18xx: add radar detection implementation
Add support for CAC start/stop commands, and pass radar detection events from the fw to mac80211.
Bump fw name (to wl18xx-fw-4.bin) and min fw version (to 8.9.*.*.11), and align event mailbox accordingly.
Signed-off-by: Guy Mishol <guym@ti.com> Signed-off-by: Eliad Peller <eliad@wizery.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
show more ...
|
Revision tags: v3.19-rc2, v3.19-rc1, v3.18, v3.18-rc7, v3.18-rc6, v3.18-rc5, v3.18-rc4, v3.18-rc3, v3.18-rc2, v3.18-rc1, v3.17, v3.17-rc7, v3.17-rc6, v3.17-rc5, v3.17-rc4, v3.17-rc3, v3.17-rc2, v3.17-rc1, v3.16, v3.16-rc7, v3.16-rc6, v3.16-rc5, v3.16-rc4, v3.16-rc3, v3.16-rc2, v3.16-rc1 |
|
#
a344d677 |
| 12-Jun-2014 |
Johannes Berg <johannes.berg@intel.com> |
mac80211: allow drivers to support NL80211_SCAN_FLAG_RANDOM_ADDR
Allow drivers to support NL80211_SCAN_FLAG_RANDOM_ADDR with software based scanning and generate a random MAC address for them for ev
mac80211: allow drivers to support NL80211_SCAN_FLAG_RANDOM_ADDR
Allow drivers to support NL80211_SCAN_FLAG_RANDOM_ADDR with software based scanning and generate a random MAC address for them for every scan request with the flag.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
show more ...
|
#
d351f5fe |
| 10-Nov-2014 |
Luciano Coelho <luciano.coelho@intel.com> |
wlcore: make wlcore_cmd_send_failsafe() static
The wlcore_cmd_send_failsafe() function is only called in the cmd.c file, where it is definde. Make it static.
Additionally, move the EXPORT_SYMBOL m
wlcore: make wlcore_cmd_send_failsafe() static
The wlcore_cmd_send_failsafe() function is only called in the cmd.c file, where it is definde. Make it static.
Additionally, move the EXPORT_SYMBOL macro for wl1271_cmd_send() to the right place.
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
show more ...
|
#
f5b8f479 |
| 10-Nov-2014 |
Luciano Coelho <luciano.coelho@intel.com> |
wlcore: check minimum buffer size in some cmd_send functions
Check for the minimum required buffer length in wlcore_cmd_send() and wlcore_cmd_configure_failsafe. This ensures that we will never try
wlcore: check minimum buffer size in some cmd_send functions
Check for the minimum required buffer length in wlcore_cmd_send() and wlcore_cmd_configure_failsafe. This ensures that we will never try to use a buffer that is smaller than the required header.
Reported-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: Luciano Coelho <luciano.coelho@intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
show more ...
|
#
30a00358 |
| 10-Jul-2014 |
Eliad Peller <eliad@wizery.com> |
wlcore: user smaller sqn padding for GEM
On recovery, we increase the current seq num by WL1271_TX_SQN_POST_RECOVERY_PADDING in order to compensate for packets we might have missed during recovery.
wlcore: user smaller sqn padding for GEM
On recovery, we increase the current seq num by WL1271_TX_SQN_POST_RECOVERY_PADDING in order to compensate for packets we might have missed during recovery.
It seems that some GEM APs have issues when the gap is too big, so use a smaller padding in this case.
Signed-off-by: Eliad Peller <eliad@wizery.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
show more ...
|
#
50d26aa3 |
| 10-Jul-2014 |
Eliad Peller <eliad@wizery.com> |
wlcore: save seq num only between recoveries
We want seq num (freed_pkts) to be initialized on each new connection, but keep persistent between recoveries/suspends.
Save the freed_pkts in the priva
wlcore: save seq num only between recoveries
We want seq num (freed_pkts) to be initialized on each new connection, but keep persistent between recoveries/suspends.
Save the freed_pkts in the private block of the sta struct (we already do a similar thing for AP's stations).
However, keep the old wlvif->total_freed_pkts in order to avoid too intrusive change.
Signed-off-by: Eliad Peller <eliad@wizery.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
show more ...
|
Revision tags: v3.15, v3.15-rc8, v3.15-rc7, v3.15-rc6, v3.15-rc5, v3.15-rc4, v3.15-rc3, v3.15-rc2, v3.15-rc1, v3.14, v3.14-rc8, v3.14-rc7, v3.14-rc6, v3.14-rc5, v3.14-rc4, v3.14-rc3, v3.14-rc2 |
|
#
633e2713 |
| 06-Feb-2014 |
David Spinadel <david.spinadel@intel.com> |
mac80211: split sched scan IEs
Split sched scan IEs to band specific and not band specific blocks. Common IEs blocks may be sent to the FW once per command, instead of per band.
This allows optimiz
mac80211: split sched scan IEs
Split sched scan IEs to band specific and not band specific blocks. Common IEs blocks may be sent to the FW once per command, instead of per band.
This allows optimization of size of the command, which may be required by some drivers (eg. iwlmvm with newer firmware version).
As this changes the mac80211 API, update all drivers to use the new version correctly, even if they don't (yet) make use of the split data.
Signed-off-by: David Spinadel <david.spinadel@intel.com> Reviewed-by: Alexander Bondar <alexander.bondar@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
show more ...
|
#
1ede9500 |
| 10-Feb-2014 |
Arik Nemtsov <arik@wizery.com> |
wlcore: decrease warning verbosity during recovery
Silently ignore repetitive scheduling of recovery work and commands being passed to the bus when the HW is not available. This can happen many time
wlcore: decrease warning verbosity during recovery
Silently ignore repetitive scheduling of recovery work and commands being passed to the bus when the HW is not available. This can happen many times during recovery and slow it down. It also spams the kernel logs.
Signed-off-by: Arik Nemtsov <arik@wizery.com> Signed-off-by: Eliad Peller <eliad@wizery.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
show more ...
|
#
028e7243 |
| 10-Feb-2014 |
Eliad Peller <eliad@wizery.com> |
wl18xx: move to new firmware (wl18xx-fw-3.bin)
Bump the min wl18xx fw version to 8.8.0.0.13
This fw is not backward compatible with older firmware (due to api changes), so use bump the firmware nam
wl18xx: move to new firmware (wl18xx-fw-3.bin)
Bump the min wl18xx fw version to 8.8.0.0.13
This fw is not backward compatible with older firmware (due to api changes), so use bump the firmware name as well.
Some modifications were done to the driver-fw api in order to support multiple APs.
Additionally, some of the consts (such as max stations, max links and max RX BA sessions) were changed.
Signed-off-by: Arik Nemtsov <arik@wizery.com> Signed-off-by: Eliad Peller <eliad@wizery.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
show more ...
|
#
da08fdfa |
| 10-Feb-2014 |
Eliad Peller <eliad@wizery.com> |
wlcore/wl12xx/wl18xx: configure num_links per-hw
Upcoming fw versions will have different max links support (according to the hw). Get ready for it by configuring wl->num_links per-hw, instead of us
wlcore/wl12xx/wl18xx: configure num_links per-hw
Upcoming fw versions will have different max links support (according to the hw). Get ready for it by configuring wl->num_links per-hw, instead of using the const WL12XX_MAX_LINKS.
However, continue using WLCORE_MAX_LINKS in order to simplify structs declarations (we use it in multiple bitmaps, and converting them to dynamic arrays is just cumbersome).
Signed-off-by: Eliad Peller <eliad@wizery.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
show more ...
|
#
75fb4df7 |
| 10-Feb-2014 |
Eliad Peller <eliad@wizery.com> |
wlcore/wl12xx/wl18xx: simplify fw_status handling
Instead of splitting the fw_status into 2 and using some complex calculations, read the fw status and let each low-level driver (wl12xx/wl18xx) conv
wlcore/wl12xx/wl18xx: simplify fw_status handling
Instead of splitting the fw_status into 2 and using some complex calculations, read the fw status and let each low-level driver (wl12xx/wl18xx) convert it into a common struct.
This is required for the upcoming fw api changes, which break the current logic anyway.
Signed-off-by: Eliad Peller <eliad@wizery.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
show more ...
|
Revision tags: v3.14-rc1, v3.13, v3.13-rc8, v3.13-rc7, v3.13-rc6, v3.13-rc5, v3.13-rc4, v3.13-rc3, v3.13-rc2, v3.13-rc1, v3.12, v3.12-rc7 |
|
#
8fe02e16 |
| 21-Oct-2013 |
Luis R. Rodriguez <mcgrof@do-not-panic.com> |
cfg80211: consolidate passive-scan and no-ibss flags
These two flags are used for the same purpose, just combine them into a no-ir flag to annotate no initiating radiation is allowed.
Old userspace
cfg80211: consolidate passive-scan and no-ibss flags
These two flags are used for the same purpose, just combine them into a no-ir flag to annotate no initiating radiation is allowed.
Old userspace sending either flag will have it treated as the no-ir flag. To be considerate to older userspace we also send both the no-ir flag and the old no-ibss flags. Newer userspace will have to be aware of older kernels.
Update all places in the tree using these flags with the following semantic patch:
@@ @@ -NL80211_RRF_PASSIVE_SCAN +NL80211_RRF_NO_IR @@ @@ -NL80211_RRF_NO_IBSS +NL80211_RRF_NO_IR @@ @@ -IEEE80211_CHAN_PASSIVE_SCAN +IEEE80211_CHAN_NO_IR @@ @@ -IEEE80211_CHAN_NO_IBSS +IEEE80211_CHAN_NO_IR @@ @@ -NL80211_RRF_NO_IR | NL80211_RRF_NO_IR +NL80211_RRF_NO_IR @@ @@ -IEEE80211_CHAN_NO_IR | IEEE80211_CHAN_NO_IR +IEEE80211_CHAN_NO_IR @@ @@ -(NL80211_RRF_NO_IR) +NL80211_RRF_NO_IR @@ @@ -(IEEE80211_CHAN_NO_IR) +IEEE80211_CHAN_NO_IR
Along with some hand-optimisations in documentation, to remove duplicates and to fix some indentation.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com> [do all the driver updates in one go] Signed-off-by: Johannes Berg <johannes.berg@intel.com>
show more ...
|
Revision tags: v3.12-rc6, v3.12-rc5, v3.12-rc4, v3.12-rc3, v3.12-rc2, v3.12-rc1 |
|
#
c2e64242 |
| 09-Sep-2013 |
Barak Bercovitz <barak@wizery.com> |
wlcore: Allow stopping fw log in recovery
The FW panic log is read during recovery work. It has to be stopped properly before reading. otherwise, inconsistent data might be read which cause the driv
wlcore: Allow stopping fw log in recovery
The FW panic log is read during recovery work. It has to be stopped properly before reading. otherwise, inconsistent data might be read which cause the driver to freeze.
__wlcore_cmd_send has to work for the special case of CMD_STOP_FWLOGGER, while in recovery, in order to stop the fw log before it is read.
Signed-off-by: Barak Bercovitz <barak@wizery.com> Signed-off-by: Eliad Peller <eliad@wizery.com> Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
show more ...
|
#
4b674144 |
| 09-Sep-2013 |
Igal Chernobelsky <igalc@ti.com> |
wlcore: fix interrogate command length
Change interrogate command prototype to have command size and returned buffer length. This fixes the issue when command parameters are needed to be passed to F
wlcore: fix interrogate command length
Change interrogate command prototype to have command size and returned buffer length. This fixes the issue when command parameters are needed to be passed to FW in addition to acx header as in the case with get RSSI command, where role_id has to be passed.
Signed-off-by: Igal Chernobelsky <igalc@ti.com> Signed-off-by: Eliad Peller <eliad@wizery.com> Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
show more ...
|
#
49540d1b |
| 17-Sep-2013 |
Eliad Peller <eliad@wizery.com> |
wlcore: clarify and fix regulatory domain bit translation
Channels 52-64 were mapped incorrectly.
Refactor and document wlcore_get_reg_conf_ch_idx() in order to make it clear what's going on there.
wlcore: clarify and fix regulatory domain bit translation
Channels 52-64 were mapped incorrectly.
Refactor and document wlcore_get_reg_conf_ch_idx() in order to make it clear what's going on there.
While on it, fix the return value check to consider 0 as a valid return value as well (indicates channel 1).
Reported-by: Yaniv Machani <yanivma@ti.com> Signed-off-by: Eliad Peller <eliad@wizery.com> Signed-off-by: Ido Reis <idor@ti.com> Signed-off-by: Victor Goldenshtein <victorg@ti.com> Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
show more ...
|
#
0fe72086 |
| 17-Sep-2013 |
Victor Goldenshtein <victorg@ti.com> |
wlcore: cleanup scan debug prints
Remove scan debug dumps which are rarely used. Make scan debug prints more clear and short.
Signed-off-by: Victor Goldenshtein <victorg@ti.com> Signed-off-by: Elia
wlcore: cleanup scan debug prints
Remove scan debug dumps which are rarely used. Make scan debug prints more clear and short.
Signed-off-by: Victor Goldenshtein <victorg@ti.com> Signed-off-by: Eliad Peller <eliad@wizery.com> Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
show more ...
|
Revision tags: v3.11, v3.11-rc7, v3.11-rc6, v3.11-rc5, v3.11-rc4, v3.11-rc3, v3.11-rc2, v3.11-rc1, v3.10, v3.10-rc7, v3.10-rc6, v3.10-rc5, v3.10-rc4, v3.10-rc3, v3.10-rc2, v3.10-rc1, v3.9, v3.9-rc8, v3.9-rc7, v3.9-rc6, v3.9-rc5, v3.9-rc4, v3.9-rc3 |
|
#
0e752df6 |
| 12-Mar-2013 |
Arik Nemtsov <arik@wizery.com> |
wlcore: AP-mode - recover security seq num for stations
Save the sequence number of the broadcast AP link in the wlvif. For each connected station, save the sequence number in the drv_priv part of i
wlcore: AP-mode - recover security seq num for stations
Save the sequence number of the broadcast AP link in the wlvif. For each connected station, save the sequence number in the drv_priv part of ieee80211_sta. Use the saved numbers on recovery/resume, with the obligatory increment on recovery.
Signed-off-by: Arik Nemtsov <arik@wizery.com> Signed-off-by: Luciano Coelho <coelho@ti.com>
show more ...
|
#
93d5d100 |
| 12-Mar-2013 |
Arik Nemtsov <arik@wizery.com> |
wlcore: consolidate tx_seq handling on recovery
Accumulate the total number of sent packets per-link to find out how far the encryption sequence number has progressed. Use this number as the initial
wlcore: consolidate tx_seq handling on recovery
Accumulate the total number of sent packets per-link to find out how far the encryption sequence number has progressed. Use this number as the initial security sequence number after recovery.
This consolidates security sequence handling for both chip families, as we no longer have to rely on 12xx specific Tx completion.
A fortunate side effect of this is correct management of seq numbers for AP roles and multi-role scenarios.
When a link is removed we save the last seq number on a persistent part of the wlvif. This helps the data survive through recoveries/suspends, which also entail changes in the hlid of the link.
This functionality is STA only currently.
Signed-off-by: Arik Nemtsov <arik@wizery.com> Signed-off-by: Luciano Coelho <coelho@ti.com>
show more ...
|
Revision tags: v3.9-rc2, v3.9-rc1, v3.8, v3.8-rc7 |
|
#
9c3a8d99 |
| 07-Feb-2013 |
Luciano Coelho <coelho@ti.com> |
wlcore: fix wrong remote rates when starting STA role
In wl18xx, we use a new ACX command in order to set the remote supported rates, once we know it (ie. after association). The wl12xx firmware do
wlcore: fix wrong remote rates when starting STA role
In wl18xx, we use a new ACX command in order to set the remote supported rates, once we know it (ie. after association). The wl12xx firmware doesn't support changing the rates after the STA is started, so we need to use all supported rates.
Commit 530abe19 (wlcore: add ACX_PEER_CAP command) broke that by using wlvif->rate_set when starting the STA role.
Signed-off-by: Luciano Coelho <coelho@ti.com>
show more ...
|
Revision tags: v3.8-rc6, v3.8-rc5, v3.8-rc4, v3.8-rc3, v3.8-rc2, v3.8-rc1, v3.7, v3.7-rc8 |
|
#
9a100968 |
| 28-Nov-2012 |
Arik Nemtsov <arik@wizery.com> |
wlcore: use link count for single-STA-PSM optimization
Only allow a PSM STA to congest FW memory when it is the single active link. Being a single STA doesn't imply a single link - there might be ot
wlcore: use link count for single-STA-PSM optimization
Only allow a PSM STA to congest FW memory when it is the single active link. Being a single STA doesn't imply a single link - there might be other links on other roles.
[Changed WARN_ON to WARN_ON_ONCE -- Luca]
Signed-off-by: Arik Nemtsov <arik@wizery.com> Signed-off-by: Luciano Coelho <coelho@ti.com>
show more ...
|
#
530abe19 |
| 28-Nov-2012 |
Eliad Peller <eliad@wizery.com> |
wlcore: add ACX_PEER_CAP command
ACX_PEER_CAP command is just ACX_PEER_HT_CAP, but allows configuring the peer's support rates as well.
this is needed because we start the station role when the rem
wlcore: add ACX_PEER_CAP command
ACX_PEER_CAP command is just ACX_PEER_HT_CAP, but allows configuring the peer's support rates as well.
this is needed because we start the station role when the remote rates are not known yet.
the two commands should be unified in future fw versions, but for now add a new set_peer_cap per-hw op, that will use ACX_PEER_CAP for 18xx, and ACX_PEER_HT_CAP for 12xx.
Signed-off-by: Eliad Peller <eliad@wizery.com> Signed-off-by: Arik Nemtsov <arik@wizery.com> Signed-off-by: Luciano Coelho <coelho@ti.com>
show more ...
|
#
1e0708a9 |
| 27-Nov-2012 |
Arik Nemtsov <arik@wizery.com> |
wlcore: track wlvif inside per-link structure
This allows us to pass only the link as a parameter to various functions and deduce the wlvif. Note that this member will be NULL for global links.
Sig
wlcore: track wlvif inside per-link structure
This allows us to pass only the link as a parameter to various functions and deduce the wlvif. Note that this member will be NULL for global links.
Signed-off-by: Arik Nemtsov <arik@wizery.com> Signed-off-by: Luciano Coelho <coelho@ti.com>
show more ...
|
#
b50a62bb |
| 27-Nov-2012 |
Arik Nemtsov <arik@wizery.com> |
wlcore: initialize per-link FW freed blocks correctly
When a link is allocated, sometimes the "freed packets" counter in FW is non zero, but we always assumed it is. This caused us to incorrectly ac
wlcore: initialize per-link FW freed blocks correctly
When a link is allocated, sometimes the "freed packets" counter in FW is non zero, but we always assumed it is. This caused us to incorrectly account FW allocated blocks in some cases.
When operating in AP mode, this bug caused some stations to never come back from PSM.
Signed-off-by: Arik Nemtsov <arik@wizery.com> Signed-off-by: Luciano Coelho <coelho@ti.com>
show more ...
|