From: sashiko-bot@kernel.org
To: "Richard Acayan" <mailingradian@gmail.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v5 13/15] ASoC: msm8916-wcd-analog: add pm8950 codec
Date: Tue, 09 Jun 2026 16:48:08 +0000 [thread overview]
Message-ID: <20260609164808.B6BD01F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260609162255.31074-14-mailingradian@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Interrupts are requested before their dependencies are initialized, leading to a NULL pointer dereference if an interrupt fires early.
--
(Due to recitation restrictions, I cannot quote the patch directly. Here is a free-form summary of the review findings based on the provided commit.)
commit 6bdf31b5b0e7905983f34bd3546744e90b15273e
Author: Adam Skladowski <a39.skl@gmail.com>
ASoC: msm8916-wcd-analog: add pm8950 codec
This commit adds register overrides for the PM8950 codec. It also implements
matching register overrides via the compatible string array.
[Severity: High]
This isn't a bug introduced by this patch, but could this pre-existing setup
cause a NULL pointer dereference if an interrupt fires early?
In pm8916_wcd_analog_spmi_probe(), threaded IRQs (such as
pm8916_mbhc_switch_irq_handler and mbhc_btn_press_irq_handler) are requested
via devm_request_threaded_irq(). This enables the interrupts immediately.
However, the ASoC component (priv->component) isn't initialized until much
later in pm8916_wcd_analog_probe() during ASoC sound card binding.
If the interrupt fires before the component probe, the IRQ handler executes
with a NULL priv->component:
pm8916_mbhc_switch_irq_handler()
struct snd_soc_component *component = priv->component;
if (snd_soc_component_read(component, CDC_A_MBHC_DET_CTL_1) ...
Passing this NULL component pointer to snd_soc_component_read() looks like
it would cause a crash. Should the IRQ registration be deferred to the
component probe, or kept disabled until the component is fully initialized?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260609162255.31074-1-mailingradian@gmail.com?part=13
next prev parent reply other threads:[~2026-06-09 16:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 16:22 [PATCH v5 00/15] SDM660 sound card and internal MI2S support Richard Acayan
2026-06-09 16:22 ` [PATCH v5 01/15] ASoC: dt-bindings: qcom,sm8250: add compatible for sdm660 Richard Acayan
2026-06-09 16:22 ` [PATCH v5 02/15] ASoC: dt-bindings: qcom: q6dsp: add support for lpi mi2s ports 5-6 Richard Acayan
2026-06-09 16:22 ` [PATCH v5 03/15] ASoC: dt-bindings: pm8916-wcd-analog-codec: Document pm8950/pm8953 Richard Acayan
2026-06-09 16:22 ` [PATCH v5 04/15] ASoC: dt-bindings: pm8916-analog-codec: Add PM660L compatible Richard Acayan
2026-06-09 16:22 ` [PATCH v5 05/15] ASoC: dt-bindings: msm8916-digital-codec: Add SDM660 compatible Richard Acayan
2026-06-09 16:22 ` [PATCH v5 06/15] ASoC: qdsp6: q6dsp-lpass-ports: add support for lpi mi2s ports 5-6 Richard Acayan
2026-06-09 16:50 ` sashiko-bot
2026-06-09 16:22 ` [PATCH v5 07/15] ASoC: qdsp6: q6afe: add internal mi2s support Richard Acayan
2026-06-09 16:22 ` [PATCH v5 08/15] ASoC: qdsp6: q6afe-dai: " Richard Acayan
2026-06-09 16:22 ` [PATCH v5 09/15] ASoC: qdsp6: q6routing: add lpi " Richard Acayan
2026-06-09 16:22 ` [PATCH v5 10/15] ASoC: qdsp6: common: support headphone jacks connected to lpi mi2s Richard Acayan
2026-06-09 16:22 ` [PATCH v5 11/15] ASoC: qcom: sm8250: add support for LPI_MI2S_RX_0 and LPI_MI2S_TX_3 Richard Acayan
2026-06-09 16:43 ` sashiko-bot
2026-06-09 16:22 ` [PATCH v5 12/15] ASoC: qcom: sm8250: add SDM660 compatible Richard Acayan
2026-06-09 16:38 ` sashiko-bot
2026-06-09 16:22 ` [PATCH v5 13/15] ASoC: msm8916-wcd-analog: add pm8950 codec Richard Acayan
2026-06-09 16:48 ` sashiko-bot [this message]
2026-06-09 16:22 ` [PATCH v5 14/15] ASoC: msm8916-wcd-analog: add pm8953 codec Richard Acayan
2026-06-09 16:22 ` [PATCH v5 15/15] ASoC: msm8916-wcd-analog: add quirk for cajon 2.0 Richard Acayan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260609164808.B6BD01F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=mailingradian@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox