Lines Matching full:time

71  * DOC: Time Events - what is it?
73  * Time Events are a fw feature that allows the driver to control the presence
75  * concurrently, the fw may choose to jump to another channel at any time.
76  * In order to make sure that the fw is on a specific channel at a certain time
77  * and for a certain duration, the driver needs to issue a time event.
79  * The simplest example is for BSS association. The driver issues a time event,
89  * time and for a certain duration, it sends a Time Event. The flow against the
99  *	What is the start time of the event?
100  *	Is there an end-time for the event?
110  * In order to simplify the use of time events to the rest of the driver,
111  * we abstract the use of time events. This component provides the functions
125  * @max_delay: maximum delay before starting the time event (in TU)
126  * @wait_for_notif: true if it is required that a time event notification be
127  *	waited for (that the time event has been scheduled before returning)
148  * the other bindings wait for the medium during that time.
192  * iwl_mvm_remove_time_event - general function to clean up of time event
194  * @vif: the vif to which the time event belongs
195  * @te_data: the time event data that corresponds to that time event
197  * This function can be used to cancel a time event regardless its type.
198  * It is useful for cleaning up time events running before removing an
206  * iwl_mvm_te_clear_data - remove time event from list
208  * @te_data: the time event data to remove
227  * @apply_time: NoA start time in GP2.
229  * This function is used to schedule NoA time event and is used to perform
238  * @te_data: the time event data that corresponds to that time event