Commit 7e189a12 authored by Luis R. Rodriguez's avatar Luis R. Rodriguez Committed by John W. Linville

mac80211: extend sta kdoc - explain when they are added

Signed-off-by: default avatarLuis R. Rodriguez <lrodriguez@atheros.com>
Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
parent 60fd2b67
...@@ -44,6 +44,15 @@ ...@@ -44,6 +44,15 @@
* When the insertion fails (sta_info_insert()) returns non-zero), the * When the insertion fails (sta_info_insert()) returns non-zero), the
* structure will have been freed by sta_info_insert()! * structure will have been freed by sta_info_insert()!
* *
* sta entries are added by mac80211 when you establish a link with a
* peer. This means different things for the different type of interfaces
* we support. For a regular station this mean we add the AP sta when we
* receive an assocation response from the AP. For IBSS this occurs when
* we receive a probe response or a beacon from target IBSS network. For
* WDS we add the sta for the peer imediately upon device open. When using
* AP mode we add stations for each respective station upon request from
* userspace through nl80211.
*
* Because there are debugfs entries for each station, and adding those * Because there are debugfs entries for each station, and adding those
* must be able to sleep, it is also possible to "pin" a station entry, * must be able to sleep, it is also possible to "pin" a station entry,
* that means it can be removed from the hash table but not be freed. * that means it can be removed from the hash table but not be freed.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment