From: sashiko-bot@kernel.org
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: sound: remove google,storm-audio binding
Date: Tue, 21 Jul 2026 18:26:26 +0000 [thread overview]
Message-ID: <20260721182626.DC0881F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260721-drop-sound-storm-v1-2-23ae4a689ffe@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incomplete cleanup leaves the IPQ806x LPASS driver as unreachable dead code.
--
--- Patch [2]: [PATCH 2/2] dt-bindings: sound: remove google,storm-audio binding ---
commit 4f1f4fbba8c2f852f688a4151731bed0fe4a61f1
Author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
dt-bindings: sound: remove google,storm-audio binding
This commit removes the device tree binding for the "google,storm-audio"
sound complex. The removal is done because the accompanying ipq806x Storm
machine driver is no longer present.
> With the ipq806x Storm machine driver gone, the accompanying device tree
> binding describing the "google,storm-audio" sound complex is no longer
> used by any driver or device tree. Remove it.
[Severity: Medium]
Since the ipq806x Storm machine driver is gone, does this leave the
IPQ806x LPASS driver as unreachable dead code?
Looking at sound/soc/qcom/Kconfig, SND_SOC_LPASS_IPQ806X is a hidden
Kconfig symbol:
config SND_SOC_LPASS_IPQ806X
tristate
select SND_SOC_LPASS_CPU
select SND_SOC_LPASS_PLATFORM
If the machine driver was the only config that selected it, this symbol can
no longer be enabled. This would mean the compilation target in
sound/soc/qcom/Makefile can no longer be reached:
obj-$(CONFIG_SND_SOC_LPASS_IPQ806X) += snd-soc-lpass-ipq806x.o
Should this incomplete cleanup be addressed by removing the orphaned config
and driver file as well?
> diff --git a/Documentation/devicetree/bindings/sound/storm.txt b/Documentation/devicetree/bindings/sound/storm.txt
> deleted file mode 100644
> index 062a4c185fa9d..0000000000000
> --- a/Documentation/devicetree/bindings/sound/storm.txt
> +++ /dev/null
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260721-drop-sound-storm-v1-0-23ae4a689ffe@oss.qualcomm.com?part=2
next prev parent reply other threads:[~2026-07-21 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 18:12 [PATCH 0/2] ASoC: qcom: remove the ipq806x Storm audio machine driver and binding Dmitry Baryshkov
2026-07-21 18:12 ` [PATCH 1/2] ASoC: qcom: remove ipq806x Storm machine driver Dmitry Baryshkov
2026-07-21 18:25 ` sashiko-bot
2026-07-22 8:00 ` Konrad Dybcio
2026-07-22 10:37 ` Christian Marangi
2026-07-22 10:48 ` Dmitry Baryshkov
2026-07-21 18:12 ` [PATCH 2/2] dt-bindings: sound: remove google,storm-audio binding Dmitry Baryshkov
2026-07-21 18:26 ` sashiko-bot [this message]
2026-07-22 8:01 ` Konrad Dybcio
2026-07-22 8:32 ` [PATCH 0/2] ASoC: qcom: remove the ipq806x Storm audio machine driver and binding Srinivas Kandagatla
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=20260721182626.DC0881F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.