From: Wen Gong <wgong@codeaurora.org>
To: ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: [PATCH v8 0/4] ath10k: improve throughout of TX of sdio
Date: Thu, 28 Nov 2019 10:30:49 +0000 [thread overview]
Message-ID: <0101016eb1903ac2-41999e13-1592-40a1-8909-f5adf648192f-000000@us-west-2.amazonses.com> (raw)
v8: split out patch "change ATH10K_SDIO_BUS_REQUEST_MAX_NUM from 64 to 1024"
from "disable TX complete indication of htt for sdio". merge patch
"ath10k: clean bundle tx queue of htt tx stop for sdio" into
"add htt TX bundle for sdio"
v7: change a few code style to meet ath10k-check script
v6: remove module parameters disable_tx_comp and alt_data
this is 3 patches of the 7 patches from ath10k: improve throughout of tcp/udp TX/RX of sdio
v5: change ath10k_htc_setup_tx_req to add check bundle_tx
to forbidden init 2 times
v4: add macro ATH10K_HTC_MSG_READY_EXT_ALT_DATA_MASK
v3: change some code style
v2: change some code style
The bottleneck of throughout on sdio chip is the bus bandwidth, to the
patches are all to increase the use ratio of sdio bus.
These patches only affect sdio bus chip, explanation is mentioned in each
patch's commit log.
Wen Gong (4):
ath10k: disable TX complete indication of htt for sdio
ath10k: change ATH10K_SDIO_BUS_REQUEST_MAX_NUM from 64 to 1024
ath10k: add htt TX bundle for sdio
ath10k: enable alt data of TX path for sdio
drivers/net/wireless/ath/ath10k/core.c | 27 +-
drivers/net/wireless/ath/ath10k/core.h | 4 +-
drivers/net/wireless/ath/ath10k/hif.h | 9 +
drivers/net/wireless/ath/ath10k/htc.c | 394 +++++++++++++++++++++--
drivers/net/wireless/ath/ath10k/htc.h | 40 ++-
drivers/net/wireless/ath/ath10k/htt.c | 13 +
drivers/net/wireless/ath/ath10k/htt.h | 17 +-
drivers/net/wireless/ath/ath10k/htt_rx.c | 35 +-
drivers/net/wireless/ath/ath10k/htt_tx.c | 39 ++-
drivers/net/wireless/ath/ath10k/hw.h | 2 +-
drivers/net/wireless/ath/ath10k/sdio.c | 23 ++
drivers/net/wireless/ath/ath10k/sdio.h | 3 +-
12 files changed, 553 insertions(+), 53 deletions(-)
--
2.23.0
reply other threads:[~2019-11-28 10:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0101016eb1903ac2-41999e13-1592-40a1-8909-f5adf648192f-000000@us-west-2.amazonses.com \
--to=wgong@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.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).