diff options
| author |   Amitkumar Karwar <akarwar@marvell.com> | 2012-04-16 21:36:52 -0700 |
|---|---|---|
| committer |   John W. Linville <linville@tuxdriver.com> | 2012-04-17 14:57:15 -0400 |
| commit | b5abcf0219263f4e961dca71cbe26e06c5b0ee68 (patch) | |
| tree | 8e8898fd6b41a13a24098b762d2f2be8a50869c0 /net/wireless | |
| parent | mwifiex: code cleanup in BSS handling (diff) | |
| download | linux-dev-b5abcf0219263f4e961dca71cbe26e06c5b0ee68.tar.xz linux-dev-b5abcf0219263f4e961dca71cbe26e06c5b0ee68.zip | |
mwifiex: corrections in timestamp related code
We get two timing related fields for each bss from firmware in scan
results.
1) timestamp - Actual timestamp information in probe response/beacon
2) network_tsf - firmware's TSF value at the time the beacon or probe
response was received.
Both are needed while associating by firmware.
The patch takes care of following things.
1) We should pass "timestamp" to cfg80211_inform_bss(), but currently
"network_tsf" is being provided. This error is corrected here.
2) Rename "network_tsf" to "fw_tsf"
3) Make use of u64 variable instead of an array of u8/u32 to save
parsed "timestamp" information.
4) Use timestamp provided to stack in scan results using
cfg80211_inform_bss() while associating. (bss->tsf)
5) Allocate space to save fw_tsf in "priv" of cfg80211_bss
and retrieve it while associating.
Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
Signed-off-by: Bing Zhao <bzhao@marvell.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'net/wireless')
0 files changed, 0 insertions, 0 deletions