From: Paul Menzel <pmenzel@molgen.mpg.de>
To: "Chris Lu (陸稚泓)" <Chris.Lu@mediatek.com>
Cc: "Will-CY Lee (李政穎)" <Will-CY.Lee@mediatek.com>,
"Steve Lee (李視誠)" <steve.lee@mediatek.com>,
luiz.dentz@gmail.com, marcel@holtmann.org,
"SS Wu (巫憲欣)" <ss.wu@mediatek.com>,
linux-kernel@vger.kernel.org, johan.hedberg@gmail.com,
"Sean Wang" <Sean.Wang@mediatek.com>,
linux-bluetooth@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v1] Bluetooth: btmtk: Add MT7928 support
Date: Wed, 17 Jun 2026 08:53:41 +0200 [thread overview]
Message-ID: <4501985d-c8df-4121-89fd-0b4eb09273c6@molgen.mpg.de> (raw)
In-Reply-To: <03e0a6787272a445448a3189b4b575aa85396fb0.camel@mediatek.com>
Dear Chris,
Thank you for your answer, and sending in v2.
Am 17.06.26 um 04:16 schrieb Chris Lu (陸稚泓):
> On Tue, 2026-06-16 at 12:24 +0200, Paul Menzel wrote:
>> Am 16.06.26 um 05:01 schrieb Chris Lu:
>>> Add support for MT7928 (device ID 0x7935) which requires additional
>>> firmware (CBMCU firmware) loading before Bluetooth firmware.
>>
>> Please detail what CBMCU firmware is.
>
> CBMCU is a new component on MT7928 to handle common part shared across
> the combo chip (Wi-Fi/Bluetooth's subsystem), providing a better user
> experience through improved coordination between subsystems.
Thank you, but please add it to the commit message.
>>> Implement two-phase CBMCU firmware download: Phase 1 loads
>>> section with type 0x5 containing global descriptor,
>>> section maps and signature data; Phase 2 loads remaining
>>> firmware sections. Add retry mechanism for concurrent download
>>> protection.
>>
>> What is type 0x5? How big is the firmware, and how long does it take?
>>
>>> After CBMCU firmware loads successfully, the driver continues
>>> to load corresponding BT firmware based on device ID through
>>> fallthrough to case 0x7922/0x7925.
>>
>> Please add the new log message to the commit message.
Thank you for adding those. Please also mention, where to find the new
firmware.
[…]
Kind regards,
Paul
PS: Also, Pauli’s question should be answered in the commit message
(internal/external name). (If questions show up during review, it’s a
good indicator to amend the commit message answering these questions.)
next prev parent reply other threads:[~2026-06-17 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 3:01 Chris Lu
2026-06-16 10:24 ` Paul Menzel
2026-06-17 2:16 ` Chris Lu (陸稚泓)
2026-06-17 6:53 ` Paul Menzel [this message]
2026-06-17 8:34 ` Chris Lu (陸稚泓)
2026-06-17 8:49 ` Paul Menzel
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=4501985d-c8df-4121-89fd-0b4eb09273c6@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=Chris.Lu@mediatek.com \
--cc=Sean.Wang@mediatek.com \
--cc=Will-CY.Lee@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=ss.wu@mediatek.com \
--cc=steve.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
all inboxes | Powered by JetHome®