From: "Jonas Dreßler" <verdre@v0yd.nl>
To: Amitkumar Karwar <amitkarwar@gmail.com>,
Ganapathi Bhat <ganapathi017@gmail.com>,
Xinming Hu <huxinming820@gmail.com>,
Kalle Valo <kvalo@codeaurora.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: "Jonas Dreßler" <verdre@v0yd.nl>,
"Tsuchiya Yuto" <kitakar@gmail.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
"Maximilian Luz" <luzmaximilian@gmail.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Pali Rohár" <pali@kernel.org>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Brian Norris" <briannorris@chromium.org>
Subject: [PATCH v2 0/2] mwifiex: Work around firmware bugs on 88W8897 chip
Date: Tue, 14 Sep 2021 13:48:11 +0200 [thread overview]
Message-ID: <20210914114813.15404-1-verdre@v0yd.nl> (raw)
This is the second revision of the patch, the first one is here:
https://lore.kernel.org/linux-wireless/20210830123704.221494-1-verdre@v0yd.nl/
Changes between v1 and v2:
- Only read-back the register write to the TX ring write pointer, not all writes
- Mention firmware version in commit message+code comment for future reference
- Use -EIO return value in second patch
- Use definitions for waiting intervals in second patch
Jonas Dreßler (2):
mwifiex: Use non-posted PCI write when setting TX ring write pointer
mwifiex: Try waking the firmware until we get an interrupt
drivers/net/wireless/marvell/mwifiex/pcie.c | 59 +++++++++++++++++----
1 file changed, 50 insertions(+), 9 deletions(-)
--
2.31.1
next reply other threads:[~2021-09-14 11:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 11:48 Jonas Dreßler [this message]
2021-09-14 11:48 ` [PATCH v2 1/2] mwifiex: Use non-posted PCI write when setting TX ring write pointer Jonas Dreßler
2021-09-22 11:17 ` Andy Shevchenko
2021-09-22 12:08 ` Jonas Dreßler
2021-09-22 13:22 ` Andy Shevchenko
2021-09-22 14:03 ` David Laight
2021-09-22 14:27 ` Pali Rohár
2021-09-22 15:54 ` David Laight
2021-09-30 14:27 ` Jonas Dreßler
2021-10-06 16:01 ` Jonas Dreßler
2021-09-14 11:48 ` [PATCH v2 2/2] mwifiex: Try waking the firmware until we get an interrupt Jonas Dreßler
2021-09-22 11:19 ` Andy Shevchenko
2021-09-30 18:04 ` Jonas Dreßler
2021-09-30 20:58 ` Andy Shevchenko
2021-09-30 21:07 ` Jonas Dreßler
2021-09-30 21:16 ` Andy Shevchenko
2021-10-03 9:18 ` Jonas Dreßler
2021-10-04 17:52 ` Brian Norris
2021-09-27 20:30 ` [PATCH v2 0/2] mwifiex: Work around firmware bugs on 88W8897 chip Brian Norris
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=20210914114813.15404-1-verdre@v0yd.nl \
--to=verdre@v0yd.nl \
--cc=amitkarwar@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=briannorris@chromium.org \
--cc=davem@davemloft.net \
--cc=ganapathi017@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=huxinming820@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kitakar@gmail.com \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pali@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;
as well as URLs for NNTP newsgroup(s).