Lines Matching full:driver
18 /* Driver wrappers are not supposed to directly touch the internal data
30 * This event needs to be delivered when the driver completes IEEE
35 * more information about the association. If the driver interface gets
54 * the local driver. Additional data is for event processing is
67 * is called. If the driver provides an unsolicited event when the scan
70 * driver, the driver wrapper code is expected to use a registered
83 * EVENT_ASSOC. Alternatively, the driver interface can include
114 * EVENT_PMKID_CANDIDATE can be called whenever the driver has updates
121 * Driver will be notified about successful pre-authentication with
148 * driver interface does not need to generate separate EVENT_ASSOCINFO
155 * If the driver generates WPA/RSN IE, this event data must be
173 * Optional association data from the driver. This data is not
175 * such, should be reported if this is available to the driver
197 * again (without scan request). At this point, the driver is
249 * wpa_supplicant_event - Report a driver event for wpa_supplicant
255 * Driver wrapper code should call this function whenever an event is received
256 * from the driver.
