From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
"Coelho, Luciano" <luciano.coelho@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Ayala Beker <ayala.beker@intel.com>
Subject: Re: [PATCH v3 3/4] nl80211: vendor-cmd: add Intel vendor commands for iwlmei usage
Date: Thu, 24 Jun 2021 22:56:49 +0300 [thread overview]
Message-ID: <CANUX_P0d0jrq9x99jM824oKOhmi0Wa5WqhECMsX=hd269H6atw@mail.gmail.com> (raw)
In-Reply-To: <87k0mji43p.fsf@codeaurora.org>
On Thu, Jun 24, 2021 at 8:09 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>
> Emmanuel Grumbach <emmanuel.grumbach@intel.com> 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
next prev parent reply other threads:[~2021-06-24 19:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 14:10 [PATCH v3 1/4] iwlwifi: mei: add the driver to allow cooperation with CSME Emmanuel Grumbach
2021-06-23 14:10 ` [PATCH v3 2/4] iwlwifi: integrate with iwlmei Emmanuel Grumbach
2021-06-23 14:10 ` [PATCH v3 3/4] nl80211: vendor-cmd: add Intel vendor commands for iwlmei usage Emmanuel Grumbach
2021-06-24 12:45 ` Johannes Berg
2021-06-24 12:51 ` Emmanuel Grumbach
2021-06-24 17:07 ` Kalle Valo
2021-06-24 19:56 ` Emmanuel Grumbach [this message]
2021-08-05 13:25 ` Kalle Valo
2021-08-07 18:32 ` Grumbach, Emmanuel
2021-10-18 11:25 ` Kalle Valo
2021-06-23 14:10 ` [PATCH v3 4/4] iwlwifi: mvm: add vendor commands needed for iwlmei Emmanuel Grumbach
2021-06-24 17:08 ` Kalle Valo
2021-06-24 19:59 ` Emmanuel Grumbach
2021-08-05 13:35 ` Kalle Valo
2021-08-07 18:34 ` Grumbach, Emmanuel
2021-10-18 11:27 ` Kalle Valo
2021-06-24 17:16 ` [PATCH v3 1/4] iwlwifi: mei: add the driver to allow cooperation with CSME Kalle Valo
2021-06-24 20:04 ` Emmanuel Grumbach
2021-08-05 13:38 ` Kalle Valo
2021-08-07 18:38 ` Grumbach, Emmanuel
2021-08-09 7:49 ` Arend van Spriel
2021-08-09 19:25 ` Grumbach, Emmanuel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANUX_P0d0jrq9x99jM824oKOhmi0Wa5WqhECMsX=hd269H6atw@mail.gmail.com' \
--to=egrumbach@gmail.com \
--cc=ayala.beker@intel.com \
--cc=emmanuel.grumbach@intel.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).