From: patchwork-bot+bluetooth@kernel.org
To: Chris Lu <chris.lu@mediatek.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, sean.wang@mediatek.com,
will-cy.Lee@mediatek.com, ss.wu@mediatek.com,
steve.lee@mediatek.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v1 0/3] Trigger reset if firmware status is abnormal when
Date: Wed, 11 Feb 2026 19:40:09 +0000 [thread overview]
Message-ID: <177083880957.688115.17676708288116358310.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260203062510.848761-1-chris.lu@mediatek.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 3 Feb 2026 14:25:07 +0800 you wrote:
> When the device unexpectedly restarts during previous firmware
> download process, it can cause mt79xx firmware status to be
> abnormal in the next attempt. In this case, a reset should be
> performed to ensure everything starts afresh.
>
> These changes include:
> 1. Optimizing the handling after the download function retry
> is exhausted, a reset should be performed.
> 2. Another download firmware command also needs to check status
> , and if an unexpected status occurs, trigger a reset.
> 3. Adding a flag "BTMTK_FIRMWARE_DL_RETRY": if download firmware
> process enters the reset mechanism, this flag will be set.
> After a successful setup, the flag will be cleared.
> If the flag is already set, no further reset attempts will be
> made to avoid endless reset retries.
>
> [...]
Here is the summary with links:
- [v1,1/3] Bluetooth: btmtk: improve mt79xx firmware setup retry flow
https://git.kernel.org/bluetooth/bluetooth-next/c/9cc9fc9bff32
- [v1,2/3] Bluetooth: btmtk: add status check in mt79xx firmware setup
https://git.kernel.org/bluetooth/bluetooth-next/c/458b6d8b0108
- [v1,3/3] Bluetooth: btmtk: Add reset mechanism if downloading firmware failed
https://git.kernel.org/bluetooth/bluetooth-next/c/73130272a121
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:[~2026-02-11 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 6:25 [PATCH v1 0/3] Trigger reset if firmware status is abnormal when Chris Lu
2026-02-03 6:25 ` [PATCH v1 1/3] Bluetooth: btmtk: improve mt79xx firmware setup retry flow Chris Lu
2026-02-03 7:48 ` Trigger reset if firmware status is abnormal when bluez.test.bot
2026-02-03 6:25 ` [PATCH v1 2/3] Bluetooth: btmtk: add status check in mt79xx firmware setup Chris Lu
2026-02-03 6:25 ` [PATCH v1 3/3] Bluetooth: btmtk: Add reset mechanism if downloading firmware failed Chris Lu
2026-02-11 19: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=177083880957.688115.17676708288116358310.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chris.lu@mediatek.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=sean.wang@mediatek.com \
--cc=ss.wu@mediatek.com \
--cc=steve.lee@mediatek.com \
--cc=will-cy.Lee@mediatek.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