Message ID | 20250122164129.807247-1-ivo.g.dimitrov.75@gmail.com |
---|---|
Headers | show |
Series | ASoC: cpcap: Implement jack headset detection | expand |
On Wed, Jan 22, 2025 at 06:41:27PM +0200, Ivaylo Dimitrov wrote:
> Add DT binding for the audio-codec headset detection interrupts.
Lee, would it be OK to merge this via ASoC?
On Thu, 23 Jan 2025, Mark Brown wrote: > On Wed, Jan 22, 2025 at 06:41:27PM +0200, Ivaylo Dimitrov wrote: > > Add DT binding for the audio-codec headset detection interrupts. > > Lee, would it be OK to merge this via ASoC? I'm not sure why you would want to and it may make subsequent changes more challenging to merge, but if you really want to ...
On Mon, Jan 27, 2025 at 01:27:25PM +0000, Lee Jones wrote: > On Thu, 23 Jan 2025, Mark Brown wrote: > > On Wed, Jan 22, 2025 at 06:41:27PM +0200, Ivaylo Dimitrov wrote: > > > Add DT binding for the audio-codec headset detection interrupts. > > Lee, would it be OK to merge this via ASoC? > I'm not sure why you would want to and it may make subsequent changes > more challenging to merge, but if you really want to ... It's the binding documentation for the ASoC change in the final patch.
On Wed, 22 Jan 2025 18:41:24 +0200, Ivaylo Dimitrov wrote: > cpcap audio codec found on cpcap PMIC supports headset detection > and PTT button through its 3.5 mm jack. This series implements > support for those capabilities. > > Changelog: > v2: > - cpcap.c: fix a typo > - dt-bindings: fix interrupts description and alignment > - motorola-cpcap-mapphone.dtsi: fix interrupts alignment > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [2/5] ASoC: cpcap: Implement .set_bias_level commit: 5b4288792ff246cf2bda0c81cebcc02d1f631ca3 [3/5] dt-bindings: mfd: motorola-cpcap: Document audio-codec interrupts commit: 02d4a97ce30c0494ce6a614cd54d583caa0f8016 [5/5] ASoC: cpcap: Implement jack detection commit: 7ed1b265021dd13ce5619501b388e489ddc8e204 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