The opmode change notification is entirely unused by existing userspace except for printing out the values. As such, there's no need to keep it perfectly accurate, and the implementation in mac80211 doesn't report it correctly today. Add a note in the documentation that it may not differentiate 80+80 and 160.
Unified · Split
| @@ -1204,10 +1204,12 @@ · 1203 unmodified lines | |||
| 1204 | * user space through the connect result as the user space would have | 1204 | * user space through the connect result as the user space would have |
| 1205 | * initiated the connection through the connect request. | 1205 | * initiated the connection through the connect request. |
| 1206 | * | 1206 | * |
| 1207 | * @NL80211_CMD_STA_OPMODE_CHANGED: An event that notify station's | 1207 | * @NL80211_CMD_STA_OPMODE_CHANGED: An event that notifies that a station's |
| 1208 | * ht opmode or vht opmode changes using any of %NL80211_ATTR_SMPS_MODE, | 1208 | * HT opmode or VHT opmode changed using any of %NL80211_ATTR_SMPS_MODE, |
| 1209 | * %NL80211_ATTR_CHANNEL_WIDTH,%NL80211_ATTR_NSS attributes with its | 1209 | * %NL80211_ATTR_CHANNEL_WIDTH, %NL80211_ATTR_NSS attributes with its |
| 1210 | * address(specified in %NL80211_ATTR_MAC). | 1210 | * address (specified in %NL80211_ATTR_MAC). |
| 1211 | * Note that 80+80 and 160 MHz might not be differentiated, i.e. may | ||
| 1212 | * report %NL80211_CHAN_WIDTH_160 instead of %NL80211_CHAN_WIDTH_80P80. | ||
| 1211 | * | 1213 | * |
| 1212 | * @NL80211_CMD_GET_FTM_RESPONDER_STATS: Retrieve FTM responder statistics, in | 1214 | * @NL80211_CMD_GET_FTM_RESPONDER_STATS: Retrieve FTM responder statistics, in |
| 1213 | * the %NL80211_ATTR_FTM_RESPONDER_STATS attribute. | 1215 | * the %NL80211_ATTR_FTM_RESPONDER_STATS attribute. |