[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174249634796.174081.9833862895994881364.b4-ty@kernel.org>
Date: Thu, 20 Mar 2025 18:45:47 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Saravana Kannan <saravanak@...gle.com>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
patches@...nsource.cirrus.com, Francesco Dolcini <francesco@...cini.it>
Cc: Francesco Dolcini <francesco.dolcini@...adex.com>,
linux-sound@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/5] ASoC: wm8904: Add DMIC and DRC support
On Wed, 19 Mar 2025 15:20:54 +0100, Francesco Dolcini wrote:
> This patch series adds DMIC and DRC support to the WM8904 driver, a new
> of_ helper is added to simplify the driver code.
>
> DRC functionality is added in the same patch series to provide the
> necessary dynamic range control to make DMIC support useful.
>
> The WM8904 supports digital microphones on two of its inputs:
> IN1L/DMICDAT1 and IN1R/DMICDAT2. These two inputs can either be
> connected to an ADC or to the DMIC system. There is an ADC for each
> line, and only one DMIC block. This DMIC block is either connected to
> DMICDAT1 or to DMICDAT2. One DMIC data line supports two digital
> microphones via time multiplexing.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/5] of: Add of_property_read_u16_index
commit: fd9582998b9a82ef53a34756de8a1fb86abac972
[2/5] ASoC: wm8904: Don't touch GPIO configs set to 0xFFFF
commit: 2aa853248b6b6c76b9dd82353e45a4283f9c53ec
[3/5] ASoC: dt-bindings: wm8904: Add DMIC, GPIO, MIC and EQ support
commit: bd552e937fc80faa70007f7a4cbbf7edd5a6629a
[4/5] ASoC: wm8904: get platform data from DT
commit: afe66ef965317381fd2894c2eba144b38b791910
[5/5] ASoC: wm8904: add DMIC support
commit: b6612c8fc3a2c279196050ecc13c77a7863d83eb
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