All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/2] ASoC: qcom: remove ipq806x Storm machine driver
Date: Tue, 21 Jul 2026 18:25:16 +0000	[thread overview]
Message-ID: <20260721182516.AB3F21F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260721-drop-sound-storm-v1-1-23ae4a689ffe@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] Removing SND_SOC_STORM leaves SND_SOC_LPASS_IPQ806X without any selectors, rendering the IPQ806X LPASS CPU driver completely unbuildable and unreachable.
- [Low] The device tree binding documentation for the removed google,storm-audio driver was left behind.
--

--- Patch [1]: [PATCH 1/2] ASoC: qcom: remove ipq806x Storm machine driver ---
commit 76b009b0b947fd2197dab876d7f10fb5105c7935
Author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>

ASoC: qcom: remove ipq806x Storm machine driver

The Storm board machine driver targets Google's IPQ806x-based Storm
reference board. This driver is removed together with its Kconfig
entry and Makefile rule since it has no upstream device tree and no
active users.

> diff --git a/sound/soc/qcom/Kconfig b/sound/soc/qcom/Kconfig
> index e6e24f3b99222..68e3146bf2307 100644
> --- a/sound/soc/qcom/Kconfig
> +++ b/sound/soc/qcom/Kconfig
> @@ -47,15 +47,6 @@ config SND_SOC_LPASS_SC7280
>  	select SND_SOC_LPASS_HDMI
>  	select SND_SOC_LPASS_CDC_DMA
>  
> -config SND_SOC_STORM
> -	tristate "ASoC I2S support for Storm boards"
> -	depends on GPIOLIB
> -	select SND_SOC_LPASS_IPQ806X

[Severity: Medium]
Does removing SND_SOC_STORM leave SND_SOC_LPASS_IPQ806X without any selectors?

SND_SOC_LPASS_IPQ806X lacks a prompt in Kconfig, so without any selectors it
cannot be enabled manually or by COMPILE_TEST. This leaves the IPQ806X LPASS
CPU driver (sound/soc/qcom/lpass-ipq806x.c) and its Makefile entry as
unbuildable dead code.

Should SND_SOC_LPASS_IPQ806X and lpass-ipq806x.c be cleaned up in this patch as
well?

[ ... ]

> diff --git a/sound/soc/qcom/storm.c b/sound/soc/qcom/storm.c
> deleted file mode 100644
> index 1e0eda8c24c4e..0000000000000
> --- a/sound/soc/qcom/storm.c
> +++ /dev/null

[ ... ]

> -#ifdef CONFIG_OF
> -static const struct of_device_id storm_device_id[]  = {
> -	{ .compatible = "google,storm-audio" },
> -	{},
> -};

[Severity: Low]
Does the device tree binding documentation for "google,storm-audio" still exist
in the tree?

Removing this compatible string might leave behind obsolete binding
documentation, such as Documentation/devicetree/bindings/sound/storm.txt.
Should the corresponding binding file be removed alongside the driver?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260721-drop-sound-storm-v1-0-23ae4a689ffe@oss.qualcomm.com?part=1

  reply	other threads:[~2026-07-21 18:25 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 [this message]
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
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=20260721182516.AB3F21F00A3A@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.