Skip to content

FROMLIST: ASoC: qcom: sc8280xp: configure codec sysclk for QCS615 - #917

Open
QTI-Quill wants to merge 1 commit into
qualcomm-linux:qcom-6.18.yfrom
QTI-Quill:talos-bt-issue
Open

FROMLIST: ASoC: qcom: sc8280xp: configure codec sysclk for QCS615#917
QTI-Quill wants to merge 1 commit into
qualcomm-linux:qcom-6.18.yfrom
QTI-Quill:talos-bt-issue

Conversation

@QTI-Quill

@QTI-Quill QTI-Quill commented Aug 7, 2026

Copy link
Copy Markdown

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

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>
@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: No Change Task Found

No associated change tasks found for CR 4612854 on any of the following entities:

Entities:

  • kernel.qli.2.0

CR: 4612854

Please ensure the CR has a change task associated with at least one of the entities for this branch.

@qswat-orbit-external

Copy link
Copy Markdown

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: kernel.qli.2.0
CR: 4612854
Reason: CR_CANNOT_MERGE

Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations.

2 similar comments
@qswat-orbit-external

Copy link
Copy Markdown

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: kernel.qli.2.0
CR: 4612854
Reason: CR_CANNOT_MERGE

Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations.

@qswat-orbit-external

Copy link
Copy Markdown

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: kernel.qli.2.0
CR: 4612854
Reason: CR_CANNOT_MERGE

Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations.

@QTI-Quill

Copy link
Copy Markdown
Author

qli-2.0 GA Critical Fix

@qcomlnxci

Copy link
Copy Markdown

Test Matrix

Test Case *

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #917

PR: #917
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/31466005090

Build Status: ✅ BUILD SUCCEEDED

The kernel compilation completed successfully with no errors. The workflow failure was caused by LAVA test infrastructure issues, not by compilation problems.

Component Status Details
Kernel Build ✅ Pass Completed successfully at 2026-08-11T07:44:35Z
RT Build ✅ Pass Completed successfully
Modified File ✅ Pass sound/soc/qcom/sc8280xp.c compiled without errors
Test Submission ❌ Fail LAVA job submission failed (infrastructure issue)

Verdict

No 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

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #917

PR: #917
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/31466005090

Verdict

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

  • ✅ Default kernel build: SUCCESS
  • ✅ RT kernel build: SUCCESS
  • ❌ LAVA test submission: FAILED (infrastructure timeout)

Root Cause: All test jobs failed to submit to the LAVA server due to connection timeouts (HTTPSConnectionPool(host='lava-oss.qualcomm.com', port=443): Read timed out). This is an infrastructure issue unrelated to the PR changes.

PR Changes: The PR adds a single line enabling codec_sysclk_set = true for QCS615 in sound/soc/qcom/sc8280xp.c. This change does not introduce any compilation errors.

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #917

PR: #917
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/31466005090

Verdict

No 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 (HTTPSConnectionPool(host='lava-oss.qualcomm.com', port=443): Read timed out) — this is an infrastructure issue unrelated to the PR code changes.

Build Status:

  • ✅ Regular kernel build: SUCCESS
  • ✅ RT kernel build: SUCCESS
  • ✅ Modified file sound/soc/qcom/sc8280xp.c: Compiled successfully
  • ❌ Test submission: FAILED (infrastructure timeout)

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #917

PR: #917
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/31466005090

Build Status: ✅ SUCCESSFUL

The kernel build completed successfully. The workflow failure was caused by test infrastructure issues (LAVA job submission failures), not compilation errors.

Component Status Details
Kernel Build ✅ Pass All files compiled successfully
Modified File ✅ Pass sound/soc/qcom/sc8280xp.c compiled without errors
Test Submission ❌ Fail LAVA job submission failed (infrastructure issue)

Verdict

No 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

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #917

PR: #917
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/31466005090

Build Status: ✅ SUCCESSFUL

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

Platform Error
qcs615-ride HTTPSConnectionPool(host='lava-oss.qualcomm.com', port=443): Read timed out. (read timeout=20.0)
qcs6490-rb3gen2 HTTPSConnectionPool(host='lava-oss.qualcomm.com', port=443): Read timed out. (read timeout=20.0)
monaco-evk HTTPSConnectionPool(host='lava-oss.qualcomm.com', port=443): Read timed out. (read timeout=20.0)
purwa-iot-evk HTTPSConnectionPool(host='lava-oss.qualcomm.com', port=443): Read timed out. (read timeout=20.0)
lemans-evk HTTPSConnectionPool(host='lava-oss.qualcomm.com', port=443): Read timed out. (read timeout=20.0)
qcs8300-ride HTTPSConnectionPool(host='lava-oss.qualcomm.com', port=443): Read timed out. (read timeout=20.0)
hamoa-iot-evk HTTPSConnectionPool(host='lava-oss.qualcomm.com', port=443): Read timed out. (read timeout=20.0)
qrb2210-rb1 502 Server Error: Bad Gateway for url: lava-oss.qualcomm.com/RPC2
shikra-iqs-evk 504 Server Error: Gateway Time-out for url: lava-oss.qualcomm.com/RPC2
qcs9100-ride-r3 LAVA job submission failed

Verdict

This 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 .codec_sysclk_set = true to qcs615_priv_data) is syntactically correct and compiled successfully.

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #917

PR: #917
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/31466005090

Verdict

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

  • ✅ Standard kernel build: SUCCESS
  • ✅ RT kernel build: SUCCESS
  • ❌ LAVA test submission: FAILED (infrastructure timeout)

Root Cause: The workflow marked as failed due to LAVA job submission timeouts when attempting to connect to lava-oss.qualcomm.com (HTTPSConnectionPool read timeout after 20 seconds). This is an infrastructure/network issue unrelated to the code changes in this PR.

PR Changes: The PR adds a single line (codec_sysclk_set = true) to sound/soc/qcom/sc8280xp.c for QCS615 audio configuration. This change compiled cleanly in both build variants.

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #917

PR: #917
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/31466005090

# Error File:Line PR-introduced? Root Cause
N/A No compilation errors N/A N/A Build succeeded; workflow failed due to LAVA test infrastructure timeout

Verdict

The 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

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #917

PR: #917
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/31466005090

Build Status: ✅ SUCCESS

Both kernel builds (standard and RT) completed successfully with no compilation errors.

Build Type Status Result
Standard build ✅ Pass Build completed successfully
RT build ✅ Pass Build completed successfully

Workflow Failure Cause

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

  • qcs6490-rb3gen2: LAVA job submission failed
  • All other target platforms: LAVA job submission failed

Verdict

No 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

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #917

PR: #917
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/31466005090

Build Status: ✅ SUCCESS

The kernel build completed successfully for both standard and RT configurations. The PR changes compiled without errors.

Build Type Status Details
Standard Build ✅ Pass sound/soc/qcom/sc8280xp.c compiled and linked successfully
RT Build ✅ Pass All modules built successfully

Workflow Failure Root Cause

The workflow was marked as failed due to LAVA test job submission timeouts, not compilation errors:

Unable to connect: HTTPSConnectionPool(host='lava-oss.qualcomm.com', port=443): 
Read timed out. (read timeout=20.0)

All 10 test jobs failed to submit due to LAVA server connectivity issues.

Verdict

No 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

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #917

PR: #917
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/31466005090

# Error File:Line PR-introduced? Root Cause
N/A No compilation errors N/A N/A Workflow failed due to LAVA infrastructure timeout, not code issues

Verdict

No 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

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