bluetooth: handle dynamic M.2 controllers (GH#533) - #534
Merged
vnarapar merged 1 commit intoAug 13, 2026
Conversation
M.2 E-key Bluetooth devices instantiated by pwrseq-pcie-m2 may not expose a static qcom,wcn*-bt device-tree node. Accept the connector topology and make a missing static BT node advisory so operational HCI devices do not false-fail, while the existing firmware, KMD, service, HCI, address, and controller checks remain authoritative. Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>
Srikanth Muppandam (smuppand)
force-pushed
the
dev/gh-533-bt-fw-kmd-service
branch
from
August 13, 2026 11:43
a4dcea3 to
9c4548e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #533 reported issue. M.2 E-key Bluetooth devices instantiated by pwrseq-pcie-m2 may not expose a static qcom,wcn*-bt device-tree node. Accept the connector topology and make a missing static BT node advisory so operational HCI devices do not false-fail, while the existing firmware, KMD, service, HCI, address, and controller checks remain authoritative.
here is the job https://lava.infra.foundries.io/scheduler/job/359721 for reference with this PR changes