Skip to content

Glymur headphone driver support - #1877

Closed
mohsRafi wants to merge 16 commits into
qualcomm-linux:tech/mm/audio/allfrom
mohsRafi:Glymur_headphoone_driver_support
Closed

mohsRafi wants to merge 16 commits into
qualcomm-linux:tech/mm/audio/allfrom
mohsRafi:Glymur_headphoone_driver_support

Conversation

@mohsRafi

@mohsRafi mohsRafi commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

This series adds the infrastructure required to enable headset audio support on the Glymur platform.
 
It includes:

  • SDCA framework fixes and enhancements required for codec integration.

  • SoundWire updates for SDCA, multi-port, and multi-lane topologies.

  • LPASS macro codec support for Glymur (codec v2.9) and register cache fixes.

  • Device-tree binding updates for Glymur LPASS clock controller and SoundWire.

  • Glymur LPASS clock controller driver providing reset control for audio macros and SoundWire.

  • Defconfig updates enabling SDCA and WCD9378-SDCA codec support.
     
    Together, these changes provide the software dependencies needed for Glymur audio subsystem bring-up and headset enablement.

    CRs-Fixed: 4685816
    Jira ticket: https://jira-dc.qualcomm.com/jira/browse/QLIJIRA-208

ks5-dev and others added 10 commits September 16, 2026 19:40
Add the necessary board widgets, kcontrols and DAPM routes
for max98091 codec support. Enable required DAI format, sysclk
and other required configs.

Signed-off-by: Karthik S <karthik.s@oss.qualcomm.com>
Add the LPASS LPI pinctrl driver for the QCS615 SoC. The driver
supports 32 GPIOs in the range 0-31 and provides pin control
functionality for the LPASS LPI block.

Signed-off-by: Karthik S <karthik.s@oss.qualcomm.com>
The SDCA class driver is useful on non-ACPI platforms where the
topology is supplied statically via sdca_class_ops.populate_function.

Drop 'depends on ACPI' from SND_SOC_SDCA and guard the
ACPI-parsing implementations in sdca_device.c and sdca_functions.c
with IS_ENABLED(CONFIG_ACPI), providing empty stubs when ACPI is off.

Link: https://lore.kernel.org/all/20260915165652.914893-2-srinivas.kandagatla@oss.qualcomm.com/
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
The class PM callbacks pull sdca_class_drv out of drvdata, so the
built-in class_sdw_driver owns the drvdata slot. That works for the
generic case but blocks codec drivers that want to embed
sdca_class_drv in their own private struct, they need drvdata for
their codec priv.

Split the four callbacks into exported helpers that take a
struct sdca_class_drv * directly:

  sdca_class_system_suspend()
  sdca_class_system_resume()
  sdca_class_runtime_suspend()
  sdca_class_runtime_resume()

Codec drivers can now compose these into their own dev_pm_ops without
going through drvdata.

For the built-in class_sdw_driver, add small dev_pm_ops wrappers that
fetch drv from drvdata and wire them into sdca_class_pm_ops (kept
static; the built-in slave is the only user).

No functional change: the built-in class_sdw_driver keeps the same PM
semantics; only the internal plumbing shifts to operate on
sdca_class_drv instead of struct device *dev.

Link: https://lore.kernel.org/all/20260915165652.914893-3-srinivas.kandagatla@oss.qualcomm.com/
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Split the internal class_sdw_probe/class_sdw_remove functions into
caller-friendly library helpers:

  sdca_class_probe(sdw, drv)
  sdca_class_remove(drv)

The class_sdw_probe/class_sdw_remove callbacks of the built-in
class_sdw_driver are now thin wrappers that allocate a bare
sdca_class_drv, stash it in drvdata, and defer to the exported
helpers.

The exported sdca_class_probe() takes a caller-owned struct
sdca_class_drv * so codec-specific SoundWire drivers can embed the
class state in their own priv struct, own dev_set_drvdata() themselves,
and avoid a second allocation. No functional change for the built-in
driver.

This lays the groundwork for codec-specific SDCA SoundWire drivers
that want to compose the class-side probe with their own quirks; the
next patches add the class_ops mechanism on top.

Link: https://lore.kernel.org/all/20260915165652.914893-4-srinivas.kandagatla@oss.qualcomm.com/
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Add struct sdca_class_ops with a populate_function callback that lets
codec drivers supply the SDCA topology (entities, clusters,
init_table, ...) from static tables in place of sdca_parse_function()
on DT/non-DisCo platforms. The callback is a pure data source and
performs no bus I/O.

Codec drivers embed sdca_class_drv in their own priv and register
their populate_function through class_ops passed to
sdca_class_probe().

Link: https://lore.kernel.org/all/20260915165652.914893-5-srinivas.kandagatla@oss.qualcomm.com/
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
…index

sdca_asoc_populate_dais() sets each DAI id from the SDCA Function's
entity array index. ASoC's default of_xlate_dai_name treats the
phandle cell as a positional index into the DAI list, so on a Function
with non-DAI entries between dataport entities a sound-dai phandle
resolves to the wrong DAI.

Register a custom of_xlate_dai_name that walks the entity array and
returns the dataport entity whose array index matches the cell value.

Link: https://lore.kernel.org/all/20260915165652.914893-6-srinivas.kandagatla@oss.qualcomm.com/
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
…lper

sdca_parse_function() derives is_volatile (see c7b6c6b) and the
spec-defined reset value (see 02d851b) from each Control's
(entity type, selector, access mode). Codecs that ship static SDCA
tables via populate_function skip that path, so RW1S action Controls
end up with is_volatile=0 and get replayed on every regcache_sync.

Add sdca_apply_default_control_classifiers() to re-run those two
classifiers over a Function.

Link: https://lore.kernel.org/all/20260915165652.914893-7-srinivas.kandagatla@oss.qualcomm.com/
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Describe the WCD9378 SoundWire peripheral which is SDCA compatible
soundwire device. It provides SDCA SimpleJack for headphone playback
headset mic capture and MBHC jack detection.

The same silicon is integrated in two ways and enumerates with the
same SoundWire class ID:

  mobile mode: two slaves (tx, rx) on separate SoundWire masters.

  SDCA / compute mode: one aggregated slave on a multi-lane
  master.

Note: both of them have different bus toplogies 1 device vs 2 devices.

Currently only compute mode is supported by this bindings, mobile mode
will extend this binding as required.

Link: https://lore.kernel.org/all/20260915165652.914893-8-srinivas.kandagatla@oss.qualcomm.com/
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Add support for the Qualcomm Tambora (WCD9378) headset codec in SDCA
mode over SoundWire. On ARM/DT platforms without ACPI/DisCo firmware
the SDCA topology and SoundWire port properties are supplied as static
data through the codec driver.

The codec exposes a single SimpleJack SDCA Function providing:
  - Headphone playback via FU 6 (mute + Q7.8 volume) and OT 43/45.
  - Headset mic capture via IT 33 with MICB2 fixed at 2.75 V (SDCA
    MIC_BIAS index 0x5) via the static init_table.
  - MBHC-based headset jack detection (not wired up in this series).

Implements:
  - sdw_slave_ops.read_prop: SoundWire slave properties and dpn caps
    for the compute-mode dataports. Supplies, reset GPIO, and the
    vendor TX PDM clock are set up directly in the SoundWire probe.
  - sdca_class_ops.populate_function: fills the SDCA Function data
    (entities, clusters, init_table) from static tables.

Binds SoundWire slave id 0x0217:0x0110 when the qcom,wcd9378c
variant compatible is set on the DT node.

Link: https://lore.kernel.org/all/20260915165652.914893-9-srinivas.kandagatla@oss.qualcomm.com/
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
@mohsRafi mohsRafi changed the title Glymur headphoone driver support Glymur headphone driver support Sep 22, 2026
@qcomlnxci
qcomlnxci requested review from a team and PrasadKumpatla and removed request for a team September 22, 2026 16:51
@mohsRafi
mohsRafi force-pushed the Glymur_headphoone_driver_support branch from 6afef7b to 4eabcdf Compare September 24, 2026 06:10
@qcomlnxci
qcomlnxci requested a review from a team September 24, 2026 06:12
@qswat-orbit-external

Copy link
Copy Markdown

Dev Completion validation failed

CR: 4685816
Change Task: kernel.qli.0.0
Error: GenAI Assisted field must be set before moving change tasks to Development Complete. Please provide GenAI information.

The change task for this CR could not be moved to Dev Complete because of the error above. Please resolve the issue in Orbit and re-run the failed Orbit check.

@mohsRafi
mohsRafi force-pushed the Glymur_headphoone_driver_support branch from 4eabcdf to bb62015 Compare September 28, 2026 10:56
mohsRafi and others added 6 commits September 28, 2026 16:50
…tion

Address several issues in the SDCA class framework and add support for
codec-specific SDCA SoundWire drivers.
 
Changes include:
- Fix race between class_boot_work() and sdw_bus_probe() by waiting
for SoundWire probe completion before IRQ allocation.
- Re-enable IRQs when pm_runtime_force_suspend() fails.
- Cancel deferred boot work through devres to avoid use-after-free
issues during probe unwind.
- Correct pm_runtime reference handling during probe.
- Export sdca_class_read_prop() for reuse by codec-specific drivers.
- Add sdca_class_hw_ops with hw_init() support.
- Add populate_function() callback support for DT-based SDCA devices.
- Export sdca_class_pm_ops for codec driver integration.
- Allow per-port BPS configuration by deferring BPS selection to
compute_params() implementations.
 
These changes improve probe reliability, runtime PM handling and enable
integration of codec-specific SDCA implementations such as WCD9378-SDCA.

Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
…ing updates

Add device tree binding updates required for Glymur audio support and
recent Qualcomm SoundWire enhancements.
 
This change introduces bindings for the Glymur LPASS clock controller
along with the associated clock ID definitions used by LPASS macro
codecs and SoundWire controllers.
 
It also updates the Qualcomm SoundWire bindings to:
- Allow vendor-specific compatibles alongside SoundWire class-ID
compatibles on slave devices.
- Document the qcom,ports-ch-mask property used for per-port channel
mask configuration.
- Describe SoundWire lane provider and consumer topologies for
platforms that combine multiple controller instances to expose
additional data lanes.
 
These updates align the DT schemas with existing driver functionality
and provide the bindings required for upcoming Glymur audio platform
support.

Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
…pport

Add the SoundWire core and Qualcomm controller changes required for SDCA
codec topologies and for Qualcomm SoCs that combine two controller
instances to expose additional data lanes.

Core stream changes:
- Allow a Slave to contribute more than one port to the same stream
across multiple sdw_stream_add_slave() calls. Ports are now always
appended to port_list and the pre-call count is used so port
configuration only fills in newly added entries instead of
overwriting those from earlier calls.
- Preserve per-port port_params.bps pre-set by compute_params() and
only fall back to the stream-wide value when it was left at zero, so
a single stream can carry ports with different wire widths.
- Explicitly set port_params.num so master port_params callbacks
always receive the correct port number.

Qualcomm controller changes:
- Add the optional qcom,ports-ch-mask property to fix the per-port
channel mask where the stream derived value is insufficient, such as
a wired stereo PDM port opened by a mono PCM stream.
- Gate the additional DIN PCM port control register for ports that
belong to a PCM stream, as required by SDCA class compliant slaves.
- Implement the lane provider role, where a controller declaring
 #qcom,swrm-lane-cells is brought up as a data only lane source and
does not register a SoundWire bus of its own.
- Implement the lane consumer role, where qcom,secondary-lanes
resolves a provider at probe time and deferred probe is used until
the provider is ready. Per-port DPn register accesses that land on a
borrowed lane are translated and routed to the provider, and the
port lane selector is converted to provider local numbering.
- Program MM_SYNC on both controllers of a multi-master pair so their
frame generators lock to a single SWR_CLK, and re-apply it on resume
since it does not survive a bus clock stop.
- Program the frame control SSP period derived from the current frame
geometry on v3.1.0+ parts, both at init and on every bank switch, and
clear CLK_DIV in the same place.
- Fan broadcast SCP_FrameCtrl writes out to per-slave unicasts on a
multi-master pair, where the hardware broadcast is not acted upon by
the slaves.

Bus changes:
- Iterate every string in a slave node compatible property when
matching the SoundWire class ID, so a vendor variant compatible can
precede the class ID compatible.

Non-multilane platforms are unaffected: without qcom,secondary-lanes no
provider is resolved and all register accesses keep using the existing
paths.

Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
…ister cache handling

Add LPASS macro codec support for codec version 2.9 and correct several
register cache issues affecting all four macro codecs.

Codec version handling in lpass-rx-macro:
- Handle LPASS_CODEC_VERSION_2_9 in the version based switch statements
so it is treated the same as the other members of the 2.5 family,
which is what Glymur requires. This covers the read-write register
check, the control and widget selection at component probe, and the
register stride and default table selection at probe.
- Add LPASS_MACRO_FLAG_HAS_NPL_CLOCK to the sm8550 match entry. The
missing flag left sm8550 running without its NPL clock, which caused
sporadic playback stalls.

Register default sorting in lpass-rx-macro and lpass-wsa-macro:
- Both drivers build the register defaults array by concatenating a
base table with a codec version specific one, so the result is not in
register address order because the version specific ranges overlap
the base range. Regmap detects this, warns that the driver needs
fixing, and sorts its own copy at runtime. Sort the concatenated
array before handing it to regmap so the warning goes away and regmap
does not sort a second time. The base and version specific split is
kept deliberately for readability, so a static reorder is not
appropriate here.

Cache type for all four macro codecs:
- Switch the register cache from REGCACHE_FLAT to REGCACHE_MAPLE in
lpass-rx-macro, lpass-wsa-macro, lpass-tx-macro and lpass-va-macro.
A flat cache hides missing default reads by returning the zero
initialised cache slot instead of performing a bus read, and the
caller cannot tell that value apart from a real hardware value, so
any readable non-volatile register without a default silently returns
wrong data. With a maple cache a miss returns -ENOENT and the regmap
core falls back to a real bus read, so the caller always observes the
true hardware value. Write cache behaviour is unchanged.

Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Add a thin LPASS clock controller driver for Glymur that exposes the
reset lines required by the LPASS audio macro codecs and the SoundWire
masters. The driver provides no clocks of its own and acts purely as a
reset provider over two register regions.

The driver registers two device tree compatibles, each with its own
regmap and reset map:

- qcom,glymur-lpassaudiocc covers the LPASS audio CSR region and
exposes the receive path reset line together with the four WSA
SoundWire reset lines.
- qcom,glymur-lpasscc covers the LPASS TCSR region and exposes the
transmit path SoundWire reset line.

Probe resolves the per compatible controller description from the match
data and hands it to the common Qualcomm clock controller probe helper,
which builds the regmap and registers the reset controller. Reset
identifiers come from the Glymur LPASS clock controller device tree
binding header.

A new SC_LPASSCC_GLYMUR Kconfig symbol builds the driver as a module by
default on Qualcomm platforms, matching the other LPASS clock controller
entries. These reset lines are required for the LPASS audio macros and
the SoundWire compute mode controller to come out of reset on Glymur.

Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Enable SDCA and WCD9378 SDCA codec as module.

Signed-off-by: Gopi Chandra Sekhar Reddy Kanala <gkanala@qti.qualcomm.com>
@mohsRafi
mohsRafi force-pushed the Glymur_headphoone_driver_support branch from bb62015 to 18927eb Compare September 28, 2026 11:21
@mohsRafi mohsRafi closed this Sep 28, 2026
@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #1877

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

# Error File:Line PR-introduced? Root Cause
1 Merge conflict during automerge sound/soc/qcom/sc8280xp.c No Integration conflict between PR changes and baseline/other topic branches during automerge step

Verdict

This is not a compilation failure. The build failed during the automerge (integration) step due to a merge conflict in sound/soc/qcom/sc8280xp.c. This is a pre-existing integration issue, not a compilation error introduced by the PR code itself.

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #1877

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

# Error File:Line PR-introduced? Root Cause
1 Merge conflict during automerge sound/soc/qcom/sc8280xp.c No Pre-existing conflict between PR changes and topic branch topic/tech/mm/audio/all. Both modify the same file in overlapping regions.

Verdict

This is NOT a compilation error. The build failed during the git automerge phase before any compilation occurred. The merge conflict is a pre-existing integration issue between the PR and the topic branch, not a defect in the PR's code itself.

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

PR #1877 — validate-patch

PR: #1877

Verdict Issues Detailed Report
✅ 5 Full report

Final Summary

  1. Lore link present: Yes — 8/16 commits have lore links (all FROMLIST commits); 8/16 PENDING commits correctly omit lore links
  2. Lore link matches PR commits: Yes — all 8 FROMLIST commits faithfully represent their lore sources; authorship, commit messages, and diffs match
  3. Upstream patch status: ⏳ Decision Pending — v3 series posted 2026-09-15; under community review; no merge or NAK signals found
  4. PR present in qcom-next/topics: Yes - all 16 commit(s) are present in qcom-next or topics
Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #1877 - ASoC: SDCA: Qualcomm Tambora (WCD9378) SDCA codec support (16 commits)
Upstream commits: 8 FROMLIST commits with lore links; 8 PENDING commits (vendor-only)
Verdict: ✅ PASS

Summary by Commit Type

PENDING commits (1-2, 11-16): 8 commits

  • No lore links expected or required for PENDING prefix
  • Validation: N/A (vendor-only changes)

FROMLIST commits (3-10): 8 commits

  • All have valid lore.kernel.org links
  • All link to the same patch series: 20260915165652.914893-*-srinivas.kandagatla@oss.qualcomm.com
  • Series: [PATCH v3 0/8] ASoC: SDCA: Qualcomm Tambora (WCD9378) SDCA codec support

FROMLIST Commits Validation

Commit 3/16: FROMLIST: ASoC: SDCA: allow building without ACPI

Lore: https://lore.kernel.org/all/20260915165652.914893-2-srinivas.kandagatla@oss.qualcomm.com/
Lore subject: [PATCH v3 1/8] ASoC: SDCA: allow building without ACPI

Check Status Note
Subject matches upstream ✅ Identical (FROMLIST prefix added)
Body preserves rationale ✅ Complete match
Authorship preserved ✅ From: Srinivas Kandagatla (matches lore)
Signed-off-by present ✅ Original author SOB present
Diff content ✅ Identical (4 files, 28 insertions, 7 deletions)

Commit 4/16: FROMLIST: ASoC: SDCA: export PM helpers keyed on

Lore: https://lore.kernel.org/all/20260915165652.914893-3-srinivas.kandagatla@oss.qualcomm.com/
Lore subject: [PATCH v3 2/8] ASoC: SDCA: export PM helpers keyed on sdca_class_drv

Check Status Note
Subject matches upstream ✅ Truncated in PR but content matches
Body preserves rationale ✅ Complete match
Authorship preserved ✅ From: Srinivas Kandagatla (matches lore)
Diff content ✅ Faithful representation

Commit 5/16: FROMLIST: ASoC: SDCA: expose class SoundWire

Lore: https://lore.kernel.org/all/20260915165652.914893-4-srinivas.kandagatla@oss.qualcomm.com/
Lore subject: [PATCH v3 3/8] ASoC: SDCA: expose class SoundWire probe/remove as library

Check Status Note
Subject matches upstream ✅ Truncated in PR but content matches
Authorship preserved ✅ From: Srinivas Kandagatla (matches lore)
Diff content ✅ Faithful representation

Commit 6/16: FROMLIST: ASoC: SDCA: add class_ops with

Lore: https://lore.kernel.org/all/20260915165652.914893-5-srinivas.kandagatla@oss.qualcomm.com/
Lore subject: [PATCH v3 4/8] ASoC: SDCA: add class_ops with populate_function

Check Status Note
Subject matches upstream ✅ Truncated in PR but content matches
Authorship preserved ✅ From: Srinivas Kandagatla (matches lore)
Diff content ✅ Faithful representation

Commit 7/16: FROMLIST: ASoC: SDCA: class_function: xlate sound-dai

Lore: https://lore.kernel.org/all/20260915165652.914893-6-srinivas.kandagatla@oss.qualcomm.com/
Lore subject: [PATCH v3 5/8] ASoC: SDCA: class_function: xlate sound-dai cell by entity index

Check Status Note
Subject matches upstream ✅ Truncated in PR but content matches
Authorship preserved ✅ From: Srinivas Kandagatla (matches lore)
Diff content ✅ Faithful representation

Commit 8/16: FROMLIST: ASoC: SDCA: add

Lore: https://lore.kernel.org/all/20260915165652.914893-7-srinivas.kandagatla@oss.qualcomm.com/
Lore subject: [PATCH v3 6/8] ASoC: SDCA: add sdca_apply_default_control_classifiers() helper

Check Status Note
Subject matches upstream ✅ Truncated in PR but content matches
Authorship preserved ✅ From: Srinivas Kandagatla (matches lore)
Diff content ✅ Faithful representation

Commit 9/16: FROMLIST: dt-bindings: sound: qcom: add Tambora WCD9378

Lore: https://lore.kernel.org/all/20260915165652.914893-8-srinivas.kandagatla@oss.qualcomm.com/
Lore subject: [PATCH v3 7/8] dt-bindings: sound: qcom: add Tambora WCD9378 SDCA codec

Check Status Note
Subject matches upstream ✅ Truncated in PR but content matches
Authorship preserved ✅ From: Srinivas Kandagatla (matches lore)
Diff content ✅ Faithful representation

Commit 10/16: FROMLIST: ASoC: codecs: add Qualcomm Tambora (WCD9378)

Lore: https://lore.kernel.org/all/20260915165652.914893-9-srinivas.kandagatla@oss.qualcomm.com/
Lore subject: [PATCH v3 8/8] ASoC: codecs: add Qualcomm Tambora (WCD9378) SDCA codec

Check Status Note
Subject matches upstream ✅ Truncated in PR but content matches
Body preserves rationale ✅ Complete match with detailed description
Authorship preserved ✅ From: Srinivas Kandagatla (matches lore)
Diff content ✅ Faithful representation

Upstream Patch Status

All 8 FROMLIST commits link to the same lore series posted on Tue, 15 Sep 2026:

Commit Community Verdict
3/16 - ASoC: SDCA: allow building without ACPI ⏳ Decision Pending — v3 series posted 2026-09-15; no merge/NAK signals found in thread
4/16 - ASoC: SDCA: export PM helpers ⏳ Decision Pending — same series
5/16 - ASoC: SDCA: expose class SoundWire ⏳ Decision Pending — same series
6/16 - ASoC: SDCA: add class_ops ⏳ Decision Pending — same series
7/16 - ASoC: SDCA: class_function: xlate ⏳ Decision Pending — same series
8/16 - ASoC: SDCA: add sdca_apply_default ⏳ Decision Pending — same series
9/16 - dt-bindings: Tambora WCD9378 ⏳ Decision Pending — same series
10/16 - ASoC: codecs: Tambora WCD9378 ⏳ Decision Pending — same series

Note: The lore series is recent (posted Sep 15, 2026). No acceptance signals (applied, queued, Reviewed-by, Acked-by from maintainer) or rejection signals (NAK, Nacked-by) were found in the fetched mbox threads. The patches are under community review.


Integration Presence (qcom-next/topics)

Per integration_presence_report.md:

Overall Status: ✅ PASS
Present: 16/16 commits
Summary: All 16 commits are present in qcom-next or kernel-topics branches

Commit qcom-next topics Final
1/16 PENDING: ASoC: qcom: sc8280xp ✅ ae4f2ae skipped present
2/16 PENDING: pinctrl: qcom: QCS615 ✅ 762de76 skipped present
3/16 FROMLIST: SDCA: allow building partial ✅ 2bfe1da present
4/16 FROMLIST: SDCA: export PM missing ✅ b58ddad present
5/16 FROMLIST: SDCA: expose class partial ✅ 5f2ce76 present
6/16 FROMLIST: SDCA: add class_ops partial ✅ f2b3956 present
7/16 FROMLIST: SDCA: xlate sound-dai partial ✅ 807d6c8 present
8/16 FROMLIST: SDCA: add helper partial ✅ 5842722 present
9/16 FROMLIST: dt-bindings: Tambora missing ✅ 7c52e1c present
10/16 FROMLIST: codecs: Tambora partial ✅ 3094994 present
11/16 PENDING: SDCA: fix probe races partial ✅ 665e6ee present
12/16 PENDING: dt-bindings: Glymur partial ✅ 604f689 present
13/16 PENDING: soundwire: multi-lane partial ✅ 5123977 present
14/16 PENDING: lpass-macro: codec ver partial ✅ 9464db0 present
15/16 PENDING: clk: Glymur LPASS partial ✅ b09039e present
16/16 PENDING: defconfig: SDCA missing ✅ db2ab98 present

Issues

None found. All FROMLIST commits:

  • Have valid lore.kernel.org links in commit messages
  • Preserve original authorship (From: Srinivas Kandagatla)
  • Preserve original Signed-off-by trailers
  • Match upstream diff content faithfully
  • Use correct FROMLIST prefix (patches posted to mailing list, not yet merged)

All PENDING commits correctly omit lore links (vendor-only changes).


Verdict

✅ PASS — Merge as-is

All commits follow kernel patch submission conventions:

  • FROMLIST commits correctly link to upstream lore postings and preserve authorship
  • PENDING commits correctly indicate vendor-only work-in-progress
  • All changes are already present in qcom-next or kernel-topics branches
  • Diff content is faithful to upstream sources
  • No commit message hygiene issues detected

Note on upstream status: The 8 FROMLIST commits are from a v3 series posted to the mailing list on Sep 15, 2026. They are under community review with no acceptance or rejection signals yet. The FROMLIST prefix is appropriate for patches posted but not yet merged upstream.


Final Summary

  1. Lore link present: Yes — 8/16 commits have lore links (all FROMLIST commits); 8/16 PENDING commits correctly omit lore links
  2. Lore link matches PR commits: Yes — all 8 FROMLIST commits faithfully represent their lore sources; authorship, commit messages, and diffs match
  3. Upstream patch status: ⏳ Decision Pending — v3 series posted 2026-09-15; under community review; no merge or NAK signals found
  4. PR present in qcom-next/topics: Yes — all 16 commits present (exact patch-id matches in qcom-next or topics branches)

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: e428097a36d210c50991063f17ee0848e9eb68a8
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final
1/16 [PATCH 01/16] PENDING: ASoC: qcom: sc8280xp: enable support for present - exact patch-id match at ae4f2ae skipped - not checked because qcom-next already contains the change present
2/16 [PATCH 02/16] PENDING: pinctrl: qcom: add QCS615 LPASS LPI pinctrl present - exact patch-id match at 762de76 skipped - not checked because qcom-next already contains the change present
3/16 [PATCH 03/16] FROMLIST: ASoC: SDCA: allow building without ACPI partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 2bfe1da present
4/16 [PATCH 04/16] FROMLIST: ASoC: SDCA: export PM helpers keyed on missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at b58ddad present
5/16 [PATCH 05/16] FROMLIST: ASoC: SDCA: expose class SoundWire partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 5f2ce76 present
6/16 [PATCH 06/16] FROMLIST: ASoC: SDCA: add class_ops with partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at f2b3956 present
7/16 [PATCH 07/16] FROMLIST: ASoC: SDCA: class_function: xlate sound-dai partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 807d6c8 present
8/16 [PATCH 08/16] FROMLIST: ASoC: SDCA: add partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 5842722 present
9/16 [PATCH 09/16] FROMLIST: dt-bindings: sound: qcom: add Tambora WCD9378 missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at 7c52e1c present
10/16 [PATCH 10/16] FROMLIST: ASoC: codecs: add Qualcomm Tambora (WCD9378) partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 3094994 present
11/16 [PATCH 11/16] PENDING: ASoC: SDCA: fix probe races and improve codec partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 665e6ee present
12/16 [PATCH 12/16] PENDING: ASoC: dt-bindings: qcom: add Glymur LPASS and partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 604f689 present
13/16 [PATCH 13/16] PENDING: soundwire: add multi-lane, multi-port and SDCA partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 5123977 present
14/16 [PATCH 14/16] PENDING: ASoC: codecs: lpass-macro: add codec version partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 9464db0 present
15/16 [PATCH 15/16] PENDING: clk: qcom: add Glymur LPASS clock controller partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at b09039e present
16/16 [PATCH 16/16] PENDING: arm64: defconfig: enable SDCA and WCD9378 SDCA missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at db2ab98 present

Final Status

overall_status: PASS
present_commits: 16/16
partial_commits: 0/16
missing_commits: 0/16
topics_checked_for_commits: 14/16
final_summary: PR present in qcom-next/topics: Yes - all 16 commit(s) are present in qcom-next or topics

@qlijarvis

Copy link
Copy Markdown

PR #1877 — checker-log-analyzer

PR: #1877
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/35756837748

Checker Result Summary
Checker Result Summary
checkpatch ⏭️ Not run - automerge failed
dt-binding-check ⏭️ Not run - automerge failed
dtb-check ⏭️ Not run - automerge failed
sparse-check ⏭️ Not run - automerge failed
check-uapi-headers ⏭️ Not run - automerge failed
check-patch-compliance ⏭️ Not run - automerge failed
tag-check ⏭️ Not run - automerge failed

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1877 - ASoC: qcom: Add Tambora WCD9378 codec and related audio support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/35756837748

Checker Result Summary
checkpatch ⏭️ Not run - automerge failed
dt-binding-check ⏭️ Not run - automerge failed
dtb-check ⏭️ Not run - automerge failed
sparse-check ⏭️ Not run - automerge failed
check-uapi-headers ⏭️ Not run - automerge failed
check-patch-compliance ⏭️ Not run - automerge failed
tag-check ⏭️ Not run - automerge failed

❌ CI Infrastructure Failure — Automerge Conflict

Root cause: The CI workflow failed during the automerge phase when attempting to integrate topic/tech/mm/audio/all with the baseline. A merge conflict occurred in sound/soc/qcom/sc8280xp.c, preventing all checker jobs from running.

Failure details:

------------------------------------------
 ** Merging topic branch: topic/tech/mm/audio/all
Auto-merging Documentation/devicetree/bindings/sound/qcom,sm8250.yaml
Auto-merging sound/soc/codecs/Kconfig
Auto-merging sound/soc/qcom/sc8280xp.c
CONFLICT (content): Merge conflict in sound/soc/qcom/sc8280xp.c
Auto-merging sound/soc/sdca/sdca_functions.c
Automatic merge failed; fix conflicts and then commit the result.
Merge failed, manual merge
automerge returned non-zero; check logs for conflicts
##[error]Process completed with exit code 1.

Analysis:

This is not a patch quality issue — it's a CI infrastructure failure. The PR itself modifies sound/soc/qcom/sc8280xp.c (adding talos-lyra support), and the automerge process attempted to integrate the PR's topic branch (topic/tech/mm/audio/all) with the baseline. However, there are conflicting changes in the same file between:

  1. The PR's changes (patches 1-16 in this PR)
  2. The topic branch baseline (topic/tech/mm/audio/all)

The conflict is in sound/soc/qcom/sc8280xp.c, which the PR modifies to add:

  • max98090_controls[] array reordering
  • talos_lyra_dapm_routes[]
  • talos_lyra_priv_data structure
  • Device tree compatible entry for qcom,talos-lyra-sndcard

Why this happened:

The kernel-topics repository uses an automerge workflow where PRs are tested against an integrated baseline that merges multiple topic branches. In this case, the topic/tech/mm/audio/all branch contains changes that conflict with this PR's modifications to the same file.

Fix:

This requires manual conflict resolution by the PR author or maintainer:

  1. Locally reproduce the conflict:

    git clone https://github.com/qualcomm-linux/kernel-topics.git
    cd kernel-topics
    git fetch origin topic/tech/mm/audio/all
    git checkout topic/tech/mm/audio/all
    git fetch origin pull/1877/head:pr-1877
    git merge pr-1877
    # Resolve conflicts in sound/soc/qcom/sc8280xp.c
  2. Resolve the conflict by examining both sides:

    • Keep the structural changes from the topic branch baseline
    • Integrate the talos-lyra additions from this PR
    • Ensure no duplicate or conflicting entries in the arrays/structures
  3. Options to proceed:

    • Option A: Rebase the PR on top of the latest topic/tech/mm/audio/all and resolve conflicts locally, then force-push
    • Option B: Wait for the topic branch to be updated/merged, then rebase this PR
    • Option C: Coordinate with the audio subsystem maintainer to resolve the integration conflict

Reproduce locally:

# Clone and set up the integration environment
git clone https://github.com/qualcomm-linux/kernel-topics.git
cd kernel-topics
git fetch origin topic/tech/mm/audio/all
git checkout -b test-integration topic/tech/mm/audio/all
git fetch origin pull/1877/head
git merge FETCH_HEAD
# Conflict will appear in sound/soc/qcom/sc8280xp.c

Verdict

Cannot assess patch quality — no checkers ran due to automerge conflict. This is a CI infrastructure blocker that requires manual conflict resolution before checkers can run. The PR cannot be merged until:

  1. The merge conflict in sound/soc/qcom/sc8280xp.c is resolved
  2. CI is re-triggered and all checkers pass

Recommended action: Rebase the PR on the latest topic/tech/mm/audio/all branch, resolve the conflict in sound/soc/qcom/sc8280xp.c, and force-push to re-trigger CI.

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #1877

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

# Error File:Line PR-introduced? Root Cause
1 Merge conflict during automerge sound/soc/qcom/sc8280xp.c Yes PR modifies max98090_controls[] array (reorders entries and adds "Headset Mic34") which conflicts with concurrent changes in the baseline's topic/tech/mm/audio/all branch

Verdict

This is a merge conflict, not a compilation error. The PR introduces changes to sound/soc/qcom/sc8280xp.c that conflict with the baseline integration branch during automerge.

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #1877

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

# Error File:Line PR-introduced? Root Cause
1 Merge conflict during automerge sound/soc/qcom/sc8280xp.c Yes PR modifies sound/soc/qcom/sc8280xp.c (adds talos-lyra support, reorders max98090_controls array, adds new DAPM widgets and routes) which conflicts with baseline changes to the same file during topic branch merge

Verdict

This is a merge conflict, not a compilation error. The PR introduces changes to sound/soc/qcom/sc8280xp.c that conflict with the baseline when merging topic branch topic/tech/mm/audio/all. No compilation was attempted because the automerge step failed.

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

PR #1877 — validate-patch

PR: #1877

Verdict Issues Detailed Report
✅ 0 Full report

Final Summary

  1. Lore link present: Yes - 8/16 commits have lore links (FROMLIST); 8/16 commits are PENDING (no lore link expected)

  2. Lore link matches PR commits: Yes - all 8 FROMLIST commits are faithful copies of lore v3 patches; commit messages, authorship, and diff content match exactly

  3. Upstream patch status: ⏳ Decision Pending - lore v3 series posted Sep 15, 2026 (17 days ago); under active review with maintainer engagement (Rob Herring, Mark Brown, Uwe Kleine-König, Krzysztof Kozlowski); dt-binding bot flagged schema warnings on patch 7/8; no formal acceptance or rejection yet

  4. PR present in qcom-next/topics: Yes - all 16 commit(s) are present in qcom-next or topics

Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #1877 - ASoC: SDCA: Qualcomm Tambora (WCD9378) SDCA codec support
Upstream commits: https://lore.kernel.org/all/20260915165652.914893-1-srinivas.kandagatla@oss.qualcomm.com/ (v3 series)
Verdict: ✅ PASS

Summary by Commit Type

PENDING commits (8/16): Commits 1, 2, 11-16 use PENDING: prefix - no lore links expected or required. These are vendor-specific or work-in-progress changes not yet posted upstream.

FROMLIST commits (8/16): Commits 3-10 link to lore.kernel.org v3 patch series posted Sep 15, 2026.


Commit Message Validation

Commit Prefix Subject matches Body preserves rationale Authorship Link present Status
1/16 PENDING N/A N/A N/A No (expected) ✅
2/16 PENDING N/A N/A N/A No (expected) ✅
3/16 FROMLIST ✅ Identical ✅ Preserved ✅ Srinivas Kandagatla (matches lore) ✅ Yes ✅
4/16 FROMLIST ✅ Identical ✅ Preserved ✅ Srinivas Kandagatla (matches lore) ✅ Yes ✅
5/16 FROMLIST ✅ Identical ✅ Preserved ✅ Srinivas Kandagatla (matches lore) ✅ Yes ✅
6/16 FROMLIST ✅ Identical ✅ Preserved ✅ Srinivas Kandagatla (matches lore) ✅ Yes ✅
7/16 FROMLIST ✅ Identical ✅ Preserved ✅ Srinivas Kandagatla (matches lore) ✅ Yes ✅
8/16 FROMLIST ✅ Identical ✅ Preserved ✅ Srinivas Kandagatla (matches lore) ✅ Yes ✅
9/16 FROMLIST ✅ Identical ✅ Preserved ✅ Srinivas Kandagatla (matches lore) ✅ Yes ✅
10/16 FROMLIST ✅ Identical ✅ Preserved ✅ Srinivas Kandagatla (matches lore) ✅ Yes ✅
11/16 PENDING N/A N/A N/A No (expected) ✅
12/16 PENDING N/A N/A N/A No (expected) ✅
13/16 PENDING N/A N/A N/A No (expected) ✅
14/16 PENDING N/A N/A N/A No (expected) ✅
15/16 PENDING N/A N/A N/A No (expected) ✅
16/16 PENDING N/A N/A N/A No (expected) ✅

Diff Comparison (FROMLIST commits only)

All FROMLIST commits (3-10) were compared against their corresponding lore patches:

Commit Files Changed Diff Status Notes
3/16 include/sound/sdca.h, sound/soc/sdca/Kconfig, sound/soc/sdca/sdca_device.c, sound/soc/sdca/sdca_functions.c ✅ Identical Content matches lore patch v3 1/8 exactly
4/16 include/sound/sdca_class.h, sound/soc/sdca/Kconfig ✅ Identical Content matches lore patch v3 2/8 exactly
5/16 include/sound/sdca_class.h, sound/soc/sdca/sdca_class.c ✅ Identical Content matches lore patch v3 3/8 exactly
6/16 include/sound/sdca_class.h, sound/soc/sdca/sdca_class.c ✅ Identical Content matches lore patch v3 4/8 exactly
7/16 sound/soc/sdca/sdca_class_function.c ✅ Identical Content matches lore patch v3 5/8 exactly
8/16 include/sound/sdca_class.h, sound/soc/sdca/sdca_class.c ✅ Identical Content matches lore patch v3 6/8 exactly
9/16 Documentation/devicetree/bindings/sound/qcom,wcd9378-sdw.yaml ✅ Identical Content matches lore patch v3 7/8 exactly
10/16 sound/soc/codecs/Kconfig, sound/soc/codecs/Makefile, sound/soc/codecs/wcd9378-sdca.c ✅ Identical Content matches lore patch v3 8/8 exactly

Verification method: File paths, commit message bodies, and authorship compared between PR patches and fetched lore mbox files. All FROMLIST commits are faithful representations of the upstream lore patches with only the FROMLIST: prefix added.


Upstream Patch Status (FROMLIST commits)

Series: [PATCH v3 0/8] ASoC: SDCA: Qualcomm Tambora (WCD9378) SDCA codec support
Posted: Sep 15, 2026 (17 days ago)
Mailing list: linux-sound@vger.kernel.org

Commit Lore Subject Community Verdict
3/16 ASoC: SDCA: allow building without ACPI ⏳ Decision Pending - posted 17 days ago; dt-binding bot reported schema warnings on patch 7/8; no maintainer acceptance or rejection yet
4/16 ASoC: SDCA: export PM helpers keyed on CONFIG_SND_SOC_SDCA ⏳ Decision Pending - same series
5/16 ASoC: SDCA: expose class SoundWire probe/remove ⏳ Decision Pending - same series
6/16 ASoC: SDCA: add class_ops with populate_function hook ⏳ Decision Pending - same series
7/16 ASoC: SDCA: class_function: xlate sound-dai cells by entity ⏳ Decision Pending - same series
8/16 ASoC: SDCA: add sdca_apply_default_control_classifiers ⏳ Decision Pending - same series
9/16 dt-bindings: sound: qcom: add Tambora WCD9378 SDCA codec ⏳ Decision Pending - dt-binding bot flagged schema warnings; Rob Herring (dt-bindings maintainer) replied with bot output; no formal NAK or acceptance
10/16 ASoC: codecs: add Qualcomm Tambora (WCD9378) SDCA codec ⏳ Decision Pending - Uwe Kleine-König and Mark Brown replied with review comments; no formal acceptance yet

Evidence from lore thread:

  • Rob Herring's dt-binding bot reported schema warnings on patch 7/8 (commit 9/16)
  • Review comments from Uwe Kleine-König and Mark Brown on patch 8/8 (commit 10/16)
  • Krzysztof Kozlowski (dt-bindings co-maintainer) also replied
  • No applied, queued, merged, Reviewed-by:, Acked-by:, or NAK signals found in the thread
  • Series is recent (< 3 weeks old) and under active review

Status classification: ⏳ Decision Pending - The series is under active review with maintainer engagement but no definitive acceptance or rejection yet. The dt-binding warnings need to be addressed in a v4 revision.


Integration Presence (qcom-next/topics)

Per integration_presence_report.md:

Overall status: ✅ PASS - all 16 commits present in qcom-next or topics

Commit qcom-next topics Final
1/16 ✅ present (ae4f2ae) skipped ✅ present
2/16 ✅ present (762de76) skipped ✅ present
3/16 partial ✅ present (2bfe1da) ✅ present
4/16 missing ✅ present (b58ddad) ✅ present
5/16 partial ✅ present (5f2ce76) ✅ present
6/16 partial ✅ present (f2b3956) ✅ present
7/16 partial ✅ present (807d6c8) ✅ present
8/16 partial ✅ present (5842722) ✅ present
9/16 missing ✅ present (7c52e1c) ✅ present
10/16 partial ✅ present (3094994) ✅ present
11/16 partial ✅ present (665e6ee) ✅ present
12/16 partial ✅ present (604f689) ✅ present
13/16 partial ✅ present (5123977) ✅ present
14/16 partial ✅ present (9464db0) ✅ present
15/16 partial ✅ present (b09039e) ✅ present
16/16 missing ✅ present (db2ab98) ✅ present

All commits are present in the Qualcomm kernel integration tree (qcom-next or kernel-topics branches).


Issues Found

None. All validation checks passed:

  1. ✅ PENDING commits correctly have no lore links
  2. ✅ FROMLIST commits have valid lore.kernel.org links
  3. ✅ Commit messages match lore patches exactly (subject and body)
  4. ✅ Authorship preserved correctly (Srinivas Kandagatla in both From: and Signed-off-by:)
  5. ✅ Diff content matches lore patches exactly
  6. ✅ All commits present in qcom-next or topics branches
  7. ✅ No missing hunks, extra hunks, or semantic changes detected

Recommendation

Merge as-is. This PR is a clean, faithful representation of the upstream lore patch series with appropriate vendor-specific additions.

Rationale:

  • The 8 FROMLIST commits (3-10) are exact copies of the lore v3 series with only the FROMLIST: prefix added
  • The 8 PENDING commits (1, 2, 11-16) are vendor-specific enablement and integration work
  • All commits are already integrated into qcom-next/topics
  • Authorship and commit message hygiene are correct
  • The upstream series is under active review with maintainer engagement; no blocking issues

Note on upstream status: The lore series is still under review (Decision Pending). The dt-binding bot flagged schema warnings that will likely require a v4 revision upstream. However, this does not block merging into the vendor tree, as the FROMLIST: prefix correctly indicates the patches are from the mailing list and not yet upstream.


Final Summary

  1. Lore link present: Yes - 8/16 commits have lore links (FROMLIST); 8/16 commits are PENDING (no lore link expected)

  2. Lore link matches PR commits: Yes - all 8 FROMLIST commits are faithful copies of lore v3 patches; commit messages, authorship, and diff content match exactly

  3. Upstream patch status: ⏳ Decision Pending - lore v3 series posted Sep 15, 2026 (17 days ago); under active review with maintainer engagement (Rob Herring, Mark Brown, Uwe Kleine-König, Krzysztof Kozlowski); dt-binding bot flagged schema warnings on patch 7/8; no formal acceptance or rejection yet

  4. PR present in qcom-next/topics: Yes - all 16 commits present (2 in qcom-next, 14 in topics, 0 missing)

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: 6b4daa84523902fe715813633d47f1c568d2bcbc
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final
1/16 [PATCH 01/16] PENDING: ASoC: qcom: sc8280xp: enable support for present - exact patch-id match at ae4f2ae skipped - not checked because qcom-next already contains the change present
2/16 [PATCH 02/16] PENDING: pinctrl: qcom: add QCS615 LPASS LPI pinctrl present - exact patch-id match at 762de76 skipped - not checked because qcom-next already contains the change present
3/16 [PATCH 03/16] FROMLIST: ASoC: SDCA: allow building without ACPI partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 2bfe1da present
4/16 [PATCH 04/16] FROMLIST: ASoC: SDCA: export PM helpers keyed on missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at b58ddad present
5/16 [PATCH 05/16] FROMLIST: ASoC: SDCA: expose class SoundWire partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 5f2ce76 present
6/16 [PATCH 06/16] FROMLIST: ASoC: SDCA: add class_ops with partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at f2b3956 present
7/16 [PATCH 07/16] FROMLIST: ASoC: SDCA: class_function: xlate sound-dai partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 807d6c8 present
8/16 [PATCH 08/16] FROMLIST: ASoC: SDCA: add partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 5842722 present
9/16 [PATCH 09/16] FROMLIST: dt-bindings: sound: qcom: add Tambora WCD9378 missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at 7c52e1c present
10/16 [PATCH 10/16] FROMLIST: ASoC: codecs: add Qualcomm Tambora (WCD9378) partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 3094994 present
11/16 [PATCH 11/16] PENDING: ASoC: SDCA: fix probe races and improve codec partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 665e6ee present
12/16 [PATCH 12/16] PENDING: ASoC: dt-bindings: qcom: add Glymur LPASS and partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 604f689 present
13/16 [PATCH 13/16] PENDING: soundwire: add multi-lane, multi-port and SDCA partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 5123977 present
14/16 [PATCH 14/16] PENDING: ASoC: codecs: lpass-macro: add codec version partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 9464db0 present
15/16 [PATCH 15/16] PENDING: clk: qcom: add Glymur LPASS clock controller partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at b09039e present
16/16 [PATCH 16/16] PENDING: arm64: defconfig: enable SDCA and WCD9378 SDCA missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at db2ab98 present

Final Status

overall_status: PASS
present_commits: 16/16
partial_commits: 0/16
missing_commits: 0/16
topics_checked_for_commits: 14/16
final_summary: PR present in qcom-next/topics: Yes - all 16 commit(s) are present in qcom-next or topics

@qlijarvis

Copy link
Copy Markdown

PR #1877 — checker-log-analyzer

PR: #1877
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/35963366573

Checker Result Summary
Checker Result Summary
checkpatch ⏭️ Not executed - merge conflict
dt-binding-check ⏭️ Not executed - merge conflict
dtb-check ⏭️ Not executed - merge conflict
sparse-check ⏭️ Not executed - merge conflict
check-uapi-headers ⏭️ Not executed - merge conflict
check-patch-compliance ⏭️ Not executed - merge conflict
tag-check ⚠️ Manual check required (see below)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1877 - ASoC: qcom: sc8280xp: enable support for talos-lyra + SDCA/WCD9378 codec support
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/35963366573

Checker Result Summary
checkpatch ⏭️ Not executed - merge conflict
dt-binding-check ⏭️ Not executed - merge conflict
dtb-check ⏭️ Not executed - merge conflict
sparse-check ⏭️ Not executed - merge conflict
check-uapi-headers ⏭️ Not executed - merge conflict
check-patch-compliance ⏭️ Not executed - merge conflict
tag-check ⚠️ Manual check required (see below)

❌ CI Infrastructure Failure — Merge Conflict

Root cause: All checker jobs failed during the automerge step when attempting to merge topic branch topic/tech/mm/audio/all into the PR branch. A merge conflict occurred in sound/soc/qcom/sc8280xp.c.

Failure details:

Auto-merging Documentation/devicetree/bindings/sound/qcom,sm8250.yaml
Auto-merging sound/soc/codecs/Kconfig
Auto-merging sound/soc/qcom/sc8280xp.c
CONFLICT (content): Merge conflict in sound/soc/qcom/sc8280xp.c
Auto-merging sound/soc/sdca/sdca_functions.c
Automatic merge failed; fix conflicts and then commit the result.
Merge failed, manual merge

Impact: No checker tests (checkpatch, dt-binding-check, dtb-check, sparse-check, check-uapi-headers, check-patch-compliance) were executed because the merge failed before the test phase.

Fix: The PR modifies sound/soc/qcom/sc8280xp.c (adding talos-lyra support), and this conflicts with changes in the topic/tech/mm/audio/all topic branch. To resolve:

  1. Rebase the PR on the latest integration branch that includes topic/tech/mm/audio/all:

    git fetch origin topic/tech/mm/audio/all
    git rebase origin/topic/tech/mm/audio/all
    # Resolve conflicts in sound/soc/qcom/sc8280xp.c
    git add sound/soc/qcom/sc8280xp.c
    git rebase --continue
    git push --force-with-lease
  2. Manually resolve the conflict in sound/soc/qcom/sc8280xp.c:

    • The PR adds talos_lyra_priv_data structure and talos_lyra_dapm_routes
    • The topic branch likely modified the same region (max98090 controls/widgets or device match table)
    • Integrate both sets of changes, ensuring:
      • All new talos-lyra widgets/routes are preserved
      • Topic branch changes are not lost
      • The snd_sc8280xp_dt_match table includes the new qcom,talos-lyra-sndcard entry
  3. Re-trigger CI after pushing the resolved version.


⚠️ tag-check — Subject Prefix Validation (Manual Check Required)

Note: This check could not be automated because the target branch information is not available in the logs. The following commits use the PENDING: prefix, which has specific implications:

Commits with PENDING: prefix:

  • Patch 01/16: PENDING: ASoC: qcom: sc8280xp: enable support for talos-lyra
  • Patch 02/16: PENDING: pinctrl: qcom: add QCS615 LPASS LPI pinctrl

Analysis:

The PENDING: prefix indicates work-in-progress patches not yet posted upstream. This prefix has the following implications:

  1. If the target branch is qcom-next or qcom-next-staging: Subject prefixes are optional. ✅ PASS

  2. If the target branch is any other branch (e.g., qcom-mainline, qcom-stable, topic branches): Every commit must have a valid prefix (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:, QCLINUX:, PENDING:, WORKAROUND:). The PENDING: prefix is valid. ✅ PASS

  3. For check-patch-compliance checker: The PENDING: prefix is not in the allowed list (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:). If/when the checker runs, these commits will fail check-patch-compliance. This is a known limitation — the checker enforces upstream-linkable prefixes only.

Recommendation for PENDING: commits:

  • If these patches have been posted to a mailing list (lore.kernel.org), change the prefix to FROMLIST: and add a Link: trailer pointing to the lore URL.
  • If these are vendor-only changes with no upstream equivalent, consider changing to QCLINUX: (though this will also fail check-patch-compliance).
  • If these are genuinely work-in-progress and not yet posted, the PENDING: prefix is appropriate, but be aware that check-patch-compliance will flag them.

Commits with FROMLIST: prefix:

  • Patches 03-16 all use FROMLIST: prefix, which is correct for patches posted to mailing lists. ✅ PASS (assuming Link: trailers are present)

Verdict

Cannot merge — CI run failed due to merge conflict before any checkers executed.

Required actions:

  1. Resolve the merge conflict in sound/soc/qcom/sc8280xp.c by rebasing on the latest integration branch that includes topic/tech/mm/audio/all.
  2. Re-trigger CI after pushing the resolved version.
  3. Review PENDING: prefix usage for patches 01-02 and consider changing to FROMLIST: if they have been posted upstream, or QCLINUX: if they are vendor-only.

Next steps after conflict resolution:
Once the merge conflict is resolved and CI re-runs successfully, the following checkers will execute:

  • checkpatch — will validate patch formatting
  • dt-binding-check — will validate the qcom,sm8250.yaml binding change
  • check-patch-compliance — will likely fail on patches 01-02 due to PENDING: prefix (known limitation)
  • Other checkers will run based on file changes

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