Lines Matching full:fw
9 #include "fw-api.h"
16 * Time Events are a fw feature that allows the driver to control the presence
17 * of the device on the channel. Since the fw supports multiple channels
18 * concurrently, the fw may choose to jump to another channel at any time.
19 * In order to make sure that the fw is on a specific channel at a certain time
25 * smoothly and won't be interrupted by channel switch decided within the fw.
29 * DOC: The flow against the fw
33 * fw goes like this:
34 * 1) Driver sends a TIME_EVENT_CMD to the fw
37 * 3) The fw sends notification when the event starts.
73 * fw will stay on the channel for %duration_ms milliseconds. This function
77 * want to make sure that the fw stays on the channel during the association.
116 * @duration: the requested duration in millisecond for the fw to be on the
121 * which means that the fw will stay in the channel for the request %duration
123 * request but does not wait for it to start. Once the FW is ready to serve the
125 * requested channel. Once the FW completes the ROC request it will issue
137 * The function is async, it will instruct the FW to stop serving the ROC
188 * iwl_mvm_te_scheduled - check if the fw received the TE cmd
191 * This function returns true iff this TE is added to the fw.