Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: tiwai@suse.com, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH] ALSA: hda/hda_cs_dsp_ctl: Delete hda_cs_dsp_ctl module
Date: Sun, 27 Apr 2025 10:02:59 +0200	[thread overview]
Message-ID: <87seluxc98.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250424181214.66759-1-rf@opensource.cirrus.com>

On Thu, 24 Apr 2025 20:12:14 +0200,
Richard Fitzgerald wrote:
> 
> Delete the hda_cs_dsp module and move the one array and one function
> that is used by the cs35l41_hda driver into that driver.
> 
> The cs35l41 and cs35l56 drivers stopped creating ALSA controls to
> wrap firmware controls. The reasons are explained in:
> 
> commit 312c04cee408 ("ALSA: hda: cs35l41: Stop creating ALSA Controls
> for firmware coefficients")
> 
> and
> 
> commit 34e1b1bb7324 ("ALSA: hda: cs35l56: Stop creating ALSA controls
> for firmware coefficients")
> 
> The cs35l56_hda driver now doesn't use hda_cs_dsp_ctl at all. The
> cs35l41_hda driver only uses the small array of firmware names and the
> function to read a control value. All other functions and data in
> hda_cs_dsp_ctl are unused. There is no need to keep a separate module
> for such a small amount of data and code that is only used by one driver,
> so remove the whole module.
> 
> Signed-off-by: Richard Fitzgerald <rf@opensource.cirrus.com>

Thanks, applied now to for-next branch.


Takashi

      reply	other threads:[~2025-04-27  8:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 18:12 [PATCH] ALSA: hda/hda_cs_dsp_ctl: Delete hda_cs_dsp_ctl module Richard Fitzgerald
2025-04-27  8:02 ` Takashi Iwai [this message]

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=87seluxc98.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.com \
    --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