From: Takashi Iwai <tiwai@suse.de>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: <broonie@kernel.org>, <tiwai@suse.com>, <perex@perex.cz>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>
Subject: Re: [PATCH v5 00/11] ALSA: hda: Adding support for CS35L56 on HDA systems
Date: Fri, 21 Jul 2023 16:50:35 +0200 [thread overview]
Message-ID: <87bkg5z5c4.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230721132120.5523-1-rf@opensource.cirrus.com>
On Fri, 21 Jul 2023 15:21:09 +0200,
Richard Fitzgerald wrote:
>
> This set of patches adds support for using the CS35L56 boosted smart
> amplifier on HDA systems. In these systems the CS35L56 audio is
> routed through a HDA-to-I2S bridge codec.
>
> This doesn't include the changes to the Realtek driver to actually hook
> up the CS35L56 driver, because we don't yet have the QUIRK IDs to
> associate it with. But we want to publish the driver now so that it is
> available for bringing up hardware with the CS35L56.
>
> The first 9 patches are moving code out of the ASoC driver and into the
> shared library so that it can be shared with the HDA driver.
>
> Patch #10 fixes missing #includes in the HDA headers so that the CS35L56
> driver doesn't have to #include headers that it doesn't use.
>
> CHANGES SINCE V5
> The series has been rebased onto commit df4167d658d4
> ("ASoC: cs35l56: Patch soft registers to defaults"), which removes
> cs35l56_reread_firmware_registers() and adds cs35l56_set_patch().
>
> Changes are trivial so I have carried forward Mark's and Takashi's acks.
Mark, I suppose it's fine to take all of those to my sound.git tree?
Takashi
next prev parent reply other threads:[~2023-07-21 14:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 13:21 [PATCH v5 00/11] ALSA: hda: Adding support for CS35L56 on HDA systems Richard Fitzgerald
2023-07-21 13:21 ` [PATCH v5 01/11] ASoC: cs35l56: Move shared data into a common data structure Richard Fitzgerald
2023-07-21 13:21 ` [PATCH v5 02/11] ASoC: cs35l56: Make cs35l56_system_reset() code more generic Richard Fitzgerald
2023-07-21 13:21 ` [PATCH v5 03/11] ASoC: cs35l56: Convert utility functions to use common data structure Richard Fitzgerald
2023-07-21 13:21 ` [PATCH v5 04/11] ASoC: cs35l56: Move utility functions to shared file Richard Fitzgerald
2023-07-21 13:21 ` [PATCH v5 05/11] ASoC: cs35l56: Move runtime suspend/resume to shared library Richard Fitzgerald
2023-07-21 13:21 ` [PATCH v5 06/11] ASoC: cs35l56: Move cs_dsp init into " Richard Fitzgerald
2023-07-21 13:21 ` [PATCH v5 07/11] ASoC: cs35l56: Move part of cs35l56_init() to " Richard Fitzgerald
2023-07-21 13:21 ` [PATCH v5 08/11] ASoC: cs35l56: Make common function for control port wait Richard Fitzgerald
2023-07-21 13:21 ` [PATCH v5 09/11] ASoC: cs35l56: Make a common function to shutdown the DSP Richard Fitzgerald
2023-07-21 13:21 ` [PATCH v5 10/11] ALSA: hda: Fix missing header dependencies Richard Fitzgerald
2023-07-21 13:21 ` [PATCH v5 11/11] ALSA: hda/cs35l56: Add driver for Cirrus Logic CS35L56 amplifier Richard Fitzgerald
2023-07-21 14:50 ` Takashi Iwai [this message]
2023-07-21 14:52 ` [PATCH v5 00/11] ALSA: hda: Adding support for CS35L56 on HDA systems Mark Brown
2023-07-21 15:04 ` Takashi Iwai
2023-07-21 15:47 ` Takashi Iwai
2023-07-24 18:28 ` Mark Brown
2023-07-25 9:51 ` Takashi Iwai
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=87bkg5z5c4.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--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