wifi: mac80211: fix header kernel-doc typos

 * helpers for sanity checking. Drivers must ensure all work added onto the

 * mac80211 workqueue should be cancelled on the driver stop() callback.

 *

 * mac80211 will flushed the workqueue upon interface removal and during

 * mac80211 will flush the workqueue upon interface removal and during

 * suspend.

 *

 * All work performed on the mac80211 workqueue must not acquire the RTNL lock.

 * field to the frame RX timestamp and report the ack TX timestamp in the

 * ieee80211_rx_status struct.

 *

 * Similarly, To report hardware timestamps for Timing Measurement or Fine

 * Similarly, to report hardware timestamps for Timing Measurement or Fine

 * Timing Measurement frame TX, the driver should set the SKB's hwtstamp field

 * to the frame TX timestamp and report the ack RX timestamp in the

 * ieee80211_tx_status struct.

 * The set_key() call for the %SET_KEY command should return 0 if

 * the key is now in use, -%EOPNOTSUPP or -%ENOSPC if it couldn't be

 * added; if you return 0 then hw_key_idx must be assigned to the

 * hardware key index, you are free to use the full u8 range.

 * hardware key index. You are free to use the full u8 range.

 *

 * Note that in the case that the @IEEE80211_HW_SW_CRYPTO_CONTROL flag is

 * set, mac80211 will not automatically fall back to software crypto if

 * When the cmd is %DISABLE_KEY then it must succeed.

 *

 * Note that it is permissible to not decrypt a frame even if a key

 * for it has been uploaded to hardware, the stack will not make any

 * for it has been uploaded to hardware. The stack will not make any

 * decision based on whether a key has been uploaded or not but rather

 * based on the receive flags.

 *

 * The update_tkip_key() call updates the driver with the new phase 1 key.

 * This happens every time the iv16 wraps around (every 65536 packets). The

 * set_key() call will happen only once for each key (unless the AP did

 * rekeying), it will not include a valid phase 1 key. The valid phase 1 key is

 * rekeying); it will not include a valid phase 1 key. The valid phase 1 key is

 * provided by update_tkip_key only. The trigger that makes mac80211 call this

 * handler is software decryption with wrap around of iv16.

 *

 *

 * mac80211 has support for various powersave implementations.

 *

 * First, it can support hardware that handles all powersaving by itself,

 * First, it can support hardware that handles all powersaving by itself;

 * such hardware should simply set the %IEEE80211_HW_SUPPORTS_PS hardware

 * flag. In that case, it will be told about the desired powersave mode

 * with the %IEEE80211_CONF_PS flag depending on the association status.

 * %IEEE80211_HW_PS_NULLFUNC_STACK flags. The hardware is of course still

 * required to pass up beacons. The hardware is still required to handle

 * waking up for multicast traffic; if it cannot the driver must handle that

 * as best as it can, mac80211 is too slow to do that.

 * as best as it can; mac80211 is too slow to do that.

 *

 * Dynamic powersave is an extension to normal powersave in which the

 * hardware stays awake for a user-specified period of time after sending a

 * frame so that reply frames need not be buffered and therefore delayed to

 * the next wakeup. It's compromise of getting good enough latency when

 * the next wakeup. It's a compromise of getting good enough latency when

 * there's data traffic and still saving significantly power in idle

 * periods.

 *

 * Note that change, for the sake of simplification, also includes information

 * elements appearing or disappearing from the beacon.

 *

 * Some hardware supports an "ignore list" instead, just make sure nothing

 * Some hardware supports an "ignore list" instead. Just make sure nothing

 * that was requested is on the ignore list, and include commonly changing

 * information element IDs in the ignore list, for example 11 (BSS load) and

 * the various vendor-assigned IEs with unknown contents (128, 129, 133-136,

 * In addition to these capabilities, hardware should support notifying the

 * host of changes in the beacon RSSI. This is relevant to implement roaming

 * when no traffic is flowing (when traffic is flowing we see the RSSI of

 * the received data packets). This can consist in notifying the host when

 * the received data packets). This can consist of notifying the host when

 * the RSSI changes significantly or when it drops below or rises above

 * configurable thresholds. In the future these thresholds will also be

 * configured by mac80211 (which gets them from userspace) to implement

 * period starts for any reason, @release_buffered_frames is called

 * with the number of frames to be released and which TIDs they are

 * to come from. In this case, the driver is responsible for setting

 * the EOSP (for uAPSD) and MORE_DATA bits in the released frames,

 * to help the @more_data parameter is passed to tell the driver if

 * the EOSP (for uAPSD) and MORE_DATA bits in the released frames.

 * To help the @more_data parameter is passed to tell the driver if

 * there is more data on other TIDs -- the TIDs to release frames

 * from are ignored since mac80211 doesn't know how many frames the

 * buffers for those TIDs contain.

 * Additionally, the driver has to then use these HW queue IDs for the queue

 * management functions (ieee80211_stop_queue() et al.)

 *

 * The driver is free to set up the queue mappings as needed, multiple virtual

 * The driver is free to set up the queue mappings as needed; multiple virtual

 * interfaces may map to the same hardware queues if needed. The setup has to

 * happen during add_interface or change_interface callbacks. For example, a

 * driver supporting station+station and station+AP modes might decide to have

 *

 * This function is used to check whether given txq is allowed to transmit by

 * the airtime scheduler, and can be used by drivers to access the airtime

 * fairness accounting without going using the scheduling order enfored by

 * fairness accounting without using the scheduling order enforced by

 * next_txq().

 *

 * Returns %true if the airtime scheduler thinks the TXQ should be allowed to