From: "Pali Rohár" <pali@kernel.org>
To: "Ganapathi Bhat" <ganapathi.bhat@nxp.com>,
"Amitkumar Karwar" <amitkarwar@gmail.com>,
"Xinming Hu" <huxinming820@gmail.com>,
"Kalle Valo" <kvalo@codeaurora.org>,
"Marek Behún" <marek.behun@nic.cz>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org,
Hemantkumar Suthar <shemant@marvell.com>,
Rakesh Parmar <rakeshp@marvell.com>,
Zhaoyang Liu <liuzy@marvell.com>, Cathy Luo <cluo@marvell.com>
Subject: [PATCH 0/4] marvell: Fix firmware filenames for sd8977/sd8997 chipsets
Date: Wed, 3 Jun 2020 10:22:25 +0200 [thread overview]
Message-ID: <20200603082229.15043-1-pali@kernel.org> (raw)
This patch series fixes mwifiex and btmrvl drivers to load firmware for sd8977
and sd8997 chipsets from correct filename.
Both Marvell distribution package and linux-firmware repository [1] contain
firmware for these chipsets in files sdsd8977_combo_v2.bin/sdsd8997_combo_v4.bin.
Linux drivers mwifiex and btmrvl try to load firmware for these chipsets from
sd8977_uapsta.bin/sd8997_uapsta.bin files which obviously fails as these files
do not exist neither in linux-firmware [1] nor in Marvell distribution packages.
So the result is that Marvell sd8977 and sd8997 chipsets via mainline kernel
drivers (mwifiex and btmrvl) do not work out of box.
Each patch in this series fixes particular git commit which introduced usage
of incorrect firmware filename. Also each patch contains Fixes: line for easier
backporting to stable kernels.
mwifiex (1/4, 2/4) and btmrvl (3/4, 4/4) parts of this patch series can be
applied separately via wireless and bluetooth trees. I'm sending all four
patches in one patch series for easier review.
[1] - https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/mrvl
Pali Rohár (4):
mwifiex: Fix firmware filename for sd8977 chipset
mwifiex: Fix firmware filename for sd8997 chipset
btmrvl: Fix firmware filename for sd8977 chipset
btmrvl: Fix firmware filename for sd8997 chipset
drivers/bluetooth/btmrvl_sdio.c | 8 ++++----
drivers/net/wireless/marvell/mwifiex/sdio.h | 4 ++--
2 files changed, 6 insertions(+), 6 deletions(-)
--
2.20.1
next reply other threads:[~2020-06-03 8:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 8:22 Pali Rohár [this message]
2020-06-03 8:22 ` [PATCH 1/4] mwifiex: Fix firmware filename for sd8977 chipset Pali Rohár
2020-06-03 9:18 ` [EXT] " Ganapathi Bhat
2020-06-03 8:22 ` [PATCH 2/4] mwifiex: Fix firmware filename for sd8997 chipset Pali Rohár
2020-06-03 9:18 ` [EXT] " Ganapathi Bhat
2020-06-03 8:22 ` [PATCH 3/4] btmrvl: Fix firmware filename for sd8977 chipset Pali Rohár
2020-06-03 9:19 ` [EXT] " Ganapathi Bhat
2020-06-03 8:22 ` [PATCH 4/4] btmrvl: Fix firmware filename for sd8997 chipset Pali Rohár
2020-06-03 9:19 ` [EXT] " Ganapathi Bhat
2020-06-03 9:17 ` [EXT] [PATCH 0/4] marvell: Fix firmware filenames for sd8977/sd8997 chipsets Ganapathi Bhat
2020-06-03 17:47 ` Marcel Holtmann
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=20200603082229.15043-1-pali@kernel.org \
--to=pali@kernel.org \
--cc=amitkarwar@gmail.com \
--cc=cluo@marvell.com \
--cc=ganapathi.bhat@nxp.com \
--cc=huxinming820@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=liuzy@marvell.com \
--cc=marek.behun@nic.cz \
--cc=rakeshp@marvell.com \
--cc=shemant@marvell.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;
as well as URLs for NNTP newsgroup(s).