From: Kalle Valo <kvalo@codeaurora.org>
To: Chris Chiu <chiu@endlessm.com>
Cc: Jes.Sorensen@gmail.com, davem@davemloft.net,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@endlessm.com
Subject: Re: [PATCH] rtl8xxxu: fix RTL8723BU connection failure issue after warm reboot
Date: Tue, 15 Oct 2019 14:36:41 +0300 [thread overview]
Message-ID: <874l0ansty.fsf@codeaurora.org> (raw)
In-Reply-To: <20191015102109.4701-1-chiu@endlessm.com> (Chris Chiu's message of "Tue, 15 Oct 2019 18:21:09 +0800")
Chris Chiu <chiu@endlessm.com> writes:
> The RTL8723BU has problems connecting to AP after each warm reboot.
> Sometimes it returns no scan result, and in most cases, it fails
> the authentication for unknown reason. However, it works totally
> fine after cold reboot.
>
> Compare the value of register SYS_CR and SYS_CLK_MAC_CLK_ENABLE
> for cold reboot and warm reboot, the registers imply that the MAC
> is already powered and thus some procedures are skipped during
> driver initialization. Double checked the vendor driver, it reads
> the SYS_CR and SYS_CLK_MAC_CLK_ENABLE also but doesn't skip any
> during initialization based on them. This commit only tells the
> RTL8723BU to do full initialization without checking MAC status.
>
> https://phabricator.endlessm.com/T28000
>
> Signed-off-by: Chris Chiu <chiu@endlessm.com>
If you send a new version of patch mark it as v2 and include a
changelog:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#patch_version_missing
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#changelog_missing
--
Kalle Valo
next prev parent reply other threads:[~2019-10-15 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 10:21 [PATCH] rtl8xxxu: fix RTL8723BU connection failure issue after warm reboot Chris Chiu
2019-10-15 11:36 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-15 10:19 Chris Chiu
2019-10-15 17:47 ` Jes Sorensen
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=874l0ansty.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Jes.Sorensen@gmail.com \
--cc=chiu@endlessm.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@endlessm.com \
--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.