Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: K@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
	Kiran <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
	chethan.tumkur.narayan@intel.com,
	chandrashekar.devegowda@intel.com
Subject: Re: [PATCH v1 1/2] Bluetooth: btintel_pcie: Add handshake between driver and firmware
Date: Fri, 11 Oct 2024 18:32:29 +0000	[thread overview]
Message-ID: <172867154974.2893426.13679059675627500735.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241001104451.626964-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 Tue,  1 Oct 2024 16:14:50 +0530 you wrote:
> The following handshake mechanism needs be followed after firmware
> download is completed to bring the firmware to running state.
> 
> After firmware fragments of Operational image are downloaded and
> secure sends result of the image succeeds,
> 
> 1. Driver sends HCI Intel reset with boot option #1 to switch FW image.
> 2. FW sends Alive GP[0] MSIx
> 3. Driver enables data path (doorbell 0x460 for RBDs, etc...)
> 4. Driver gets Bootup event from firmware
> 5. Driver performs D0 entry to device (WRITE to IPC_Sleep_Control =0x0)
> 6. FW sends Alive GP[0] MSIx
> 7. Device host interface is fully set for BT protocol stack operation.
> 8. Driver may optionally get debug event with ID 0x97 which can be dropped
> 
> [...]

Here is the summary with links:
  - [v1,1/2] Bluetooth: btintel_pcie: Add handshake between driver and firmware
    https://git.kernel.org/bluetooth/bluetooth-next/c/5ea625845b0f
  - [v1,2/2] Bluetooth: btintel_pcie: Add recovery mechanism
    (no matching commit)

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



  parent reply	other threads:[~2024-10-11 18:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01 10:44 [PATCH v1 1/2] Bluetooth: btintel_pcie: Add handshake between driver and firmware Kiran K
2024-10-01 10:44 ` [PATCH v1 2/2] Bluetooth: btintel_pcie: Add recovery mechanism Kiran K
2024-10-01 14:21   ` Luiz Augusto von Dentz
2024-10-07 14:06     ` K, Kiran
2024-10-01 14:32 ` [PATCH v1 1/2] Bluetooth: btintel_pcie: Add handshake between driver and firmware Luiz Augusto von Dentz
2024-10-07 13:51   ` K, Kiran
2024-10-11 18:32 ` patchwork-bot+bluetooth [this message]
2024-11-11 18:29 ` Bjorn Helgaas
2024-11-12 15:59   ` K, Kiran

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=172867154974.2893426.13679059675627500735.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=K@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox