Linux wireless drivers development
 help / color / mirror / Atom feed
From: Lachlan Hodges <lachlan.hodges@morsemicro.com>
To: johannes@sipsolutions.net, Ulf Hansson <ulfh@kernel.org>
Cc: arien.judge@morsemicro.com, dan.callaghan@morsemicro.com,
	ayman.grais@morsemicro.com, linux-wireless@vger.kernel.org,
	Lachlan Hodges <lachlan.hodges@morsemicro.com>,
	linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH wireless-next v3 23/33] mmc: sdio: add Morse Micro vendor ids
Date: Fri, 26 Jun 2026 16:29:19 +1000	[thread overview]
Message-ID: <20260626063014.1275235-24-lachlan.hodges@morsemicro.com> (raw)
In-Reply-To: <20260626063014.1275235-1-lachlan.hodges@morsemicro.com>

Add the Morse Micro mm81x series vendor ids.

Signed-off-by: Lachlan Hodges <lachlan.hodges@morsemicro.com>
---
Hi Ulf, since v2 we've made another slight change to the name removing
a "B2" suffix so even though you acked v2, I suppose it's best to
recollect again - sorry about that. As last time, the patchset is
split once per file following wireless driver submission guidelines,
but will be a pull request with a single patch adding the driver +
sdio ID once review is complete through the wireless tree.
---
 include/linux/mmc/sdio_ids.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/include/linux/mmc/sdio_ids.h b/include/linux/mmc/sdio_ids.h
index 0685dd717e85..bbffad9ae88e 100644
--- a/include/linux/mmc/sdio_ids.h
+++ b/include/linux/mmc/sdio_ids.h
@@ -117,6 +117,9 @@
 #define SDIO_VENDOR_ID_MICROCHIP_WILC		0x0296
 #define SDIO_DEVICE_ID_MICROCHIP_WILC1000	0x5347
 
+#define SDIO_VENDOR_ID_MORSEMICRO		0x325b
+#define SDIO_DEVICE_ID_MORSEMICRO_MM8108	0x0809
+
 #define SDIO_VENDOR_ID_NXP			0x0471
 #define SDIO_DEVICE_ID_NXP_IW61X		0x0205
 
-- 
2.43.0


  parent reply	other threads:[~2026-06-26  6:32 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26  6:28 [PATCH wireless-next v3 00/33] wifi: mm81x: add mm81x driver Lachlan Hodges
2026-06-26  6:28 ` [PATCH wireless-next v3 01/33] wifi: cfg80211: introduce helper to get S1G primary width Lachlan Hodges
2026-06-26  6:28 ` [PATCH wireless-next v3 02/33] wifi: ieee80211: introduce generic KHZ_TO_HZ helper Lachlan Hodges
2026-06-26  6:28 ` [PATCH wireless-next v3 03/33] wifi: mm81x: add bus.h Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 04/33] wifi: mm81x: add command.c Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 05/33] wifi: mm81x: add command_defs.h Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 06/33] wifi: mm81x: add command.h Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 07/33] wifi: mm81x: add core.c Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 08/33] wifi: mm81x: add core.h Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 09/33] wifi: mm81x: add fw.c Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 10/33] wifi: mm81x: add fw.h Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 11/33] wifi: mm81x: add hif.h Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 12/33] wifi: mm81x: add hw.c Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 13/33] wifi: mm81x: add hw.h Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 14/33] wifi: mm81x: add mac.c Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 15/33] wifi: mm81x: add mac.h Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 16/33] wifi: mm81x: add mmrc.c Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 17/33] wifi: mm81x: add mmrc.h Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 18/33] wifi: mm81x: add ps.c Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 19/33] wifi: mm81x: add ps.h Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 20/33] wifi: mm81x: add rate_code.h Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 21/33] wifi: mm81x: add rc.c Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 22/33] wifi: mm81x: add rc.h Lachlan Hodges
2026-06-26  6:29 ` Lachlan Hodges [this message]
2026-06-26  6:29 ` [PATCH wireless-next v3 24/33] wifi: mm81x: add sdio.c Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 25/33] wifi: mm81x: add skbq.c Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 26/33] wifi: mm81x: add skbq.h Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 27/33] wifi: mm81x: add usb.c Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 28/33] wifi: mm81x: add yaps.c Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 29/33] wifi: mm81x: add yaps.h Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 30/33] wifi: mm81x: add yaps_hw.c Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 31/33] wifi: mm81x: add yaps_hw.h Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 32/33] wifi: mm81x: add Kconfig and Makefile Lachlan Hodges
2026-06-26  6:29 ` [PATCH wireless-next v3 33/33] wifi: mm81x: add MAINTAINERS entry Lachlan Hodges
2026-06-29  0:13 ` [PATCH wireless-next v3 00/33] wifi: mm81x: add mm81x driver Lachlan Hodges

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=20260626063014.1275235-24-lachlan.hodges@morsemicro.com \
    --to=lachlan.hodges@morsemicro.com \
    --cc=arien.judge@morsemicro.com \
    --cc=ayman.grais@morsemicro.com \
    --cc=dan.callaghan@morsemicro.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --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