On Thu, Jun 24, 2021 at 8:09 PM Kalle Valo <kvalo@xxxxxxxxxxxxxx> wrote: > > Emmanuel Grumbach <emmanuel.grumbach@xxxxxxxxx> writes: > > > iwlmei allows to integrate with the CSME firmware. There are > > flows that are prioprietary for this purpose: > > > > * Get the information the AP, the CSME firmware is connected > > to. This is useful when we need to speed up the connection > > process in case the CSME firmware has an TCP connection > > that must be kept alive across the ownership transition. > > * Forbid roaming, which will happen when the CSME firmware > > wants to tell the user space not disrupt the connection. > > * Request ownership, upon driver boot when the CSME firmware > > owns the device. > > Vendor command requirements are documented here: > > https://wireless.wiki.kernel.org/en/developers/documentation/nl80211#vendor-specific_api > > The commit log is not really answering to those. For example, how a user > would use this? Or is there a user space tool? We intend to send those command from the NetworkManager. I'll write a commit message that explains this better. The gist of it is that the user space will see that the NIC is not owned by the host thanks to the new RFKILL reason that I added. Then, it can ask CSME what AP it is connected to, check if it has the a profile configure for that AP and connect to that same profile. I'll respin. > > -- > https://patchwork.kernel.org/project/linux-wireless/list/ > > https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
