Skip to content

Conversation

@WeiDeng-weiden
Copy link

@WeiDeng-weiden WeiDeng-weiden commented Jan 12, 2026

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: 4366079

@Mani-Sadhasivam

…ass pwrseq 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]>
@qcomlnxci qcomlnxci requested a review from a team January 12, 2026 09:03
@shashim-quic
Copy link
Collaborator

May be let's keep it failing till it is resolved formally in upstream.

@WeiDeng-weiden
Copy link
Author

May be let's keep it failing till it is resolved formally in upstream.

Hi maintainer, without this temporary fix, BT cannot power up after an on→off→on cycle, so the functionality is blocked. The DTS change passes DT binding checks.

@Mani-Sadhasivam
Copy link
Contributor

May be let's keep it failing till it is resolved formally in upstream.

@shashim-quic So you do not want the BT feature to be enabled in the meantime?

@che-jiang
Copy link

@shashim-quic Without this change, the Bluetooth functionality will remain blocked. We would like to add the workaround, as the formal upstream fix (M.2 solution) has no confirmed timeline and may take a long time to be available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants