From: Kalle Valo <kvalo@codeaurora.org>
To: <yhchuang@realtek.com>
Cc: <linux-wireless@vger.kernel.org>, <pkshih@realtek.com>,
<kai.heng.feng@canonical.com>, <bigeasy@linutronix.de>,
<vicamo.yang@canonical.com>
Subject: Re: [PATCH v2 1/3] rtw88: coex: 8723d: set antanna control owner
Date: Fri, 29 May 2020 17:36:33 +0000 (UTC) [thread overview]
Message-ID: <20200529173634.0409EC433CB@smtp.codeaurora.org> (raw)
In-Reply-To: <20200529025009.2468-2-yhchuang@realtek.com>
<yhchuang@realtek.com> wrote:
> From: Ping-Ke Shih <pkshih@realtek.com>
>
> Without setting antenna control owner, the WiFi could be disconnected if
> the BT has traffic. Because the antenna is switched to BT side for its
> traffic, and the WiFi will have no chance to transfer data. Set control
> owner to prevent WiFi disconnect issue.
>
> Fixes: f5df1a8b4376 ("rtw88: 8723d: Add 8723DE to Kconfig and Makefile")
> Tested-by: You-Sheng Yang <vicamo.yang@canonical.com>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
> Signed-off-by: Yan-Hsuan Chuang <yhchuang@realtek.com>
3 patches applied to wireless-drivers-next.git, thanks.
efad661168c7 rtw88: coex: 8723d: set antanna control owner
2647d2827f2a rtw88: coex: 8723d: handle BT inquiry cases
7a242fb69821 rtw88: fix EAPOL 4-way failure by finish IQK earlier
--
https://patchwork.kernel.org/patch/11577459/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-05-29 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 2:50 [PATCH v2 0/3] rtw88: 8723d: follow up fixes yhchuang
2020-05-29 2:50 ` [PATCH v2 1/3] rtw88: coex: 8723d: set antanna control owner yhchuang
2020-05-29 17:36 ` Kalle Valo [this message]
2020-05-29 2:50 ` [PATCH v2 2/3] rtw88: coex: 8723d: handle BT inquiry cases yhchuang
2020-05-29 2:50 ` [PATCH v2 3/3] rtw88: fix EAPOL 4-way failure by finish IQK earlier yhchuang
2020-05-29 7:18 ` [PATCH v2 0/3] rtw88: 8723d: follow up fixes Sebastian Andrzej Siewior
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=20200529173634.0409EC433CB@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=bigeasy@linutronix.de \
--cc=kai.heng.feng@canonical.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=vicamo.yang@canonical.com \
--cc=yhchuang@realtek.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).