Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 9625FC433D2
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PATCH] rtw88: 8822c: config RF table path B before path A
From:   Kalle Valo <kvalo@codeaurora.org>
In-Reply-To: <20200318095224.12940-1-yhchuang@realtek.com>
References: <20200318095224.12940-1-yhchuang@realtek.com>
To:     <yhchuang@realtek.com>
Cc:     <linux-wireless@vger.kernel.org>, <briannorris@chromium.org>
User-Agent: pwcli/0.0.0-git (https://github.com/kvalo/pwcli/) Python/2.7.12
Message-Id: <20200323173415.BE20BC433BA@smtp.codeaurora.org>
Date:   Mon, 23 Mar 2020 17:34:15 +0000 (UTC)
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

<yhchuang@realtek.com> wrote:

> From: Yan-Hsuan Chuang <yhchuang@realtek.com>
> 
> After MAC switched power, the hardware's RF registers will have
> its default value, but the default value for path B is incorrect.
> So, load RF path B first, to decrease the period between MAC on
> and RF path B config.
> 
> By test, if we load path A first, then there's ~300ms that the
> path B is incorrect, it could lead to BT coex's A2DP glitch.
> But if we configure path B first, there will only have ~3ms,
> significantly lower possibility to have A2DP sound glitch.
> 
> Signed-off-by: Yan-Hsuan Chuang <yhchuang@realtek.com>

Patch applied to wireless-drivers-next.git, thanks.

11a64888c79b rtw88: 8822c: config RF table path B before path A

-- 
https://patchwork.kernel.org/patch/11444805/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches