From: patchwork-bot+bluetooth@kernel.org
To: Kiran K <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
chethan.tumkur.narayan@intel.com,
chandrashekar.devegowda@intel.com, aluvala.sai.teja@intel.com
Subject: Re: [PATCH v3 1/2] Bluetooth: btintel_pcie: Make driver wait for alive interrupt
Date: Mon, 21 Jul 2025 13:40:07 +0000 [thread overview]
Message-ID: <175310520782.52701.10009254792730458350.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250721094437.1163753-1-kiran.k@intel.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 21 Jul 2025 15:14:36 +0530 you wrote:
> The firmware raises an alive interrupt upon receiving the HCI_RESET or
> BTINTEL_HCI_OP_RESET (Intel reset - 0xfc01) command. This change fixes
> the driver to properly wait for the alive interrupt to avoid driver
> sending commands to firmware before it is ready to process.
>
> For details on the handshake between the driver and firmware, refer to
> commit 05c200c8f029 ("Bluetooth: btintel_pcie: Add handshake between
> driver and firmware").
>
> [...]
Here is the summary with links:
- [v3,1/2] Bluetooth: btintel_pcie: Make driver wait for alive interrupt
https://git.kernel.org/bluetooth/bluetooth-next/c/3bf15df70a10
- [v3,2/2] Bluetooth: btintel_pcie: Fix Alive Context State Handling
https://git.kernel.org/bluetooth/bluetooth-next/c/b4e417d5d32c
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:[~2025-07-21 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 9:44 [PATCH v3 1/2] Bluetooth: btintel_pcie: Make driver wait for alive interrupt Kiran K
2025-07-21 9:44 ` [PATCH v3 2/2] Bluetooth: btintel_pcie: Fix Alive Context State Handling Kiran K
2025-07-21 10:10 ` [v3,1/2] Bluetooth: btintel_pcie: Make driver wait for alive interrupt bluez.test.bot
2025-07-21 13:40 ` 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=175310520782.52701.10009254792730458350.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=aluvala.sai.teja@intel.com \
--cc=chandrashekar.devegowda@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ravishankar.srivatsa@intel.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 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.