From: patchwork-bot+bluetooth@kernel.org
To: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, amitkumar.karwar@nxp.com,
rohit.fule@nxp.com, sherry.sun@nxp.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: btnxpuart: Improve inband Independent Reset handling
Date: Wed, 16 Aug 2023 00:10:27 +0000 [thread overview]
Message-ID: <169214462799.26309.4529557002572252958.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230810135509.835889-1-neeraj.sanjaykale@nxp.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 10 Aug 2023 19:25:09 +0530 you wrote:
> This improves the inband IR command handling for NXP BT chipsets.
> When the IR vendor command is received, the driver injects a HW
> error event, which causes a reset sequence in hci_error_reset().
> The vendor IR command is sent to the controller while hci dev
> is been closed, and FW is re-downloaded when nxp_setup() is
> called during hci_dev_do_open().
> The HCI_SETUP flag is set in nxp_hw_err() to make sure that
> nxp_setup() is been called during hci_dev_do_open().
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: btnxpuart: Improve inband Independent Reset handling
https://git.kernel.org/bluetooth/bluetooth-next/c/db4d87d4a68e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-16 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 13:55 [PATCH v1] Bluetooth: btnxpuart: Improve inband Independent Reset handling Neeraj Sanjay Kale
2023-08-10 14:36 ` [v1] " bluez.test.bot
2023-08-16 0:10 ` patchwork-bot+bluetooth [this message]
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=169214462799.26309.4529557002572252958.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=amitkumar.karwar@nxp.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=neeraj.sanjaykale@nxp.com \
--cc=rohit.fule@nxp.com \
--cc=sherry.sun@nxp.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