From: Brian Norris <briannorris@chromium.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Kalle Valo <kvalo@kernel.org>,
linux-wireless@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH 2/2] wifi: mwifiex: followup PCIE and related cleanups
Date: Wed, 20 Sep 2023 16:36:09 -0700 [thread overview]
Message-ID: <ZQuB6aEcMGSsmvLs@google.com> (raw)
In-Reply-To: <20230919132804.73340-2-dmantipov@yandex.ru>
On Tue, Sep 19, 2023 at 04:28:00PM +0300, Dmitry Antipov wrote:
> Introduce a few more (PCIE and generic interface related)
> cleanups which becomes reasonable after the previous patch.
>
> Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
> ---
> drivers/net/wireless/marvell/mwifiex/main.h | 4 +--
> drivers/net/wireless/marvell/mwifiex/pcie.c | 28 +++++----------------
> 2 files changed, 8 insertions(+), 24 deletions(-)
...
> --- a/drivers/net/wireless/marvell/mwifiex/pcie.c
> +++ b/drivers/net/wireless/marvell/mwifiex/pcie.c
> @@ -710,18 +710,12 @@ static int mwifiex_pm_wakeup_card_complete(struct mwifiex_adapter *adapter)
> * The host interrupt mask is read, the disable bit is reset and
> * written back to the card host interrupt mask register.
> */
> -static int mwifiex_pcie_disable_host_int(struct mwifiex_adapter *adapter)
> +static void mwifiex_pcie_disable_host_int(struct mwifiex_adapter *adapter)
> {
> if (mwifiex_pcie_ok_to_access_hw(adapter))
> mwifiex_write_reg(adapter, PCIE_HOST_INT_MASK, 0x00000000);
>
> atomic_set(&adapter->tx_hw_pending, 0);
> - return 0;
> }
I have a nagging feeling that some of this is hitting
partially-implemented features (esp. around error handling for the sleep
cookie / mwifiex_pcie_ok_to_access_hw() stuff), but I also bet that the
only chip using that feature (8766) is in bad enough shape that no one
is getting reliable usage out of it anyway. (I know I'm not; ChromeOS
never picked up PCIe support until 8997, where we worked out most of the
driver/firmware bugs.)
So maybe no one cares, and simplifying the dead logic is a net win.
Acked-by: Brian Norris <briannorris@chromium.org>
next prev parent reply other threads:[~2023-09-20 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 13:27 [PATCH 1/2] wifi: mwifiex: simplify PCIE write operations Dmitry Antipov
2023-09-19 13:28 ` [PATCH 2/2] wifi: mwifiex: followup PCIE and related cleanups Dmitry Antipov
2023-09-20 23:36 ` Brian Norris [this message]
2023-09-20 23:31 ` [PATCH 1/2] wifi: mwifiex: simplify PCIE write operations Brian Norris
2023-09-22 7:43 ` Kalle Valo
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=ZQuB6aEcMGSsmvLs@google.com \
--to=briannorris@chromium.org \
--cc=dmantipov@yandex.ru \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lvc-project@linuxtesting.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.