MIME-Version: 1.0
References: <CAA=hcWT_dmKU1Uj4YmJ_rxZ+HsCVOEYJLSH-h3B3qqNhC1xi-g@mail.gmail.com>
 <CAD=FV=V3n95DNXFd4mHpkAAKapCs5UWZXUkw=1vWpfn6oXfouA@mail.gmail.com>
In-Reply-To: <CAD=FV=V3n95DNXFd4mHpkAAKapCs5UWZXUkw=1vWpfn6oXfouA@mail.gmail.com>
From:   Jupiter <jupiter.hce@gmail.com>
Date:   Sat, 20 Nov 2021 11:16:08 +1100
Message-ID: <CAA=hcWS91uL4kRK8r1uJ_2YLXi1ZuB067ACVPTDZKnF53jgrRQ@mail.gmail.com>
Subject: Re: mwifiex reset buggy
To:     Doug Anderson <dianders@chromium.org>
Cc:     linux-wireless <linux-wireless@vger.kernel.org>,
        Amitkumar Karwar <amitkumar.karwar@nxp.com>,
        Ganapathi Bhat <ganapathi.bhat@nxp.com>,
        Brian Norris <briannorris@chromium.org>,
        Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
        Linux MMC List <linux-mmc@vger.kernel.org>,
        Ulf Hansson <ulf.hansson@linaro.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hi Doug,

Thank you for your kindly response.

> I think I blocked most of this stuff out of my mind and it's also been
> over 2 years. ;-) ...but any chance that Bluetooth could somehow be
> involved, too? I seem to remember that things got complicated because
> we could have both functions going at once. I think I advocated for
> keeping it simple and always doing a full unplug / replug of the card
> to reset it, but from notes I guess upstream landed it so you need to
> handle the two cases (just WiFi vs WiFi+BT) in totally different ways.

I think the main issue is many of you tested the mwifiex reset on
Marvell card (or BT?), unfortunately I am using uBlox Lily module
which is a WiFi only no Bluetooth, it is a iMX6ULL custom design, MMC
and SDIO are based on iMX6ULL EVK. I don't think anyone tested mwifiex
reset on that card, to make it worse, I am new to mwifiex, I might be
able to assist with debugging, but certainly not in the position to
contribute to fixing it.

> It looks like there's ongoing discussion going on in
> https://issuetracker.google.com/172214846. Maybe something there would
> be helpful?

I am using mwifiex on kernel upstream v4.19.75, does that include your
fix? Do you have a patch I can add to my Yocto build? Should I make
comments to the discussion at
https://issuetracker.google.com/172214846?

Thank you very much Doug.

- JH