Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v2] Bluetooth: btnxpuart: Enable flow control before checking
 boot signature
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <168202442062.11865.1139590238714814236.git-patchwork-notify@kernel.org>
Date:   Thu, 20 Apr 2023 21:00:20 +0000
References: <20230419152413.1688840-1-neeraj.sanjaykale@nxp.com>
In-Reply-To: <20230419152413.1688840-1-neeraj.sanjaykale@nxp.com>
To:     Neeraj sanjay kale <neeraj.sanjaykale@nxp.com>
Cc:     marcel@holtmann.org, johan.hedberg@gmail.com, luiz.dentz@gmail.com,
        pmenzel@molgen.mpg.de, linux-kernel@vger.kernel.org,
        linux-bluetooth@vger.kernel.org, amitkumar.karwar@nxp.com,
        rohit.fule@nxp.com, sherry.sun@nxp.com
Precedence: bulk

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Wed, 19 Apr 2023 20:54:13 +0530 you wrote:
> This enables flow control before checking for bootloader signature and
> deciding whether FW download is needed or not. In case of V1 bootloader
> chips w8987 and w8997, it is observed that if WLAN FW is downloaded first
> and power save is enabled in wlan core, bootloader signatures are not
> emitted by the BT core when the chip is put to sleep. As a result, the
> driver skips FW download and subsequent HCI commands get timeout errors
> in dmesg as shown below:
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: btnxpuart: Enable flow control before checking boot signature
    https://git.kernel.org/bluetooth/bluetooth-next/c/4b1f1ab59be1

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html