All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Sai Teja Aluvala <aluvala.sai.teja@intel.com>
Cc: linux-bluetooth@vger.kernel.org, kiran.k@intel.com,
	chethan.tumkur.narayan@intel.com
Subject: Re: [PATCH v3] Bluetooth: btintel_pcie: DBGC flush doorbell and dump rate-limit
Date: Wed, 04 Nov 2026 16:30:08 +0000	[thread overview]
Message-ID: <179380980870.2929236.9750765977869830675.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261104064610.4109582-1-aluvala.sai.teja@intel.com>

Hello:

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

On Wed,  4 Nov 2026 12:16:10 +0530 you wrote:
> DBGC data in SMEM may not be up to date when a dump is collected. Make
> btintel_pcie_coredump() arm USER_TRIGGERED_DUMP and ring the
> IPC_CONTROL.COLLECT_DUMP_REQ doorbell first, so the firmware flushes
> the SMEM contents to DRAM and the dump holds valid data. The resulting
> fwTriggerDump interrupt queues the coredump with
> TRIGGER_REASON_USER_TRIGGER and skips the firmware trigger event, as
> there is none for a host-initiated flush. Firmware-initiated triggers
> emit the diagnostic frame with TRIGGER_REASON_FW_ASSERT, except while a
> doorbell reply is pending, as both raise the same interrupt.
> 
> [...]

Here is the summary with links:
  - [v3] Bluetooth: btintel_pcie: DBGC flush doorbell and dump rate-limit
    https://git.kernel.org/bluetooth/bluetooth-next/c/ed960ec020a7

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



      parent reply	other threads:[~2026-11-04 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04  6:46 [PATCH v3] Bluetooth: btintel_pcie: DBGC flush doorbell and dump rate-limit Sai Teja Aluvala
2026-11-04  8:42 ` [v3] " bluez.test.bot
2026-11-04 16:30 ` 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=179380980870.2929236.9750765977869830675.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=aluvala.sai.teja@intel.com \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=kiran.k@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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.