From: Kalle Valo <kvalo@codeaurora.org>
To: Ramon Fried <rfried@codeaurora.org>
Cc: k.eugene.e@gmail.com, wcn36xx@lists.infradead.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, bjorn.andersson@linaro.org,
nicolas.dechesne@linaro.org, Eyal Ilsar <eilsar@codeaurora.org>
Subject: Re: [PATCH] wcn36xx: Set BTLE coexistence related configuration values to defaults
Date: Tue, 14 Nov 2017 08:54:37 +0200 [thread overview]
Message-ID: <871sl1jqoi.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1510496506-4428-1-git-send-email-rfried@codeaurora.org> (Ramon Fried's message of "Sun, 12 Nov 2017 16:21:46 +0200")
Ramon Fried <rfried@codeaurora.org> writes:
> From: Eyal Ilsar <eilsar@codeaurora.org>
>
> If the value for the firmware configuration parameters
> BTC_STATIC_LEN_LE_BT and BTC_STATIC_LEN_LE_WLAN are not set the duty
> cycle between BT and WLAN is such that if BT (including BLE) is active
> WLAN gets 0 bandwidth. When tuning these parameters having a too high
> value for WLAN means that BLE performance degrades. The "sweet" point
> of roughly half of the maximal values was empirically found to achieve
> a balance between BLE and Wi-Fi coexistence performance.
>
> Signed-off-by: Eyal Ilsar <eilsar@codeaurora.org>
> Signed-off-by: Ramon Fried <rfried@codeaurora.org>
Then submit a new version of the patch then please include the version
number:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#patch_version_missing
So after fixing Bjorn's comments the next version should be v3.
--
Kalle Valo
next prev parent reply other threads:[~2017-11-14 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 14:21 [PATCH] wcn36xx: Set BTLE coexistence related configuration values to defaults Ramon Fried
2017-11-13 18:16 ` Bjorn Andersson
2017-11-14 6:54 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-12 12:48 Ramon Fried
2017-11-12 12:50 ` Kalle Valo
2017-11-12 12:51 ` Kalle Valo
[not found] ` <1510490904-21255-1-git-send-email-rfried-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-11-14 12:48 ` kbuild test robot
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=871sl1jqoi.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=eilsar@codeaurora.org \
--cc=k.eugene.e@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dechesne@linaro.org \
--cc=rfried@codeaurora.org \
--cc=wcn36xx@lists.infradead.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).