public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: David Lin <yu-hao.lin@nxp.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
	Calvin Owens <calvin@wbinvd.org>,
	Brian Norris <briannorris@chromium.org>,
	Kalle Valo <kvalo@kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [EXT] [RFC PATCH 0/4] mwifiex: add support for iw61x
Date: Tue, 3 Sep 2024 09:52:08 +0200	[thread overview]
Message-ID: <ZtbAKPP7tIexefd3@pengutronix.de> (raw)
In-Reply-To: <DU0PR04MB96367FEE321C1F269278EA4DD1932@DU0PR04MB9636.eurprd04.prod.outlook.com>

On Tue, Sep 03, 2024 at 07:35:59AM +0000, David Lin wrote:
> > From: Sascha Hauer <s.hauer@pengutronix.de>
> > Sent: Tuesday, September 3, 2024 3:30 PM
> > To: David Lin <yu-hao.lin@nxp.com>
> > Cc: Francesco Dolcini <francesco@dolcini.it>; Calvin Owens
> > <calvin@wbinvd.org>; Brian Norris <briannorris@chromium.org>; Kalle Valo
> > <kvalo@kernel.org>; linux-wireless@vger.kernel.org;
> > linux-kernel@vger.kernel.org; kernel@pengutronix.de
> > Subject: Re: [EXT] [RFC PATCH 0/4] mwifiex: add support for iw61x
> > 
> > Caution: This is an external email. Please take care when clicking links or
> > opening attachments. When in doubt, report the message using the 'Report
> > this email' button
> > 
> > 
> > On Tue, Sep 03, 2024 at 06:39:15AM +0000, David Lin wrote:
> > > > > > > Not only this code segment. In fact, you did not add VDLL data
> > > > > > > patch support
> > > > > > to sdio.c.
> > > > > > > If you try to add the code and do test, you will know what is
> > > > > > > missing in your
> > > > > > code.
> > > > > >
> > > > > > Could you point me to the code you mean?
> > > > > >
> > > > > > Sascha
> > > > > >
> > > > >
> > > > > I only know the porting VDLL code in nxpwifi.
> > > >
> > > > Yes, and I asked for a pointer to that code, some function name, or
> > > > file/line or whatever, because I looked at the nxpwifi driver and
> > > > don't know what you mean with "VDLL data patch support" in sdio.c.
> > > >
> > > > Sascha
> > > >
> > >
> > > It is better for you to check MXM driver. It is the same as Mwifiex which
> > support all SDIO modes.
> > 
> > Now I am confused. You said:
> > 
> > > In fact, you did not add VDLL data patch support to sdio.c
> > 
> > I was under the assumption that the nxpwifi driver that you specifically posted
> > for the iw61x chipset should contain this code. Isn't that the case?
> > 
> > BTW did you really mean "VDLL data patch" or did you mean "VDLL data
> > path"?
> > 
> 
> Sorry VDLL data path.
> You did not add the code to support this new SDIO data type in your patch.
> 
> Please check MXM driver which supports all SDIO modes.

But why? The nxpwifi driver is much closer to the mwifiex driver and
much better readable, so I would rather pick the missing pieces from
there.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2024-09-03  7:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26  7:26 [RFC PATCH 0/4] mwifiex: add support for iw61x Sascha Hauer
2024-08-26  7:26 ` [PATCH 1/4] wifi: mwifiex: release firmware at remove time Sascha Hauer
2024-08-26  7:26 ` [PATCH 2/4] wifi: mwifiex: handle VDLL Sascha Hauer
2024-08-26  7:26 ` [PATCH 3/4] wifi: mwifiex: wait longer for SDIO card status Sascha Hauer
2024-08-26  7:26 ` [PATCH 4/4] mwifiex: add iw61x support Sascha Hauer
2024-08-26  7:57 ` [EXT] [RFC PATCH 0/4] mwifiex: add support for iw61x David Lin
2024-08-26  8:09   ` Francesco Dolcini
2024-08-26  8:12     ` David Lin
2024-09-02  2:24 ` David Lin
2024-09-02  6:40   ` Sascha Hauer
2024-09-02  6:54     ` David Lin
2024-09-02  7:05       ` David Lin
2024-09-02  7:46       ` Sascha Hauer
2024-09-02  8:00         ` David Lin
2024-09-02 13:11           ` Sascha Hauer
2024-09-03  1:51             ` David Lin
2024-09-03  6:33               ` Sascha Hauer
2024-09-03  6:39                 ` David Lin
2024-09-03  7:29                   ` Sascha Hauer
2024-09-03  7:35                     ` David Lin
2024-09-03  7:52                       ` Sascha Hauer [this message]
2024-09-03  7:57                         ` David Lin
2024-09-03  9:01                           ` Sascha Hauer

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=ZtbAKPP7tIexefd3@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=briannorris@chromium.org \
    --cc=calvin@wbinvd.org \
    --cc=francesco@dolcini.it \
    --cc=kernel@pengutronix.de \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yu-hao.lin@nxp.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