On Tue, Aug 22, 2023 at 08:21:52PM +0530, Gokul Sivakumar wrote: > With "TWT_SETUP" control SOCK CMD interface currently available in the > wpa_supplicant, it is currently possible to generate the TWT Setup Action > frame with the desired TWT session params like SP, SI, TWT Setup CMD type, > Flow ID, Trigger/Non-Trigger based, Un-Announced/Announced session types, > etc, without informing the TWT state machine in the low layer. The current TWT implementation in wpa_supplicant is only for testing purposes, so I would like to understand what is the use case for this extension proposed in patch 2..7. I did apply patch 1/7 with some cleanup, but I'm not sure I understand what the functionality in the other patches would be used for and more specifically, why it would need to be in wpa_supplicant. It looks like this set of patches does not add any direct use of this into wpa_supplicant, i.e., this just defines a vendor specific kernel interface and a wpa_supplicant control interface to use that kernel interface. Why does wpa_supplicant need to be involved in that? Couldn't the component that would use the wpa_supplicant control interface use the vendor specific kernel interface directly to simplify this? -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
