Linux wireless drivers development
 help / color / mirror / Atom feed
From: Andrei Rusu de Castro <arc@empyreal.works>
To: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	Luca Coelho <luciano.coelho@intel.com>,
	Kalle Valo <kvalo@kernel.org>,
	Ayala Beker <ayala.beker@intel.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] wifi: iwlwifi: keep Wi-Fi when Intel AMT powers the host on
Date: Mon, 16 Nov 2026 16:40:47 +0000	[thread overview]
Message-ID: <cover.1794846777.git.arc@empyreal.works> (raw)

With IWLMEI enabled and AMT's wireless enabled, the host can come up
without Wi-Fi after AMT powers it on: CSME is still handing the NIC back
to the host while iwlwifi probes. On an HP ZBook Firefly 14 G10 (AX211,
CSME 16.1) this happened in two ways:

 - the NIC cannot be woken at probe while CSME still drives it, and the
   probe fails with -110 for good (patch 1);
 - ownership moves back to CSME between the end of the probe and the
   op mode's start, which then fails with -EBUSY (patch 2).

In both cases the SAP connection to CSME is up, so the host can take the
NVM from CSME and request the NIC over SAP, as it does when CSME visibly
owns the NIC at probe.

The series applies to iwlwifi-next. IWLMEI depends on BROKEN; it builds
with CONFIG_WERROR only together with [1], and binds only with [2]:

[1] https://lore.kernel.org/r/20261116-iwlmei-nvm-const-0c16d1de@empyreal.works
[2] https://lore.kernel.org/r/20261116-mei-cl-dma-parent-60802f47@empyreal.works

Tested with both patches on that machine. The failure in patch 1 hit four
of six AMT power-ons and resets before it; with it, AMT power-ons came back
on Wi-Fi 36-48 s after Power on. The race in patch 2 was seen once in seven
AMT power-ons with patch 1 applied (after about 20 minutes off) and did not
recur in the three power-ons since (after 0 s, 2 and 33 minutes off), so its
fallback has not yet run on hardware.

Andrei Rusu de Castro (2):
  wifi: iwlwifi: pcie: use the CSME path when the NIC cannot be woken at
    probe
  wifi: iwlwifi: mvm: take the NVM from CSME when it takes the device
    back

 drivers/net/wireless/intel/iwlwifi/mvm/ops.c  | 13 ++++++
 .../net/wireless/intel/iwlwifi/pcie/trans.c   | 40 ++++++++++++++++++-
 2 files changed, 51 insertions(+), 2 deletions(-)

-- 
2.55.0


             reply	other threads:[~2026-11-16 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 16:40 Andrei Rusu de Castro [this message]
2026-11-16 16:41 ` [PATCH 1/2] wifi: iwlwifi: pcie: use the CSME path when the NIC cannot be woken at probe Andrei Rusu de Castro
2026-11-16 16:41 ` [PATCH 2/2] wifi: iwlwifi: mvm: take the NVM from CSME when it takes the device back Andrei Rusu de Castro

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=cover.1794846777.git.arc@empyreal.works \
    --to=arc@empyreal.works \
    --cc=ayala.beker@intel.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@intel.com \
    --cc=miriam.rachel.korenblit@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