From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Vijendar Mukunda <Vijendar.Mukunda@amd.com>,
Syed Saba Kareem <Syed.SabaKareem@amd.com>,
Arnd Bergmann <arnd@arndb.de>,
Randy Dunlap <rdunlap@infradead.org>,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Venkata Prasad Potturu <venkataprasad.potturu@amd.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH 0/2] AMD Vangogh support for NAU8821/MAX98388
Date: Wed, 21 Jun 2023 10:58:02 +0300 [thread overview]
Message-ID: <892273c4-82b2-47d5-c03c-2d298424c18f@collabora.com> (raw)
In-Reply-To: <20230620222743.274432-1-cristian.ciocaltea@collabora.com>
On 6/21/23 01:27, Cristian Ciocaltea wrote:
> This patch series extends the Vangogh machine driver to support a variant based
> on the Nuvoton NAU88L21 Codec and the Analog Devices MAX98388 Speaker Amplifier.
Please ignore this for the moment, as it depends on a firmware upgrade
and would break the existing devices based on the CS35L41 codec.
I will resend as soon as a proper solution is figured out.
Thanks,
Cristian
prev parent reply other threads:[~2023-06-21 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 22:27 Cristian Ciocaltea
2023-06-20 22:27 ` [PATCH 1/2] ASoC: amd: vangogh: Add ACPI probe support Cristian Ciocaltea
2023-06-20 22:27 ` [PATCH 2/2] ASoC: amd: vangogh: Add support for NAU8821/MAX98388 variant Cristian Ciocaltea
2023-06-21 7:58 ` Cristian Ciocaltea [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=892273c4-82b2-47d5-c03c-2d298424c18f@collabora.com \
--to=cristian.ciocaltea@collabora.com \
--cc=Syed.SabaKareem@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=kernel@collabora.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rdunlap@infradead.org \
--cc=tiwai@suse.com \
--cc=venkataprasad.potturu@amd.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
all inboxes | Powered by JetHome®