From: Kalle Valo <kvalo@codeaurora.org>
To: Ikjoon Jang <ikjn@chromium.org>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, ath10k@lists.infradead.org,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH] ath10k: disable cpuidle during downloading firmware.
Date: Fri, 8 Nov 2019 08:54:11 +0000 (UTC) [thread overview]
Message-ID: <20191108085411.B30B460DA6@smtp.codeaurora.org> (raw)
In-Reply-To: <20191101054035.42101-1-ikjn@chromium.org>
Ikjoon Jang <ikjn@chromium.org> wrote:
> Downloading ath10k firmware needs a large number of IOs and
> cpuidle's miss predictions make it worse. In the worst case,
> resume time can be three times longer than the average on sdio.
>
> This patch disables cpuidle during firmware downloading by
> applying PM_QOS_CPU_DMA_LATENCY in ath10k_download_fw().
>
> Tested-on: QCA9880
> Tested-on: QCA6174 hw3.2 SDIO WLAN.RMH.4.4.1-00029
>
> Signed-off-by: Ikjoon Jang <ikjn@chromium.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
3b58d6a599ba ath10k: disable cpuidle during downloading firmware
--
https://patchwork.kernel.org/patch/11222331/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2019-11-08 8:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 5:40 [PATCH] ath10k: disable cpuidle during downloading firmware Ikjoon Jang
2019-11-01 5:40 ` Ikjoon Jang
2019-11-06 18:22 ` Kalle Valo
2019-11-06 18:22 ` Kalle Valo
2019-11-06 18:33 ` Tom Psyborg
2019-11-06 18:33 ` Tom Psyborg
2019-11-08 8:31 ` Kalle Valo
2019-11-08 8:31 ` Kalle Valo
2019-11-07 4:16 ` Ikjoon Jang
2019-11-07 4:16 ` Ikjoon Jang
2019-11-08 8:32 ` Kalle Valo
2019-11-08 8:32 ` Kalle Valo
2019-11-08 8:54 ` Kalle Valo [this message]
2019-11-08 8:54 ` 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=20191108085411.B30B460DA6@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=ikjn@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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 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.