From: patchwork-bot+bluetooth@kernel.org
To: Ravindra <ravindra@intel.com>
Cc: linux-bluetooth@vger.kernel.org,
chethan.tumkur.narayan@intel.com, kiran.k@intel.com,
pmenzel@molgen.mpg.de
Subject: Re: [PATCH v3] Bluetooth: btintel: read ROM debug registers on FW download failure
Date: Mon, 21 Sep 2026 14:10:08 +0000 [thread overview]
Message-ID: <178999980864.3047822.15306584107639595745.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260921131047.2780402-1-ravindra@intel.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 21 Sep 2026 18:40:47 +0530 you wrote:
> The bootloader records init sequence progress and debug info in four
> core debug registers, useful for debugging FW download failures.
>
> Add btintel_get_rom_debug_info() to issue BTINTEL_GET_ROM_DEBUG_INFO
> (0xfcde) and log these registers, and invoke it from every FW download
> failure and timeout path: btintel_download_fw() (legacy .sfi flow) and
> btintel_prepare_fw_download_tlv() (TLV flow), before resetting to the
> bootloader.
>
> [...]
Here is the summary with links:
- [v3] Bluetooth: btintel: read ROM debug registers on FW download failure
https://git.kernel.org/bluetooth/bluetooth-next/c/06d991977eef
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-09-21 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 13:10 [PATCH v3] Bluetooth: btintel: read ROM debug registers on FW download failure Ravindra
2026-09-21 14:10 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-21 5:48 Ravindra
2026-09-18 8:44 Ravindra
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=178999980864.3047822.15306584107639595745.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=ravindra@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