[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172980101186.554299.11182862966336254463.b4-ty@kernel.org>
Date: Thu, 24 Oct 2024 21:16:51 +0100
From: Mark Brown <broonie@...nel.org>
To: Martin PoviĊĦer <povik+lin@...ebit.org>,
David Rhodes <david.rhodes@...rus.com>,
Richard Fitzgerald <rf@...nsource.cirrus.com>,
Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, James Calligeros <jcalligeros99@...il.com>
Cc: asahi@...ts.linux.dev, linux-sound@...r.kernel.org,
patches@...nsource.cirrus.com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Hector Martin <marcan@...can.st>,
Neal Gompa <neal@...pa.dev>
Subject: Re: [PATCH v2 0/3] ASoC: add CS42L84 codec driver
On Sun, 20 Oct 2024 00:47:30 +1000, James Calligeros wrote:
> This is version 2 of the Cirrus Logic CS42L84 ASoC codec driver.
>
> This patch set adds a driver for the Cirrus Logic CS42L84 codec. This chip
> is (so far) found only on Apple Silicon Macs. In keeping with proud Apple
> tradition, the CS42L84 is essentially just a CS42L42 with a different
> regmap and no publicly available datasheet. It may also be missing its
> parent's S/PDIF capabilities as none of Apple's devices support S/PDIF out,
> however this cannot be positively confirmed.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] dt-bindings: sound: Add CS42L84 codec
commit: f2a67da9f4eb03f5402acb9aeb65b23cac990827
[2/3] ASoC: cs42l84: Add new codec driver
commit: 250304a0fb34bb74f4726645ae24dc31d7582a22
[3/3] ASoC: cs42l84: leverage ring sense IRQs to correctly detect headsets
commit: 2391b8719d686b1947b5f81250281fa112da91dc
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