summaryrefslogtreecommitdiffstats
path: root/mm/mlock.c
diff options
context:
space:
mode:
authorAlexander Bondar <alexander.bondar@intel.com>2015-03-01 09:10:00 +0200
committerJohannes Berg <johannes.berg@intel.com>2015-03-03 15:56:06 +0100
commit2ecc3905e6c51f545a44cc621216b5dfd7f94c50 (patch)
tree6df50f49ffd720d3335e48d30d413deacf17c739 /mm/mlock.c
parent5fc7432991a86678b38a2d700edbe8bcd29cc579 (diff)
downloadop-kernel-dev-2ecc3905e6c51f545a44cc621216b5dfd7f94c50.zip
op-kernel-dev-2ecc3905e6c51f545a44cc621216b5dfd7f94c50.tar.gz
mac80211: Update beacon's timing and DTIM count on every beacon
Beacon's timestamp, device system time associated with this beacon and DTIM count parameters are not updated in the associated vif context if the latest beacon's content is identical to the previously received. It make sense to update these changing parameters on every beacon so the driver can get most updated values. This may be necessary, for example, to avoid either beacons' drift effect or device time stamp overrun. IMPORTANT: Three sync_* parameters - sync_ts, sync_device_ts and sync_dtim_count would possibly be out of sync by the time the driver will use them. The synchronized view is currently guaranteed only in certain callbacks. Signed-off-by: Alexander Bondar <alexander.bondar@intel.com> Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'mm/mlock.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud