linux-kernel - Re: [PATCH v1] Bluetooth: btnxpuart: Revert baudrate change in nxp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <174371163824.2672071.8887469535332941682.git-patchwork-notify@kernel.org>
Date: Thu, 03 Apr 2025 20:20:38 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Neeraj Sanjay Kale <neeraj.sanjaykale@....com>
Cc: marcel@...tmann.org, luiz.dentz@...il.com,
 linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
 amitkumar.karwar@....com, sherry.sun@....com
Subject: Re: [PATCH v1] Bluetooth: btnxpuart: Revert baudrate change in
 nxp_shutdown

Hello:

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

On Thu,  3 Apr 2025 20:32:23 +0530 you wrote:
> This reverts the change baudrate logic in nxp_shutdown.
> 
> Earlier, when the driver was removed, it restored the controller
> baudrate to fw_init_baudrate, so that on re-loading the driver, things
> work fine.
> 
> However, if the driver was removed while hci0 interface is down, the
> change baudrate vendor command could not be sent by the driver. When the
> driver was re-loaded, host and controller baudrate would be mismatched
> and hci initialization would fail. The only way to recover would be to
> reboot the system.
> 
> [...]

Here is the summary with links:
  - [v1] Bluetooth: btnxpuart: Revert baudrate change in nxp_shutdown
    https://git.kernel.org/bluetooth/bluetooth-next/c/17931d1b6d0c

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