Linux wireless drivers development
 help / color / mirror / Atom feed
From: Jeff Chen <chunfan.chen@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: johannes@sipsolutions.net, francesco@dolcini.it,
	linux-mmc@vger.kernel.org, Ulf Hansson <ulfh@kernel.org>,
	Jeff Chen <jeff.chen_1@nxp.com>
Subject: [PATCH wireless-next 0/4] wifi: nxpwifi: add support for SDIO IW610
Date: Tue,  8 Sep 2026 17:37:54 +0800	[thread overview]
Message-ID: <20260908093758.596444-1-chunfan.chen@gmail.com> (raw)

From: Jeff Chen <jeff.chen_1@nxp.com>

This series adds support for the NXP SDIO IW610 to the nxpwifi driver.

IW610 uses different SDIO device IDs and a different firmware image
from the existing IW61x devices. It shares the same SDIO register
layout, so most of the existing SDIO support can be reused.

The first two patches update the MMC subsystem. They add the SDIO IDs
needed by IW610 and apply the required
MMC_QUIRK_BLKSZ_FOR_BYTE_MODE quirk. The last two patches add SDIO
IW610 support to nxpwifi and limit channel width requests based on
firmware capabilities.

Ulf, could you please Ack patches 1 and 2? 

  [1/4] mmc: sdio: add NXP IW610 device ID
        Add SDIO device ID 0x0215 for IW610.

  [2/4] mmc: core: add IW610 base ID and block-size quirk
        Add base card ID 0x0214 and apply
        MMC_QUIRK_BLKSZ_FOR_BYTE_MODE.

  [3/4] wifi: nxpwifi: add support for SDIO IW610
        Add the IW610 device descriptor and firmware name.

  [4/4] wifi: nxpwifi: restrict channel width on 20 MHz-only hardware
        Do not request 40 MHz or 80 MHz operation when the firmware
        does not support it.

Tested on:
  - NXP i.MX93 EVK running the NXP BSP kernel
  - Lenovo ThinkPad T430 running current wireless-next

Jeff Chen (4):
  mmc: sdio: add NXP IW610 device ID
  mmc: core: add NXP IW610 base ID and block size quirk
  wifi: nxpwifi: Add support for SDIO-based IW610
  wifi: nxpwifi: Limit channel width based on firmware capability

 drivers/mmc/core/quirks.h               |  3 +++
 drivers/net/wireless/nxp/nxpwifi/11n.c  |  4 +++-
 drivers/net/wireless/nxp/nxpwifi/fw.h   |  2 ++
 drivers/net/wireless/nxp/nxpwifi/sdio.c | 16 ++++++++++++++++
 drivers/net/wireless/nxp/nxpwifi/sdio.h |  1 +
 include/linux/mmc/sdio_ids.h            |  2 ++
 6 files changed, 27 insertions(+), 1 deletion(-)


base-commit: 1b60ed34f712e9f606d80951f1586f4274ebadf1
-- 
2.34.1


             reply	other threads:[~2026-09-08  9:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08  9:37 Jeff Chen [this message]
2026-09-08  9:37 ` [PATCH wireless-next 1/4] mmc: sdio: add NXP IW610 device ID Jeff Chen
2026-09-11 15:28   ` Ulf Hansson
2026-09-08  9:37 ` [PATCH wireless-next 2/4] mmc: core: add NXP IW610 base ID and block size quirk Jeff Chen
2026-09-11 15:28   ` Ulf Hansson
2026-09-08  9:37 ` [PATCH wireless-next 3/4] wifi: nxpwifi: Add support for SDIO-based IW610 Jeff Chen
2026-09-08  9:37 ` [PATCH wireless-next 4/4] wifi: nxpwifi: Limit channel width based on firmware capability Jeff Chen

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=20260908093758.596444-1-chunfan.chen@gmail.com \
    --to=chunfan.chen@gmail.com \
    --cc=francesco@dolcini.it \
    --cc=jeff.chen_1@nxp.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ulfh@kernel.org \
    /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