From: Mark Brown <broonie@kernel.org>
To: Joerg Schambacher <joerg.hifiberry@gmail.com>
Cc: a-krasser@ti.com, joerg@hifiberry.com,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Zhang Qilong" <zhangqilong3@huawei.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] ASoC: Adds support for TAS575x to the pcm512x driver
Date: Tue, 03 Oct 2023 14:19:58 +0100 [thread overview]
Message-ID: <169633919804.32637.4231540899734549446.b4-ty@kernel.org> (raw)
In-Reply-To: <20230929150722.405415-1-joerg.hifiberry@gmail.com>
On Fri, 29 Sep 2023 17:07:20 +0200, Joerg Schambacher wrote:
> Enables the existing pcm512x driver to control the almost
> compatible TAS5754 and -76 amplifers. Both amplifiers support
> only an I2C interface and the internal PLL must be always
> on to provide necessary clocks to the amplifier section.
> Tested on TAS5756 with support from Andreas Arbesser-Krasser
> from Texas Instruments <a-krasser@ti.com>
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[2/2] ASoC: Adds support for TAS575x to the pcm512x driver
commit: 1f817805262c2c34142291da376d4932d3c493bc
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
prev parent reply other threads:[~2023-10-03 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 15:07 Joerg Schambacher
2023-10-03 13:19 ` Mark Brown [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=169633919804.32637.4231540899734549446.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=a-krasser@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=joerg.hifiberry@gmail.com \
--cc=joerg@hifiberry.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=zhangqilong3@huawei.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®