mbox series

[0/2] Allow detecting ACP6x DMIC via _DSD

Message ID 20220411134532.13538-1-mario.limonciello@amd.com
Headers show
Series Allow detecting ACP6x DMIC via _DSD | expand

Message

Mario Limonciello April 11, 2022, 1:45 p.m. UTC 
It's not possible to probe for the presence of a DMIC, so the ACP6x
machine driver currently has a hardcoded list of all the systems known
to have a DMIC connected to the ACP.

Although this design works it means that the acp6x driver needs to always
grow with more systems and worse, if an OEM introduces a new system there
will be a mismatch in time that even if the driver (otherwise) works fine
it needs their system added to the list to work.

So this series introduces a _DSD that OEMs can populate into the BIOS to
indicate presence of a DMIC.

Mario Limonciello (2):
  ASoC: amd: Add driver data to acp6x machine driver
  ASoC: amd: Add support for enabling DMIC on acp6x via _DSD

 sound/soc/amd/yc/acp6x-mach.c | 42 +++++++++++++++++++++++++++++++----
 1 file changed, 38 insertions(+), 4 deletions(-)

Comments

Mark Brown April 12, 2022, 5:38 p.m. UTC | #1 
On Mon, 11 Apr 2022 08:45:30 -0500, Mario Limonciello wrote:
> It's not possible to probe for the presence of a DMIC, so the ACP6x
> machine driver currently has a hardcoded list of all the systems known
> to have a DMIC connected to the ACP.
> 
> Although this design works it means that the acp6x driver needs to always
> grow with more systems and worse, if an OEM introduces a new system there
> will be a mismatch in time that even if the driver (otherwise) works fine
> it needs their system added to the list to work.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/2] ASoC: amd: Add driver data to acp6x machine driver
      commit: e521f087780d07731e8c950f2f34d08358c86bc9
[2/2] ASoC: amd: Add support for enabling DMIC on acp6x via _DSD
      commit: 5426f506b58424f8ab2cd741bacf4b18b5fe578e

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