FROMLIST: ASoC: qcom: sc8280xp: configure codec sysclk for QCS615 - #917
FROMLIST: ASoC: qcom: sc8280xp: configure codec sysclk for QCS615#917QTI-Quill wants to merge 1 commit into
Conversation
Continuous high-amplitude noise could occur in the DA7213 microphone capture path after a Bluetooth out-of-range/reset event followed by reconnection. The noise was present in both the raw ALSA capture and PipeWire input, confirming that it originated before Bluetooth encoding. The codec already obtains and enables MCLK through its DT clock and bias-level handling. However, the machine driver did not explicitly configure the codec sysclk during hw_params(). Enable codec_sysclk_set for QCS615 so that the DA7213 clock source and rate are configured before the codec power-up sequence. Verified on QCS615 Talos with repeated Bluetooth disconnect and reconnect cycles. The noise was no longer reproducible. Link: https://lore.kernel.org/all/20260807012450.1038180-1-le.qi@oss.qualcomm.com/ Signed-off-by: Le Qi <le.qi@oss.qualcomm.com>
|
Merge Check Failed: No Change Task Found No associated change tasks found for CR 4612854 on any of the following entities: Entities:
CR: 4612854 Please ensure the CR has a change task associated with at least one of the entities for this branch. |
|
Merge Check Failed: CR Not Eligible for Merge CR 4612854 is not eligible for merge. The parent software image for kernel.qli.2.0 is not development complete. Entity: Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations. |
2 similar comments
|
Merge Check Failed: CR Not Eligible for Merge CR 4612854 is not eligible for merge. The parent software image for kernel.qli.2.0 is not development complete. Entity: Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations. |
|
Merge Check Failed: CR Not Eligible for Merge CR 4612854 is not eligible for merge. The parent software image for kernel.qli.2.0 is not development complete. Entity: Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations. |
|
qli-2.0 GA Critical Fix |
Test Matrix
|
🔨 Build Failure Analysis — PR #917PR: #917 Build Status: ✅ BUILD SUCCEEDEDThe kernel compilation completed successfully with no errors. The workflow failure was caused by LAVA test infrastructure issues, not by compilation problems.
VerdictNo compilation errors were introduced by this PR. The build succeeded completely. The workflow failure is due to test infrastructure (LAVA job submission) issues, which are unrelated to the code changes in this PR. 📎 Detailed analysis: Full report |
🔨 Build Failure Analysis — PR #917PR: #917 VerdictNo compilation errors found. Both the default and RT kernel builds completed successfully. The workflow failure was caused by LAVA test infrastructure timeouts, not by any issues introduced in this PR. Build Status:
Root Cause: All test jobs failed to submit to the LAVA server due to connection timeouts ( PR Changes: The PR adds a single line enabling 📎 Detailed analysis: Full report |
🔨 Build Failure Analysis — PR #917PR: #917 VerdictNo compilation errors found. The workflow failed due to LAVA test infrastructure timeout, not build failures. Both kernel builds (regular and RT) completed successfully. Root Cause: LAVA job submission timeout ( Build Status:
📎 Detailed analysis: Full report |
🔨 Build Failure Analysis — PR #917PR: #917 Build Status: ✅ SUCCESSFULThe kernel build completed successfully. The workflow failure was caused by test infrastructure issues (LAVA job submission failures), not compilation errors.
VerdictNo compilation errors were introduced by this PR. The workflow failure is due to test infrastructure problems, not code issues. The PR changes are build-safe. 📎 Detailed analysis: Full report |
🔨 Build Failure Analysis — PR #917PR: #917 Build Status: ✅ SUCCESSFULBoth the standard and RT kernel builds completed successfully with zero compilation errors. Test Status: ❌ FAILED (Infrastructure Issue)All 10 LAVA test jobs failed due to LAVA server connectivity issues, not code problems:
VerdictThis PR introduces ZERO compilation errors. The workflow failure is caused by LAVA infrastructure connectivity issues (timeouts and gateway errors), not by the code changes in this PR. The PR change (adding 📎 Detailed analysis: Full report |
🔨 Build Failure Analysis — PR #917PR: #917 VerdictNo compilation errors found. Both kernel builds (standard and RT) completed successfully. The workflow failure was caused by LAVA test infrastructure issues (connection timeouts to lava-oss.qualcomm.com), not by the PR changes. Build Status:
Root Cause: The workflow marked as failed due to LAVA job submission timeouts when attempting to connect to PR Changes: The PR adds a single line ( 📎 Detailed analysis: Full report |
🔨 Build Failure Analysis — PR #917PR: #917
VerdictThe kernel build completed successfully. The workflow failure was caused by LAVA test job submission timeouts (infrastructure issue), not by compilation errors. The PR introduces no build-breaking changes. 📎 Detailed analysis: Full report |
🔨 Build Failure Analysis — PR #917PR: #917 Build Status: ✅ SUCCESSBoth kernel builds (standard and RT) completed successfully with no compilation errors.
Workflow Failure CauseThe workflow was marked as failed due to LAVA test job submission failures, not build failures. All test jobs failed to submit to the LAVA infrastructure:
VerdictNo compilation errors were introduced by this PR. The PR changes compile cleanly. The workflow failure is due to infrastructure issues with LAVA test job submission, which is unrelated to the code changes in this PR. 📎 Detailed analysis: Full report |
🔨 Build Failure Analysis — PR #917PR: #917 Build Status: ✅ SUCCESSThe kernel build completed successfully for both standard and RT configurations. The PR changes compiled without errors.
Workflow Failure Root CauseThe workflow was marked as failed due to LAVA test job submission timeouts, not compilation errors: All 10 test jobs failed to submit due to LAVA server connectivity issues. VerdictNo compilation errors found. The PR introduces no build failures. The workflow failure is due to infrastructure issues (LAVA server timeout), not code problems. 📎 Detailed analysis: Full report |
🔨 Build Failure Analysis — PR #917PR: #917
VerdictNo compilation errors found. The kernel built successfully for both standard and RT configurations. The workflow failure was caused by LAVA server connectivity timeouts during test job submission, which is an infrastructure issue unrelated to the PR code changes. 📎 Detailed analysis: Full report |
Continuous high-amplitude noise could occur in the DA7213 microphone capture path after a Bluetooth out-of-range/reset event followed by reconnection. The noise was present in both the raw ALSA capture and PipeWire input, confirming that it originated before Bluetooth encoding.
The codec already obtains and enables MCLK through its DT clock and bias-level handling. However, the machine driver did not explicitly configure the codec sysclk during hw_params(). Enable codec_sysclk_set for QCS615 so that the DA7213 clock source and rate are configured before the codec power-up sequence.
Verified on QCS615 Talos with repeated Bluetooth disconnect and reconnect cycles. The noise was no longer reproducible.
Link: https://lore.kernel.org/all/20260807012450.1038180-1-le.qi@oss.qualcomm.com/
CRs-Fixed: 4612854