From: Kalle Valo <kvalo@kernel.org>
To: mhi@lists.linux.dev
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: [PATCH v4 0/3] wifi: ath11k: support firmware-2.bin
Date: Thu, 27 Jul 2023 13:04:27 +0300 [thread overview]
Message-ID: <20230727100430.3603551-1-kvalo@kernel.org> (raw)
From: Kalle Valo <quic_kvalo@quicinc.com>
We need firmware-2.bin support in ath11k so that we can add ath11k specific meta
data to firmware releases, for example feature flags so that ath11k can
automatically detect what features the firmware release supports. Also makes
it easier and more reliable to update the firmware for PCI devices as it's not
possible to mix firmware files, everything will be in one file.
Please review and comment.
v4:
* patch 1: document in struct struct mhi_controller_config::fw_data the
fbc_download requirement (Jeffrey)
v3: https://patchwork.kernel.org/project/linux-wireless/list/?series=752266&state=*&order=date
* patch 1: add "bus: mhi: host: ..." to title
* patch 1: add a comment to mhi_fw_load_handler()
* patch 1: check sbl_size
* patch 3: for smooth backwards compatibility don't print an error "failed to
load firmware-2.bin: -2"
v2: https://patchwork.kernel.org/project/linux-wireless/list/?series=727935&state=*&order=date
* mhi_fw_load_handler(): fold two lines into one
* struct mhi_controller_config: document that fbc_download needs to be set
* run pahole struct mhi_controller_config
v1: https://patchwork.kernel.org/project/linux-wireless/list/?series=710862&state=*&order=date
Anilkumar Kolli (1):
wifi: ath11k: add firmware-2.bin support
Kalle Valo (2):
bus: mhi: host: allow MHI client drivers to provide the firmware via a
pointer
wifi: ath11k: qmi: refactor ath11k_qmi_m3_load()
drivers/bus/mhi/host/boot.c | 34 +++--
drivers/net/wireless/ath/ath11k/Makefile | 3 +-
drivers/net/wireless/ath/ath11k/core.c | 8 ++
drivers/net/wireless/ath/ath11k/core.h | 15 +++
drivers/net/wireless/ath/ath11k/fw.c | 157 +++++++++++++++++++++++
drivers/net/wireless/ath/ath11k/fw.h | 27 ++++
drivers/net/wireless/ath/ath11k/mhi.c | 18 ++-
drivers/net/wireless/ath/ath11k/qmi.c | 54 +++++---
include/linux/mhi.h | 6 +
9 files changed, 289 insertions(+), 33 deletions(-)
create mode 100644 drivers/net/wireless/ath/ath11k/fw.c
create mode 100644 drivers/net/wireless/ath/ath11k/fw.h
base-commit: 9102ee8eaa6d29624ed2068396502ad8545f2ff0
--
2.39.2
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next reply other threads:[~2023-07-27 10:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 10:04 Kalle Valo [this message]
2023-07-27 10:04 ` [PATCH v4 1/3] bus: mhi: host: allow MHI client drivers to provide the firmware via a pointer Kalle Valo
2023-08-01 4:20 ` Jeffrey Hugo
2023-08-02 11:01 ` Manivannan Sadhasivam
2023-08-03 18:31 ` Kalle Valo
2023-08-04 6:40 ` Manivannan Sadhasivam
2023-07-27 10:04 ` [PATCH v4 2/3] wifi: ath11k: qmi: refactor ath11k_qmi_m3_load() Kalle Valo
2023-07-27 16:47 ` Jeff Johnson
2023-10-19 9:53 ` Kalle Valo
2023-10-25 9:54 ` Kalle Valo
2023-07-27 10:04 ` [PATCH v4 3/3] wifi: ath11k: add firmware-2.bin support Kalle Valo
2023-07-27 17:12 ` Jeff Johnson
2023-10-19 13:27 ` Kalle Valo
2023-10-19 15:22 ` Jeff Johnson
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=20230727100430.3603551-1-kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mhi@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).