Skip to content

Hawi support - #1933

Merged
mohsRafi merged 15 commits into
qualcomm-linux:tech/mm/audio/allfrom
PrasadKumpatla:hawi_support
Oct 1, 2026
Merged

mohsRafi merged 15 commits into
qualcomm-linux:tech/mm/audio/allfrom
PrasadKumpatla:hawi_support

Conversation

@PrasadKumpatla

Copy link
Copy Markdown

Hawi/Maili Audio Support enabled.

@qcomlnxci
qcomlnxci requested review from a team and mohsRafi and removed request for a team September 29, 2026 10:59
PrasadKumpatla and others added 15 commits September 30, 2026 10:42
Add support for the Qualcomm Maili SoC to the protection
domain mapper. Maili shares the same protection domain
configuration as Kaanapali, so reuse the existing
Kaanapali domain data.

Link: https://lore.kernel.org/all/20260819054203.61385-3-prasad.kumpatla@oss.qualcomm.com/
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
…playback

During back-to-back speaker playback the PA sometimes fails to enable
because a few I2S/TDM and clock source registers retain their previous
state and are not reprogrammed on the next stream.

Reset the relevant I2S/TDM, clock source and bandgap override registers
in hw_free() so the codec is torn down cleanly and the speaker amplifier
comes up reliably on back-to-back use cases. Move the bandgap override
reset out of set_sysclk() into the teardown path where it belongs.

Link: https://patch.msgid.link/20260923084627.748920-2-prasad.kumpatla@oss.qualcomm.com
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Maili ships its own firmware, so its topology file has to live in a
separate maili/ firmware directory. The topology load path is derived
from the sound card driver_name, so reusing the Hawi data would look
up the topology under hawi/ instead.

Add a dedicated maili_priv_data with driver_name "maili" for the
qcom,maili-sndcard compatible so the topology is loaded from the maili/
directory. It keeps the same DAPM widgets and enables codec sysclk,
MI2S BCLK and WCD jack detection for the Maili audio pipeline.

Link: https://patch.msgid.link/20260923084627.748920-3-prasad.kumpatla@oss.qualcomm.com
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Add compatibles for the RX, TX and VA macro codecs found in the Low
Power Audio SubSystem (LPASS) of the Qualcomm Maili SoC.

The Maili RX, TX and VA macros are identical to their Hawi counterparts,
so document them with the corresponding Hawi compatible as fallback.

Link: https://patch.msgid.link/20260923084627.748920-4-prasad.kumpatla@oss.qualcomm.com
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
…clock

Add a binding for the Qualcomm LPASS VA CSR rate generator node that
exposes the lpass_heartbeat_pulse clock on Hawi.

The HeartBeat Pulse, also known as RateGen Pulse, synchronizes the
start of DMAs and Codec Interfaces for the audio usecase and can serve
as a periodic wakeup source for the DSP.

Require the LPASS LPR and audio vote clocks to access VA CSR register
space safely.

Signed-off-by: Sarath Ganapathiraju <sarath.ganapathiraju@oss.qualcomm.com>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
Link: https://patch.msgid.link/20260928-master-v9-1-2277f09f9a09@oss.qualcomm.com
The HeartBeat Pulse, also known as RateGen Pulse, synchronizes the
start of DMAs and Codec Interfaces for the audio usecases and can
serve as a periodic wakeup source for the DSP.

Add the LPASS VA CSR driver that models the rate generator as a clock
provider so consumers can enable and disable it through the common
clock framework.

Attach the DT vote clocks to runtime PM and resume the device before
programming the rate generator registers in probe. Also take a runtime
PM reference from the clock prepare path so later enable and disable
register accesses happen only while the LPASS votes are active.

Signed-off-by: Sarath Ganapathiraju <sarath.ganapathiraju@oss.qualcomm.com>
Link: https://patch.msgid.link/20260928-master-v9-2-2277f09f9a09@oss.qualcomm.com
…ring

LPASS_CODEC_VERSION_2_9 is detected by lpass-va-macro.c and consumed by
lpass-wsa-macro.c, but lpass_macro_get_codec_version_string() never
learned about it, so the probe log reports "LPASS Codec Version NA" on
those parts.

Add the missing case.

Reviewed-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Reviewed-by: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>
Link: https://patch.msgid.link/20260922-add_shikra_support-v1-2-6c6cb6444caf@oss.qualcomm.com
Document compatibles for the RX, TX and VA macro codecs found in the
Low Power Audio SubSystem (LPASS) of the Qualcomm Hawi SoC.

All three macros differ from SM8550, so describe them as standalone
compatibles with their own clock constraints rather than as SM8550
fallbacks: the RX macro uses the 'lpr' clock instead of the 'macro'
clock, the TX macro is based on Bolero v4.0, and the VA macro takes an
additional "heartbeatpulse" clock sourced from the LPASS VA CSR rate
generator.

Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Link: https://patch.msgid.link/20260922-add_shikra_support-v1-6-6c6cb6444caf@oss.qualcomm.com
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Hawi integrates the Bolero v4.0 TX macro, which extends the v9.x TX
macro with a port-select stage in the SWR microphone input path and an
adaptive filter (ADPT) block.

Add the additional CFG2 mux registers and per-path CFG2 registers to the
register map, extend the maximum register offset to cover the new ADPT
control register, and describe the new v4.0 decimator, SWR microphone,
WSA and port-select mux widgets and their routes.

The ADPT block has to be disabled before a decimator is enabled. This
register only exists on v4.0, so gate the write on a has_adpt flag set
from the match data rather than issuing it unconditionally.

Add the "qcom,hawi-lpass-tx-macro" compatible and its match data to
select the new widgets and routes.

Co-developed-by: Sarath Ganapathiraju <sarath.ganapathiraju@oss.qualcomm.com>
Signed-off-by: Sarath Ganapathiraju <sarath.ganapathiraju@oss.qualcomm.com>
Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Link: https://patch.msgid.link/20260922-add_shikra_support-v1-7-6c6cb6444caf@oss.qualcomm.com
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Hawi and Maili use the LPASS codec v4.0, which the macro drivers do not
yet recognise.

Add LPASS_CODEC_VERSION_4_0 and its "v4.0" version string, and detect it
in the VA macro when the hardware reports major version 4, minor 0.

The RX macro register layout of LPASS codec v4.0 matches the v2.5+
layout, so reuse the existing v2.5 register access helpers, controls,
widgets and register defaults for it. Unlike v4.1, v4.0 does not need
the FS counter bypass or the adaptive filter blocks, so those stay keyed
off v4.1 only.

Add the "qcom,hawi-lpass-rx-macro" and "qcom,hawi-lpass-va-macro"
compatibles, both pointing at the sm8550 match data, so the version is
read back from the hardware at probe.

Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Link: https://patch.msgid.link/20260922-add_shikra_support-v1-8-6c6cb6444caf@oss.qualcomm.com
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Add new dai ids entries for Qualcomm Audio Interface (QAIF) AIF MI2S
and TDM audio lines.

Co-developed-by: Harendra Gautam <harendra.gautam@oss.qualcomm.com>
Signed-off-by: Harendra Gautam <harendra.gautam@oss.qualcomm.com>
Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Reviewed-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Tested-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Link: https://patch.msgid.link/20260918-qaif_dai_id_support-v1-1-ed863c0e5e45@oss.qualcomm.com
…2S and TDM dais

Add support for Qualcomm Audio Interface (QAIF) AIF MI2S and TDM dais in
the dai-driver, these dais are used in Shikra, Hawi and Nord based
Qualcomm platform devices.

Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Reviewed-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Reviewed-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Tested-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Link: https://patch.msgid.link/20260918-qaif_dai_id_support-v1-2-ed863c0e5e45@oss.qualcomm.com
Handle AIF MI2S and TDM DAI IDs in the SC8280XP machine driver
and extend LPASS_MAX_PORT to accommodate the additional audio
interfaces.

Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Reviewed-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Reviewed-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Tested-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Link: https://patch.msgid.link/20260918-qaif_dai_id_support-v1-3-ed863c0e5e45@oss.qualcomm.com
… LPI pinctrl

Add bindings for the pin controller in Low Power Audio SubSystem (LPASS)
of Qualcomm Hawi SoC.

The controller has 23 GPIOs (gpio0-gpio22) with functions including
SoundWire, I2S, DMIC, VA I2S, ext_mclk1, slimbus and lpass_lpi_dbg_clk.

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Link: https://patch.msgid.link/20260821113548.2686650-2-prasad.kumpatla@oss.qualcomm.com
Add pin controller driver for the Low Power Audio SubSystem (LPASS)
Low Power Island (LPI) of Qualcomm Hawi SoC.

The controller has 23 GPIOs with SoundWire, I2S, DMIC, VA I2S,
ext_mclk1 and slimbus mux functions.

Two pins (gpio13, gpio22) require 6 mux slots due to a test_bus
entry occupying a middle hardware slot. Add LPI_PINGROUP6 macro
to pinctrl-lpass-lpi.h to support pins with 5 alternate functions.

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
Link: https://patch.msgid.link/20260821113548.2686650-3-prasad.kumpatla@oss.qualcomm.com
@mohsRafi
mohsRafi merged commit 6713b47 into qualcomm-linux:tech/mm/audio/all Oct 1, 2026
4 of 7 checks passed
@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #1933

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

# Error File:Line PR-introduced? Root Cause
1 Merge conflict during automerge Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml No Pre-existing conflict - file not modified by PR
2 Merge conflict during automerge drivers/gpu/drm/msm/dp/dp_display.c No Pre-existing conflict - file not modified by PR
3 Merge conflict during automerge drivers/soundwire/qcom.c No Pre-existing conflict - file not modified by PR
4 Merge conflict during automerge sound/soc/codecs/Kconfig No Pre-existing conflict - file not modified by PR
5 Merge conflict during automerge sound/soc/codecs/adau1977-i2c.c No Pre-existing conflict - file not modified by PR
6 Merge conflict during automerge sound/soc/codecs/lpass-rx-macro.c Possibly PR adds codec version cases; conflict may be related to PR changes
7 Merge conflict during automerge sound/soc/qcom/sc8280xp.c Possibly PR adds maili_priv_data struct and AIF_MI2S/AIF_TDM ranges; conflict may be related to PR changes

Verdict

This is NOT a compilation failure. The build failed during the automerge phase when attempting to merge the PR branch topic/tech/mm/audio/all into the integration branch. 7 merge conflicts were encountered. 5 of 7 conflicts are in files NOT modified by this PR and are pre-existing integration issues. 2 of 7 conflicts are in files modified by the PR (lpass-rx-macro.c and sc8280xp.c) and may be partially caused by this PR's changes conflicting with other topic branches in the integration.

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #1933

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

# Error File:Line PR-introduced? Root Cause
1 Merge conflict Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml No Pre-existing conflict with qcom-next baseline - file not modified by PR
2 Merge conflict drivers/gpu/drm/msm/dp/dp_display.c No Pre-existing conflict with qcom-next baseline - file not modified by PR
3 Merge conflict drivers/soundwire/qcom.c No Pre-existing conflict with qcom-next baseline - file not modified by PR
4 Merge conflict sound/soc/codecs/Kconfig No Pre-existing conflict with qcom-next baseline - file not modified by PR
5 Merge conflict sound/soc/codecs/adau1977-i2c.c No Pre-existing conflict with qcom-next baseline - file not modified by PR
6 Merge conflict sound/soc/codecs/lpass-rx-macro.c Yes PR adds LPASS_CODEC_VERSION_4_0/4_1 case statements that conflict with parallel changes in qcom-next
7 Merge conflict sound/soc/qcom/sc8280xp.c Yes PR adds maili_priv_data structure and modifies device match table, conflicts with parallel changes in qcom-next

Verdict

2 of 7 merge conflicts are introduced by this PR; 5 are pre-existing. The build failed during automerge before compilation started - no compilation errors exist.

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

PR #1933 — validate-patch

PR: #1933

Verdict Issues Detailed Report
⚠️ 3 Full report

Final Summary

  1. Lore link present: Yes - all 15 commits have lore.kernel.org links in Link: tags
  2. Lore link matches PR commits: Commit 1: Yes - diff identical to lore; Commits 2-15: Unknown - lore evidence not fetched (cannot verify without mbox files)
  3. Upstream patch status: Commit 1: ⏳ Decision Pending - Reviewed-by present, no merge confirmation; Commits 2-15: Unknown - cannot determine without lore thread analysis
  4. PR present in qcom-next/topics: Yes - all 15 commit(s) are present in qcom-next or topics
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1933 - Add Maili SoC support (15 commits)
Upstream commits: Multiple lore.kernel.org links (see per-commit analysis below)
Verdict: ⚠️ PARTIAL

Summary

This PR contains 15 FROMLIST: commits adding Maili SoC support. Only commit 1/15 has fetched lore evidence available for full validation. The remaining 14 commits have lore links but no fetched mbox files for detailed comparison. However, the integration presence report confirms all 15 commits are present in qcom-next or kernel topics branches.


Per-Commit Analysis

Commit 1/15: FROMLIST: soc: qcom: pd-mapper: Add support for Maili SoC

Lore link: https://lore.kernel.org/all/20260819054203.61385-3-prasad.kumpatla@oss.qualcomm.com/
Status: ✅ Fully validated with fetched lore evidence

Check Status Note
Subject matches upstream ✅ Identical except for FROMLIST: prefix
Body preserves rationale ✅ Commit message identical to lore patch
Fixes tag present/correct N/A No Fixes tag in upstream or PR
Authorship preserved ✅ From: matches lore author (Prasad Kumpatla)
Backport note N/A Not a backport - FROMLIST: prefix correct
Link tag present ✅ Correct lore link in commit message
Reviewed-by preserved ✅ Reviewed-by: Konrad Dybcio present in both

Diff Comparison:

File Status Notes
drivers/soc/qcom/qcom_pd_mapper.c ✅ Identical - adds one line for qcom,maili compatible

Upstream Status: ⏳ Decision Pending - Reviewed-by present from Konrad Dybcio (subsystem maintainer), but no merge confirmation found in lore thread. Thread contains NAK discussion about a different patch in the series (dt-bindings patch 1/2), not this pd-mapper patch (2/2).

Integration Presence: ✅ Present in topics branch at 93b3043fb15b3a75f3bf76b6c6eb562ce6e60a4b


Commits 2-15: Various FROMLIST patches

Lore links: Present for all commits (see PR patch for individual links)
Status: ⚠️ Limited validation - no fetched lore evidence available

Common observations across commits 2-15:

  • All use FROMLIST: prefix correctly
  • All have Link: tags pointing to lore.kernel.org
  • Authors vary: Prasad Kumpatla, Sarath Ganapathiraju, Mohammad Rafi Shaik
  • All have Signed-off-by: from the commit author
  • Commit messages appear well-formatted with proper subject/body structure

Integration Presence: ✅ All 15 commits present in qcom-next or topics branches (see integration_presence_report.md for details)

Commit Subject Integration Status
2/15 ASoC: codecs: wsa885x: Reset registers ✅ Present at 62dbd8c2f257
3/15 ASoC: qcom: sc8280xp: add Maili sound card ✅ Present at 0b15747087e2
4/15 ASoC: dt-bindings: qcom: Add Maili LPASS ✅ Present at 13c94bc17811
5/15 dt-bindings: clock: qcom: Add LPASS VA CSR ✅ Present at 5a107002dce9
6/15 clk: qcom: Add LPASS VA CSR heartbeat pulse ✅ Present at 33a82daec023
7/15 ASoC: qcom: lpass-macro-common: Add missing ✅ Present at 27cf083ae6b2
8/15 ASoC: dt-bindings: qcom: Add Hawi LPASS macro ✅ Present at 230500035f56
9/15 ASoC: qcom: lpass-tx-macro: Add support for ✅ Present at 4cdd3d811aa2
10/15 ASoC: qcom: lpass: Add support for LPASS ✅ Present at ed3440ca6b6d
11/15 ASoC: dt-bindings: qcom: add QAIF AIF MI2S ✅ Present at fd9f0d9e76b7
12/15 ASoC: qcom: qdsp6: lpass-ports: add support ✅ Present at ff1ca128edd7
13/15 ASoC: qcom: sc8280xp: Handle AIF MI2S and TDM ✅ Present at qcom-next
14/15 dt-bindings: pinctrl: ✅ Present at 5f50e9f2757e
15/15 pinctrl: qcom: hawi-lpass-lpi: add Hawi LPASS ✅ Present at 6713b47b8cca

Issues

Commit 1/15:

  • No issues found - patch faithfully represents lore upstream

Commits 2-15:

  • ⚠️ Limited validation scope: Lore evidence not fetched for these commits. Cannot verify:

    • Exact diff match with upstream lore patches
    • Upstream acceptance status (merged/pending/rejected)
    • Whether commit messages preserve all upstream details
  • ✅ Mitigating factors:

    • All commits present in qcom-next/topics (verified by integration presence report)
    • All have proper FROMLIST: prefix and lore links
    • Commit message structure appears correct
    • Authorship and sign-off chains present

Verdict

Commit 1/15: ✅ Merge as-is - fully validated against lore, diff identical, commit message correct

Commits 2-15: ⚠️ Conditionally approve - all commits are present in qcom-next/topics branches, suggesting they have been reviewed and integrated. However, without fetched lore evidence, detailed validation of diff content and upstream status cannot be performed. The presence in integration branches provides strong evidence of correctness.

Overall recommendation: The PR can be merged based on:

  1. Commit 1 is fully validated and correct
  2. All 15 commits are already present in qcom-next or topics branches
  3. All commits follow proper FROMLIST: conventions with lore links
  4. No obvious commit message or authorship issues detected

For higher confidence, consider fetching lore evidence for commits 2-15 to perform full diff validation.


Final Summary

  1. Lore link present: Yes - all 15 commits have lore.kernel.org links in Link: tags
  2. Lore link matches PR commits: Commit 1: Yes - diff identical to lore; Commits 2-15: Unknown - lore evidence not fetched (cannot verify without mbox files)
  3. Upstream patch status: Commit 1: ⏳ Decision Pending - Reviewed-by present, no merge confirmation; Commits 2-15: Unknown - cannot determine without lore thread analysis
  4. PR present in qcom-next/topics: Yes - all 15 commits present (verified by integration_presence_report.md)

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: ba86f67908354f41f269ca1d64b22e4624766dcf
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final
1/15 [PATCH 01/15] FROMLIST: soc: qcom: pd-mapper: Add support for Maili missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at 93b3043 present
2/15 [PATCH 02/15] FROMLIST: ASoC: codecs: wsa885x: Reset registers on partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 62dbd8c present
3/15 [PATCH 03/15] FROMLIST: ASoC: qcom: sc8280xp: add Maili sound card partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 0b15747 present
4/15 [PATCH 04/15] FROMLIST: ASoC: dt-bindings: qcom: Add Maili LPASS partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 13c94bc present
5/15 [PATCH 05/15] FROMLIST: dt-bindings: clock: qcom: Add LPASS VA CSR missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at 5a10700 present
6/15 [PATCH 06/15] FROMLIST: clk: qcom: Add LPASS VA CSR heartbeat pulse partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 33a82da present
7/15 [PATCH 07/15] FROMLIST: ASoC: qcom: lpass-macro-common: Add missing present - exact patch-id match at 27cf083 skipped - not checked because qcom-next already contains the change present
8/15 [PATCH 08/15] FROMLIST: ASoC: dt-bindings: qcom: Add Hawi LPASS macro partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 2305000 present
9/15 [PATCH 09/15] FROMLIST: ASoC: qcom: lpass-tx-macro: Add support for partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 4cdd3d8 present
10/15 [PATCH 10/15] FROMLIST: ASoC: qcom: lpass: Add support for LPASS partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at ed3440c present
11/15 [PATCH 11/15] FROMLIST: ASoC: dt-bindings: qcom: add QAIF AIF MI2S partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at fd9f0d9 present
12/15 [PATCH 12/15] FROMLIST: ASoC: qcom: qdsp6: lpass-ports: add support partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at ff1ca12 present
13/15 [PATCH 13/15] FROMLIST: ASoC: qcom: sc8280xp: Handle AIF MI2S and TDM present - all checked added lines are present skipped - not checked because qcom-next already contains the change present
14/15 [PATCH 14/15] FROMLIST: dt-bindings: pinctrl: missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at 5f50e9f present
15/15 [PATCH 15/15] FROMLIST: pinctrl: qcom: hawi-lpass-lpi: add Hawi LPASS partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 6713b47 present

Final Status

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

@qlijarvis

Copy link
Copy Markdown

PR #1933 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ⚠️ CI infrastructure failure - automerge conflicts
dt-binding-check ⚠️ CI infrastructure failure - automerge conflicts
dtb-check ⚠️ CI infrastructure failure - automerge conflicts
sparse-check ⚠️ CI infrastructure failure - automerge conflicts
check-uapi-headers ⚠️ CI infrastructure failure - automerge conflicts
check-patch-compliance ⚠️ CI infrastructure failure - automerge conflicts
tag-check ✅ All 15 commits have valid FROMLIST: prefix
qcom-next-check ✅ All commits are FROMLIST: with proper Link: tags

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1933 - FROMLIST: ASoC: qcom: Add Maili LPASS support (15 commits)
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/36558984875

Checker Result Summary
checkpatch ⚠️ CI infrastructure failure - automerge conflicts
dt-binding-check ⚠️ CI infrastructure failure - automerge conflicts
dtb-check ⚠️ CI infrastructure failure - automerge conflicts
sparse-check ⚠️ CI infrastructure failure - automerge conflicts
check-uapi-headers ⚠️ CI infrastructure failure - automerge conflicts
check-patch-compliance ⚠️ CI infrastructure failure - automerge conflicts
tag-check ✅ All 15 commits have valid FROMLIST: prefix
qcom-next-check ✅ All commits are FROMLIST: with proper Link: tags

⚠️ CI Infrastructure Failure — Automerge Conflicts

Root cause: The kernel-checkers CI workflow failed during the automerge step when attempting to merge topic/tech/mm/audio/all into the integration branch. This is a CI infrastructure issue, not a patch quality problem.

Failure details:

Merging topic branch: topic/tech/mm/audio/all
CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml
CONFLICT (content): Merge conflict in drivers/gpu/drm/msm/dp/dp_display.c
CONFLICT (content): Merge conflict in drivers/soundwire/qcom.c
CONFLICT (content): Merge conflict in sound/soc/codecs/Kconfig
CONFLICT (content): Merge conflict in sound/soc/codecs/adau1977-i2c.c
CONFLICT (content): Merge conflict in sound/soc/codecs/lpass-rx-macro.c
CONFLICT (content): Merge conflict in sound/soc/qcom/sc8280xp.c
Automatic merge failed; fix conflicts and then commit the result.
automerge returned non-zero; check logs for conflicts
##[error]Process completed with exit code 1.

Analysis:

The CI workflow attempts to merge the PR branch with the baseline integration branch (topic/tech/mm/audio/all) before running checkers. This merge encountered conflicts in 7 files, all related to audio/soundwire subsystems. The conflicts prevented the CI from proceeding to the actual checker steps (checkpatch, dt-binding-check, etc.).

Important: None of the actual code quality checkers ran. The failure occurred during the pre-check integration step, which means:

  • No checkpatch analysis was performed
  • No DT binding validation was performed
  • No DTB validation was performed
  • No sparse static analysis was performed
  • No UAPI/ABI checks were performed
  • No patch compliance checks were performed

What this means:

This is not a patch defect. The PR patches themselves may be perfectly valid. The failure indicates that the PR branch has diverged from the integration baseline and cannot be automatically merged with other pending audio topic branches.

Fix:

This requires one of the following actions:

  1. Rebase the PR on the latest integration baseline to resolve conflicts:

    git fetch origin
    git rebase origin/main  # or the appropriate baseline branch
    # resolve conflicts
    git push --force-with-lease
  2. Wait for the conflicting topic branch (topic/tech/mm/audio/all) to be merged first, then rebase this PR.

  3. Manually resolve conflicts with the integration branch and update the PR.

  4. Re-trigger CI after the baseline has been updated (if conflicts were due to stale baseline).

Reproduce locally:

To reproduce the automerge conflict locally:

git clone https://github.com/qualcomm-linux/kernel-topics.git
cd kernel-topics
git checkout <PR-branch>
git fetch origin topic/tech/mm/audio/all
git merge origin/topic/tech/mm/audio/all
# Conflicts will appear in the 7 files listed above

✅ Manual Checks Passed

tag-check: All 15 commits have the required FROMLIST: subject prefix.

qcom-next-check: All commits include proper Link: tags pointing to lore.kernel.org, indicating they have been posted upstream.

Sample commits:

  • FROMLIST: soc: qcom: pd-mapper: Add support for Maili SoC
  • FROMLIST: ASoC: codecs: wsa885x: Reset registers on teardown for B2B playback
  • FROMLIST: ASoC: qcom: sc8280xp: add Maili sound card configuration
  • FROMLIST: ASoC: dt-bindings: qcom: Add Maili LPASS macro bindings
  • FROMLIST: pinctrl: qcom: hawi-lpass-lpi: add Hawi LPASS LPI pinctrl driver

All commits follow the required format with FROMLIST: prefix and include Link: tags to upstream mailing list posts.

Verdict

Cannot assess patch quality — CI infrastructure failure prevented all code quality checkers from running. The PR requires rebase/conflict resolution with the integration baseline before checkers can execute. Once conflicts are resolved and CI is re-triggered, a full checker analysis can be performed.

Action required: Rebase PR on latest baseline to resolve automerge conflicts, then re-run CI.

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #1933

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

# Error File:Line PR-introduced? Root Cause
1 Merge conflict during automerge sound/soc/codecs/lpass-rx-macro.c Yes PR modifies this file; conflicts with baseline changes during topic branch integration
2 Merge conflict during automerge sound/soc/qcom/sc8280xp.c Yes PR modifies this file; conflicts with baseline changes during topic branch integration
3 Merge conflict during automerge Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml No Pre-existing conflict; PR does not modify this file
4 Merge conflict during automerge drivers/gpu/drm/msm/dp/dp_display.c No Pre-existing conflict; PR does not modify this file
5 Merge conflict during automerge drivers/soundwire/qcom.c No Pre-existing conflict; PR does not modify this file
6 Merge conflict during automerge sound/soc/codecs/Kconfig No Pre-existing conflict; PR does not modify this file
7 Merge conflict during automerge sound/soc/codecs/adau1977-i2c.c No Pre-existing conflict; PR does not modify this file

Verdict

2 of 7 merge conflicts are introduced by this PR; 5 are pre-existing integration conflicts in the baseline.

Note: This is not a compilation failure. The build failed during the automerge step when integrating topic branch topic/tech/mm/audio/all into baseline e428097a36d210c50991063f17ee0848e9eb68a8. No compilation was attempted.

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #1933

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

Build Status: ❌ Automerge Failure (No Compilation Attempted)

The build failed during the automerge phase when attempting to integrate the PR with the baseline branch topic/tech/mm/audio/all. The kernel was never compiled because merge conflicts prevented the integration from completing.

# Conflicting File PR-introduced? Root Cause
1 Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml No Pre-existing conflict between baseline and topic branch
2 drivers/gpu/drm/msm/dp/dp_display.c No Pre-existing conflict between baseline and topic branch
3 drivers/soundwire/qcom.c No Pre-existing conflict between baseline and topic branch
4 sound/soc/codecs/Kconfig No Pre-existing conflict between baseline and topic branch
5 sound/soc/codecs/adau1977-i2c.c No Pre-existing conflict between baseline and topic branch
6 sound/soc/codecs/lpass-rx-macro.c Possibly PR modifies this file; conflict may be PR-related
7 sound/soc/qcom/sc8280xp.c Possibly PR modifies this file; conflict may be PR-related

Verdict

0 of 7 merge conflicts are definitively caused by this PR. The build failure is primarily due to pre-existing conflicts in the baseline integration branch (topic/tech/mm/audio/all) that are unrelated to the PR changes. Two files (lpass-rx-macro.c and sc8280xp.c) are modified by the PR and also have conflicts, but the conflicts may be due to overlapping changes in the topic branch rather than issues introduced by the PR itself.

This is NOT a compilation error — the kernel build never started because the automerge step failed first.

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

PR #1933 — validate-patch

PR: #1933

Verdict Issues Detailed Report
⚠️ 0 Full report

Final Summary

  1. Lore link present: Yes for all 15 commits - all have valid lore.kernel.org links in Link: tags
  2. Lore link matches PR commits: Verified for commit 01/15 (✅ exact match); cannot verify for commits 02-15 (lore evidence not fetched)
  3. Upstream patch status:
    • Commit 01/15: ⏳ Decision Pending (process concerns raised, no explicit acceptance or rejection)
    • Commits 02-15: Unknown (lore threads not available for analysis)
  4. PR present in qcom-next/topics: Yes - all 15 commit(s) are present in qcom-next or topics
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1933 - "Add Maili SoC support and audio enablement"
Commits: 15 commits, all with FROMLIST: prefix
Verdict: ⚠️ PARTIAL


Analysis Summary

This PR contains 15 commits from multiple lore.kernel.org patch series. All commits use the FROMLIST: prefix correctly. I validated commit 01/15 in detail against its lore source and provide a summary assessment for the remaining commits.


Commit 01/15: soc: qcom: pd-mapper: Add support for Maili SoC

Lore link: https://lore.kernel.org/all/20260819054203.61385-3-prasad.kumpatla@oss.qualcomm.com/
Lore series: [PATCH v1 2/2] from "Add initial Maili SoC support" series

Commit Message

Check Status Note
Subject matches upstream ✅ PR adds FROMLIST: prefix; core subject identical
Body preserves rationale ✅ Identical to lore patch
Fixes tag present/correct N/A No Fixes tag in upstream or PR
Authorship preserved ✅ From: matches lore author (Prasad Kumpatla) - correct for FROMLIST:
Original author in Signed-off-by ✅ Prasad Kumpatla's Signed-off-by: present
Reviewed-by preserved ✅ Konrad Dybcio's Reviewed-by: present
Link tag present ✅ Correct lore.kernel.org link

Diff Comparison

File Status Notes
drivers/soc/qcom/qcom_pd_mapper.c ✅ Identical - adds one line for qcom,maili compatible

Diff fingerprint: Exact match between PR and lore patch. The change adds a single line mapping qcom,maili to kaanapali_domains in the device ID table.

Upstream Patch Status

Community verdict: ⏳ Decision Pending (with process concerns)

Evidence from lore thread:

  • Patch 1/2 (dt-bindings): ❌ Explicitly NACKed by Krzysztof Kozlowski for adding a compatible without a user
  • Patch 2/2 (pd-mapper, this commit): Krzysztof commented "This patchset makes no sense... such trivialities targeting Qcom SoC should be sent with the SoC DTS. It brings no value to send it earlier."
  • Status: No explicit NAK on patch 2/2, but strong process criticism. No "applied" or "queued" signal found.
  • Reviewed-by: Konrad Dybcio provided Reviewed-by: tag (positive signal)
  • Last activity: August 19, 2026 (original posting)

Interpretation: The pd-mapper patch (2/2) received process criticism but not an explicit rejection. The dt-bindings patch (1/2, not in this PR) was NACKed. The pd-mapper change itself is technically sound (adds a user for the compatible), but the maintainer questioned the value of upstreaming it separately from the full SoC DTS.


Remaining Commits (02/15 through 15/15)

Lore links present: ✅ All 14 commits have valid lore.kernel.org links

Lore link patterns:

  • Commits 02-04: From series 20260923084627.748920 (ASoC: Maili sound card)
  • Commits 05-06: From series 20260928-master-v9 (LPASS VA CSR)
  • Commits 07-10: From series 20260922-add_shikra_support-v1 (Hawi LPASS macro)
  • Commits 11-13: From series 20260918-qaif_dai_id_support-v1 (QAIF AIF MI2S)
  • Commits 14-15: From series 20260821113548.2686650 (Hawi LPASS LPI pinctrl)

Lore evidence: Only commit 01/15's lore thread was fetched. The other 14 lore links were not fetched by Jarvis, so I cannot verify:

  • Whether the PR diffs match the lore patches
  • Upstream acceptance status for those patches
  • Commit message fidelity

Authorship: All 15 commits show From: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com> which is appropriate for FROMLIST: commits where the submitter may differ from the original patch author. I cannot verify whether the original authors' Signed-off-by: tags are preserved without the lore sources.


Integration Presence (qcom-next/topics)

Per integration_presence_report.md:

Status Count Details
✅ Present 15/15 All commits found in qcom-next or kernel-topics
⚠️ Partial match in qcom-next 11/15 Subject or partial tree evidence, but full verified via topics
✅ Exact match in qcom-next 2/15 Commits 07/15 and 13/15
✅ Verified via topics 13/15 Exact patch-id match in kernel-topics branches

Final integration status: ✅ PASS - All 15 commits are present in the integration tree (qcom-next or topics).


Issues Found

  1. Incomplete lore validation: Only 1 of 15 lore links was fetched, preventing full validation of commits 02-15 against their upstream sources.

  2. Upstream status unclear for most commits: Without the lore threads for commits 02-15, I cannot determine whether those patches have been accepted, are under review, or have been rejected upstream.

  3. Commit 01/15 upstream concerns: The lore thread shows process criticism from the DT maintainer. While not an explicit NAK of the pd-mapper patch itself, the maintainer questioned the value of upstreaming this change separately from the full SoC support.

  4. FROMLIST prefix timing: All commits use FROMLIST: prefix, which is correct for patches posted to mailing lists but not yet merged upstream. However, if any of these patches have since been accepted into maintainer trees or mainline, the prefix should be updated to UPSTREAM:, FROMGIT:, or BACKPORT: as appropriate.


Recommendation

For commit 01/15: ⚠️ Merge with caution - The patch is technically correct and has a Reviewed-by: tag, but the upstream maintainer expressed concerns about the upstreaming approach. The patch adds a legitimate user (pd-mapper) for the Maili compatible, addressing the concern that led to the NAK of the dt-bindings patch. However, the maintainer's process criticism suggests this may not be accepted upstream in its current form.

For commits 02-15: ⏸️ Cannot fully validate - Without lore evidence, I cannot verify diff fidelity or upstream status. The integration presence check confirms all commits are in qcom-next/topics, which provides confidence they are appropriate for the Qualcomm kernel tree.

Overall: The PR is suitable for merging into the Qualcomm kernel tree given that all commits are already present in qcom-next or topics. However, the upstream acceptance path for these patches (especially commit 01/15) remains uncertain.


Final Summary

  1. Lore link present: Yes for all 15 commits - all have valid lore.kernel.org links in Link: tags
  2. Lore link matches PR commits: Verified for commit 01/15 (✅ exact match); cannot verify for commits 02-15 (lore evidence not fetched)
  3. Upstream patch status:
    • Commit 01/15: ⏳ Decision Pending (process concerns raised, no explicit acceptance or rejection)
    • Commits 02-15: Unknown (lore threads not available for analysis)
  4. PR present in qcom-next/topics: ✅ Yes - all 15 commits present (2 in qcom-next, 13 verified via topics, overall status PASS)

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: ba86f67908354f41f269ca1d64b22e4624766dcf
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final
1/15 [PATCH 01/15] FROMLIST: soc: qcom: pd-mapper: Add support for Maili missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at 93b3043 present
2/15 [PATCH 02/15] FROMLIST: ASoC: codecs: wsa885x: Reset registers on partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 62dbd8c present
3/15 [PATCH 03/15] FROMLIST: ASoC: qcom: sc8280xp: add Maili sound card partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 0b15747 present
4/15 [PATCH 04/15] FROMLIST: ASoC: dt-bindings: qcom: Add Maili LPASS partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 13c94bc present
5/15 [PATCH 05/15] FROMLIST: dt-bindings: clock: qcom: Add LPASS VA CSR missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at 5a10700 present
6/15 [PATCH 06/15] FROMLIST: clk: qcom: Add LPASS VA CSR heartbeat pulse partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 33a82da present
7/15 [PATCH 07/15] FROMLIST: ASoC: qcom: lpass-macro-common: Add missing present - exact patch-id match at 27cf083 skipped - not checked because qcom-next already contains the change present
8/15 [PATCH 08/15] FROMLIST: ASoC: dt-bindings: qcom: Add Hawi LPASS macro partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 2305000 present
9/15 [PATCH 09/15] FROMLIST: ASoC: qcom: lpass-tx-macro: Add support for partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 4cdd3d8 present
10/15 [PATCH 10/15] FROMLIST: ASoC: qcom: lpass: Add support for LPASS partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at ed3440c present
11/15 [PATCH 11/15] FROMLIST: ASoC: dt-bindings: qcom: add QAIF AIF MI2S partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at fd9f0d9 present
12/15 [PATCH 12/15] FROMLIST: ASoC: qcom: qdsp6: lpass-ports: add support partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at ff1ca12 present
13/15 [PATCH 13/15] FROMLIST: ASoC: qcom: sc8280xp: Handle AIF MI2S and TDM present - all checked added lines are present skipped - not checked because qcom-next already contains the change present
14/15 [PATCH 14/15] FROMLIST: dt-bindings: pinctrl: missing - no subject, patch-id, or full tree-content match found present - exact patch-id match at 5f50e9f present
15/15 [PATCH 15/15] FROMLIST: pinctrl: qcom: hawi-lpass-lpi: add Hawi LPASS partial - subject or partial tree evidence found, but full change was not verified present - exact patch-id match at 6713b47 present

Final Status

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

@qlijarvis

Copy link
Copy Markdown

PR #1933 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch ⏭️ Skipped - automerge conflict
dt-binding-check ⏭️ Skipped - automerge conflict
dtb-check ⏭️ Skipped - automerge conflict
sparse-check ⏭️ Skipped - automerge conflict
check-uapi-headers ⏭️ Skipped - automerge conflict
check-patch-compliance ⏭️ Skipped - automerge conflict
tag-check ✅ All 15 commits have valid FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1933 - Maili and Hawi LPASS audio support
Target branch: topic/tech/mm/audio/all
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/36677229373

Checker Result Summary
checkpatch ⏭️ Skipped - automerge conflict
dt-binding-check ⏭️ Skipped - automerge conflict
dtb-check ⏭️ Skipped - automerge conflict
sparse-check ⏭️ Skipped - automerge conflict
check-uapi-headers ⏭️ Skipped - automerge conflict
check-patch-compliance ⏭️ Skipped - automerge conflict
tag-check ✅ All 15 commits have valid FROMLIST: prefix

⚠️ Automerge Conflict (CI Infrastructure Issue)

Root cause: The CI workflow failed during the automerge stage when attempting to integrate topic/tech/mm/audio/all with the qcom-next baseline. This prevented all checkers from running.

Failure details:

Merging topic branch: topic/tech/mm/audio/all
CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml
CONFLICT (content): Merge conflict in drivers/gpu/drm/msm/dp/dp_display.c
CONFLICT (content): Merge conflict in drivers/soundwire/qcom.c
CONFLICT (content): Merge conflict in sound/soc/codecs/Kconfig
CONFLICT (content): Merge conflict in sound/soc/codecs/adau1977-i2c.c
CONFLICT (content): Merge conflict in sound/soc/codecs/lpass-rx-macro.c
CONFLICT (content): Merge conflict in sound/soc/qcom/sc8280xp.c
Automatic merge failed; fix conflicts and then commit the result.
automerge returned non-zero; check logs for conflicts

Analysis:

This is not a defect in PR #1933. The automerge conflict occurs because:

  1. PR Hawi support #1933 targets a topic branch (topic/tech/mm/audio/all), not qcom-next or qcom-next-staging
  2. The CI workflow attempts to merge the topic branch with qcom-next as part of integration testing
  3. Conflicts exist between the topic branch and qcom-next in 7 files, primarily in audio/soundwire subsystems
  4. These conflicts are expected when topic branches diverge from the integration baseline

The conflicts are in:

  • Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml (DT binding)
  • drivers/gpu/drm/msm/dp/dp_display.c (display driver - unrelated to this PR)
  • drivers/soundwire/qcom.c (soundwire driver)
  • sound/soc/codecs/Kconfig (codec Kconfig)
  • sound/soc/codecs/adau1977-i2c.c (codec driver)
  • sound/soc/codecs/lpass-rx-macro.c (LPASS macro)
  • sound/soc/qcom/sc8280xp.c (sound card driver)

Fix:

This is a topic branch integration issue, not a patch quality issue. The PR maintainer should:

  1. Rebase the topic branch onto the latest qcom-next:

    git fetch origin qcom-next
    git rebase origin/qcom-next topic/tech/mm/audio/all
    # Resolve conflicts manually
    git push --force-with-lease origin topic/tech/mm/audio/all
  2. Or merge qcom-next into the topic branch:

    git fetch origin qcom-next
    git merge origin/qcom-next
    # Resolve conflicts manually
    git push origin topic/tech/mm/audio/all
  3. Re-trigger CI after resolving conflicts

Note: The conflicts in drivers/gpu/drm/msm/dp/dp_display.c are unrelated to this audio-focused PR and suggest that the topic branch has diverged significantly from qcom-next.


✅ tag-check — PASS

Analysis: All 15 commits in PR #1933 have valid subject-line prefixes:

✅ FROMLIST: soc: qcom: pd-mapper: Add support for Maili
✅ FROMLIST: ASoC: codecs: wsa885x: Reset registers on teardown for B2B playback
✅ FROMLIST: ASoC: qcom: sc8280xp: add Maili sound card configuration
✅ FROMLIST: ASoC: dt-bindings: qcom: Add Maili LPASS
✅ FROMLIST: dt-bindings: clock: qcom: Add LPASS VA CSR
✅ FROMLIST: clk: qcom: Add LPASS VA CSR heartbeat pulse
✅ FROMLIST: ASoC: qcom: lpass-macro-common: Add missing
✅ FROMLIST: ASoC: dt-bindings: qcom: Add Hawi LPASS macro
✅ FROMLIST: ASoC: qcom: lpass-tx-macro: Add support for
✅ FROMLIST: ASoC: qcom: lpass: Add support for LPASS
✅ FROMLIST: ASoC: dt-bindings: qcom: add QAIF AIF MI2S
✅ FROMLIST: ASoC: qcom: qdsp6: lpass-ports: add support
✅ FROMLIST: ASoC: qcom: sc8280xp: Handle AIF MI2S and TDM
✅ FROMLIST: dt-bindings: pinctrl:
✅ FROMLIST: pinctrl: qcom: hawi-lpass-lpi: add Hawi LPASS

All commits use the FROMLIST: prefix, indicating they have been posted to the upstream mailing list (lore.kernel.org). This is the correct prefix for patches that are under upstream review.

Reproduce locally:

git log --format="%H %s" origin/topic/tech/mm/audio/all~15..origin/topic/tech/mm/audio/all | \
  grep -vE '^[0-9a-f]+ (FROMLIST|FROMGIT|UPSTREAM|BACKPORT|QCLINUX|PENDING|WORKAROUND):'

(Should return no output if all commits have valid prefixes)


Verdict

The PR patches themselves are compliant — all commits have valid FROMLIST: prefixes.

However, the CI run failed due to automerge conflicts between the topic branch and qcom-next baseline. This is a topic branch integration issue, not a patch defect.

Action required:

  1. Rebase or merge topic/tech/mm/audio/all with the latest qcom-next to resolve conflicts
  2. Re-trigger CI after conflict resolution
  3. Once automerge succeeds, the actual checkers (checkpatch, dt-binding-check, dtb-check, sparse, etc.) will run and provide patch-level feedback

No patch changes are needed at this time — the issue is purely integration-related.

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.

3 participants