From: "Ivan T. Ivanov" <iivanov@suse.de>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
Jeff Chen <jeff.chen_1@nxp.com>,
Pete Hsieh <tsung-hsien.hsieh@nxp.com>,
Brian Norris <briannorris@chromium.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH do not merge 0/4] wifi: mwifiex: add iw61x support
Date: Tue, 29 Apr 2025 15:59:28 +0300 [thread overview]
Message-ID: <20250429125928.pw7k4raw52jyvyaj@localhost.localdomain> (raw)
In-Reply-To: <20250331065026.GA12444@francesco-nb>
Hi,
On 03-31 08:50, Francesco Dolcini wrote:
> Message-ID: <20250331065026.GA12444@francesco-nb>
>
> +Pete/Jesse @NXP
>
> On Wed, Mar 26, 2025 at 01:18:30PM +0100, Sascha Hauer wrote:
> > This series adds iw61x support to the mwifiex driver. It works for me,
> > but is not yet ready to be merged. Some people showed interest in it, so
> > I am sending it here.
> >
> > All testing and review feedback appreciated.
> >
> > During startup I get these messages:
> >
> > [ 12.078010] mwifiex_sdio mmc1:0001:1: Unknown GET_HW_SPEC TLV type: 0xff
> > [ 12.078018] mwifiex_sdio mmc1:0001:1: Unknown GET_HW_SPEC TLV type: 0xff
> > [ 12.078024] mwifiex_sdio mmc1:0001:1: Unknown GET_HW_SPEC TLV type: 0x23e
In the downstream driver, branch lf-6.12.3_1.0.0, t his seems to be
MrvlIEtypes_fw_cap_info_t for things like:
FW_CAPINFO_EXT_802_11AX, FW_CAPINFO_EXT_6G ....
> > [ 12.078029] mwifiex_sdio mmc1:0001:1: Unknown GET_HW_SPEC TLV type: 0x25c
> >
This looks like MrvlIEtypes_Secure_Boot_Uuid_t. Doesn't seems too
important.
> > Not sure what these are about, I can't see these handled in the
> > downstream mwifiex driver as well. Could also be there is some parsing
> > error. Nevertheless the driver seems to work.
Yep, it is working. Thank you! I am testing this on FRDM-iMX93, which has
IW612 revision 1.0.
I have to use nxp/sd_w61x_v1.bin.se on this board and NULL firmware_sdiouart
because it seems that firmware return 1 as "strap" value, even if WiFi
is definitely connected over SDIO.
Regards,
Ivan
next prev parent reply other threads:[~2025-04-29 12:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 12:18 [PATCH do not merge 0/4] wifi: mwifiex: add iw61x support Sascha Hauer
2025-03-26 12:18 ` [PATCH do not merge 1/4] wifi: mwifiex: release firmware at remove time Sascha Hauer
2025-03-26 12:18 ` [PATCH do not merge 2/4] wifi: mwifiex: handle VDLL Sascha Hauer
2025-04-18 8:12 ` [EXT] " Jeff Chen
2025-03-26 12:18 ` [PATCH do not merge 3/4] wifi: mwifiex: wait longer for SDIO card status Sascha Hauer
2025-03-26 12:18 ` [PATCH do not merge 4/4] wifi: mwifiex: add iw61x support Sascha Hauer
2025-03-26 12:23 ` Francesco Dolcini
2025-03-26 13:54 ` Sascha Hauer
2025-03-27 9:33 ` Francesco Dolcini
2025-03-28 15:10 ` Sascha Hauer
2025-04-29 8:25 ` Ivan T. Ivanov
2025-03-28 15:05 ` Ernest Van Hoecke
2025-03-31 6:50 ` [PATCH do not merge 0/4] " Francesco Dolcini
2025-04-29 12:59 ` Ivan T. Ivanov [this message]
2025-05-05 7:32 ` Francesco Dolcini
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=20250429125928.pw7k4raw52jyvyaj@localhost.localdomain \
--to=iivanov@suse.de \
--cc=briannorris@chromium.org \
--cc=francesco@dolcini.it \
--cc=jeff.chen_1@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=tsung-hsien.hsieh@nxp.com \
--cc=ulf.hansson@linaro.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