[RFC,0/2] ASoC: dapm/pins: handle component prefix

Message

Pierre-Louis Bossart Feb. 8, 2021, 11:40 p.m. UTC

SoundWire machine drivers make a heavy use of component prefixes to
uniquify control names. This however results in errors when looking
for widgets or pins. This patchset suggests two solutions but feedback
or suggestions on how to take the prefix into account would be
welcome.

Bard Liao (1):
  ASoC: Intel: boards: max98373: get dapm from cpu_dai

Shuming Fan (1):
  ASoC: dapm: use component prefix when checking widget names

 sound/soc/intel/boards/sof_maxim_common.c |  5 +++--
 sound/soc/soc-dapm.c                      | 13 ++++++++++++-
 2 files changed, 15 insertions(+), 3 deletions(-)

Comments

Mark Brown Feb. 10, 2021, 8:11 p.m. UTC | #1

On Mon, 8 Feb 2021 17:40:41 -0600, Pierre-Louis Bossart wrote:
> SoundWire machine drivers make a heavy use of component prefixes to
> uniquify control names. This however results in errors when looking
> for widgets or pins. This patchset suggests two solutions but feedback
> or suggestions on how to take the prefix into account would be
> welcome.
> 
> Bard Liao (1):
>   ASoC: Intel: boards: max98373: get dapm from cpu_dai
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dapm: use component prefix when checking widget names
      commit: ae4fc532244b3bb4d86c397418d980b0c6be1dfd
[2/2] ASoC: Intel: boards: max98373: get dapm from cpu_dai
      commit: 1183c350011a6f6b551c200b9206bf1808c22a4c

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