The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Christian Marangi <ansuelsmth@gmail.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Srinivas Kandagatla <srini@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] ASoC: qcom: remove ipq806x Storm machine driver
Date: Wed, 22 Jul 2026 12:37:55 +0200	[thread overview]
Message-ID: <6a609d87.87c5160c.1accad.0f33@mx.google.com> (raw)
In-Reply-To: <85f2799d-fadf-478d-9f3f-fb8ff91ba84d@oss.qualcomm.com>

On Wed, Jul 22, 2026 at 10:00:34AM +0200, Konrad Dybcio wrote:
> On 7/21/26 8:12 PM, Dmitry Baryshkov wrote:
> > The Storm board machine driver targets Google's IPQ806x-based Storm
> > reference board (a MAX98357A DAC wired to the LPASS I2S bus). This board
> > has no upstream device tree, no active users and has seen no functional
> > changes in years, so the driver is dead weight.
> > 
> > Remove the driver together with its Kconfig entry and Makefile rule.
> > 
> > Assisted-by: Claude:claude-opus-4-8
> 
> Using AI to `git rm` is definitely tokenmaxxing!
> 
> > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> > ---
> 
> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>

Honestly I'm pretty angry about the latest changes on ipq806x. First the
dtsi just because there weren't device (it's ok and understandable) now we
are starting to remove driver...

There are godzillion situation where there is a driver but absolutely no
dtsi. Lets remove the dwmac driver, usb phy, pcie and everything else at
this point and treat this soc like it's a 80-90 code...

I will post dtsi with actual device for the SoC but really I'm not
following all this hurry in cleaning code for device that still gets used
and actually some company even produced new one (even if it's EOL)

-- 
	Ansuel

  reply	other threads:[~2026-07-22 10:38 UTC|newest]

Thread overview: 12+ 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-22  8:00   ` Konrad Dybcio
2026-07-22 10:37     ` Christian Marangi [this message]
2026-07-22 10:48       ` Dmitry Baryshkov
2026-07-23 18:38         ` Christian Marangi
2026-07-23 19:18           ` Dmitry Baryshkov
2026-07-23 19:24             ` Mark Brown
2026-07-23 19:39               ` Dmitry Baryshkov
2026-07-21 18:12 ` [PATCH 2/2] dt-bindings: sound: remove google,storm-audio binding Dmitry Baryshkov
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=6a609d87.87c5160c.1accad.0f33@mx.google.com \
    --to=ansuelsmth@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=robh@kernel.org \
    --cc=srini@kernel.org \
    --cc=tiwai@suse.com \
    /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