From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Maciej Strozek <mstrozek@opensource.cirrus.com>
Cc: Mark Brown <broonie@kernel.org>, Takashi Iwai <tiwai@suse.com>,
Lee Jones <lee@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
patches@opensource.cirrus.com, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 0/4] Add support for CS42L43B codec to CS42L43 driver
Date: Wed, 4 Feb 2026 11:11:42 +0000 [thread overview]
Message-ID: <aYMpbnzi/UTO5Fqs@opensource.cirrus.com> (raw)
In-Reply-To: <20260126144011.140029-1-mstrozek@opensource.cirrus.com>
On Mon, Jan 26, 2026 at 02:39:14PM +0000, Maciej Strozek wrote:
> Hello,
>
> Introducing CS42L43B, a variant of the CS42L43 codec with changes to
> PDM (DMIC) inputs, RAM/ROM memory and extra channels to two SoundWire
> ports and ISRCs, and can be supported by the existing CS42L43 driver
> with some modifications.
> Support is split into four commits:
> 1. Add CS42L43B codec info to SoundWire utils
> 2. Add dt binding for the new variant
> 3. MFD driver part 1/2
> 4. ASoC codec driver part 2/2
>
> Regards,
> Maciej
>
> ---
Reviewed-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Thanks,
Charles
prev parent reply other threads:[~2026-02-04 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 14:39 [PATCH v4 0/4] Add support for CS42L43B codec to CS42L43 driver Maciej Strozek
2026-01-26 14:39 ` [PATCH v4 1/4] ASoC: sdw_utils: Add CS42L43B codec info Maciej Strozek
2026-01-26 14:39 ` [PATCH v4 2/4] ASoC: dt-bindings: cirrus,cs42l43: Add CS42L43B variant Maciej Strozek
2026-01-26 14:39 ` [PATCH v4 3/4] mfd: cs42l43: Add support for the B variant Maciej Strozek
2026-01-26 14:39 ` [PATCH v4 4/4] ASoC: " Maciej Strozek
2026-02-04 11:11 ` Charles Keepax [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=aYMpbnzi/UTO5Fqs@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mstrozek@opensource.cirrus.com \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.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