-
Notifications
You must be signed in to change notification settings - Fork 53
WORKAROUND: arm64: dts: qcom: Remove WCN6855 PMU node to bypass pwrse… #214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
WeiDeng-weiden
wants to merge
1
commit into
qualcomm-linux:qcom-6.18.y
Choose a base branch
from
WeiDeng-weiden:qcom-6.18.y
base: qcom-6.18.y
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
WORKAROUND: arm64: dts: qcom: Remove WCN6855 PMU node to bypass pwrse… #214
WeiDeng-weiden
wants to merge
1
commit into
qualcomm-linux:qcom-6.18.y
from
WeiDeng-weiden:qcom-6.18.y
+16
−130
Conversation
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
…q flow There is a conflict between the current DTS configuration and the driver behavior for the WCN6855 Bluetooth path. With the PMU node in place, the driver takes the pwrseq code path unintentionally, which leads to Bluetooth failing to power up during an on -> off -> on transition. To unblock function, temporarily remove the WCN6855 PMU node so that the driver follows the non-pwrseq path and avoids the unexpected sequence. This is a TEMPORARY WORKAROUND. Once a proper M.2 binding/solution is upstreamed, will re-submit both DTS and driver changes aligned with the M.2 model. Signed-off-by: Wei Deng <[email protected]>
shashim-quic
approved these changes
Feb 2, 2026
Tests-kaanapali-qrd
Tests-lemans-evk
Tests-qcs615-ride
Tests-qcs6490-rb3gen2
Tests-qcs8300-ride
Tests-qcs9100-ride-r3
Tests-sm8750-mtp
Tests-x1e80100-crd
|
Author
|
Hi @shashim-quic, I saw some jobs failed here, I checked log, then found the f/w not found issue is not reproduced in the local build(2.0 base+this fix). |
Tests-kaanapali-qrd
Tests-lemans-evk
Tests-qcs615-ride
Tests-qcs6490-rb3gen2
Tests-qcs8300-ride
Tests-qcs9100-ride-r3
Tests-sm8750-mtp
Tests-x1e80100-crd
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

…q flow
There is a conflict between the current DTS configuration and the driver behavior for the WCN6855 Bluetooth path. With the PMU node in place, the driver takes the pwrseq code path unintentionally, which leads to Bluetooth failing to power up during an on -> off -> on transition.
To unblock function, temporarily remove the WCN6855 PMU node so that the driver follows the non-pwrseq path and avoids the unexpected sequence.
This is a TEMPORARY WORKAROUND. Once a proper M.2 binding/solution is upstreamed, will re-submit both DTS and driver changes aligned with the M.2 model.
CRs-Fixed: 4406298