[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167209763526.330820.3472409126479136319.b4-ty@kernel.org>
Date: Mon, 26 Dec 2022 23:33:55 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org,
Ajye Huang <ajye_huang@...pal.corp-partner.google.com>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>,
Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
Akihiko Odaki <akihiko.odaki@...il.com>,
Yong Zhi <yong.zhi@...el.com>,
ye xingchen <ye.xingchen@....com.cn>,
Muralidhar Reddy <muralidhar.reddy@...el.com>,
"balamurugan . c" <balamurugan.c@...el.com>,
Libin Yang <libin.yang@...el.com>,
Jaroslav Kysela <perex@...ex.cz>,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
Cezary Rojewski <cezary.rojewski@...el.com>,
David Lin <CTLIN0@...oton.com>, Brent Lu <brent.lu@...el.com>,
Takashi Iwai <tiwai@...e.com>,
Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
alsa-devel@...a-project.org
Subject: Re: [PATCH v2] ASoC: Intel: sof_nau8825: add variant with nau8318 amplifier.
On Fri, 16 Dec 2022 23:49:38 +0800, Ajye Huang wrote:
> This patch adds the driver data for two nau8318 speaker amplifiers on
> SSP1 and nau8825 on SSP0 for ADL platform.
>
> The nau8315 and nau8318 are both Nuvoton Amp chips. They use the same
> Amp driver nau8315.c. The acpi_device_id for nau8315 is "NVTN2010",
> for nau8318 is "NVTN2012".
> The nau8825 is one of Nuvoton headset codec, and its acpi_device_id is
> "10508825".
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: Intel: sof_nau8825: add variant with nau8318 amplifier.
commit: ba7523bb0f494fc440d3a9bb0b665cfcaa192d0c
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
Powered by blists - more mailing lists