From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>, Sen Wang <sen@ti.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Shenghao Ding <shenghao-ding@ti.com>, Kevin Lu <kevin-lu@ti.com>,
Baojun Xu <baojun.xu@ti.com>,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/4] ASoC: Add TAS67524 quad-channel Class-D amplifier driver
Date: Mon, 27 Apr 2026 08:36:23 +0900 [thread overview]
Message-ID: <177724658349.266775.3229695329706944762.b4-ty@b4> (raw)
In-Reply-To: <20260416232640.3084132-1-sen@ti.com>
On Thu, 16 Apr 2026 18:26:31 -0500, Sen Wang wrote:
> ASoC: Add TAS67524 quad-channel Class-D amplifier driver
>
> This series adds support for the TI TAS675x (TAS6754, TAS67524)
> quad-channel automotive Class-D amplifiers. The devices have an
> integrated DSP and load diagnostics, and are controlled over I2C.
>
> Patch 1 adds the dt-binding, patch 2 the codec driver, patch 3 the
> ALSA mixer controls documentation, and patch 4 adds the MAINTAINERS
> entry.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.2
Thanks!
[1/4] ASoC: dt-bindings: Add ti,tas67524
https://git.kernel.org/broonie/sound/c/5067f61ccaa1
[2/4] ASoC: codecs: Add TAS67524 quad-channel audio amplifier driver
https://git.kernel.org/broonie/sound/c/133c81f84471
[3/4] Documentation: sound: Add TAS675x codec mixer controls documentation
https://git.kernel.org/broonie/sound/c/ba46edca354e
[4/4] MAINTAINERS: add entry for TAS67524 audio amplifier
https://git.kernel.org/broonie/sound/c/3507e568d634
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:[~2026-04-27 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 23:26 Sen Wang
2026-04-16 23:26 ` [PATCH v6 1/4] ASoC: dt-bindings: Add ti,tas67524 Sen Wang
2026-04-16 23:26 ` [PATCH v6 2/4] ASoC: codecs: Add TAS67524 quad-channel audio amplifier driver Sen Wang
2026-04-16 23:26 ` [PATCH v6 3/4] Documentation: sound: Add TAS675x codec mixer controls documentation Sen Wang
2026-04-16 23:26 ` [PATCH v6 4/4] MAINTAINERS: add entry for TAS67524 audio amplifier Sen Wang
2026-04-26 23:36 ` 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=177724658349.266775.3229695329706944762.b4-ty@b4 \
--to=broonie@kernel.org \
--cc=baojun.xu@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kevin-lu@ti.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=sen@ti.com \
--cc=shenghao-ding@ti.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
all inboxes | Powered by JetHome®