mbox series

[0/6] ASoC: rt5670/Intel: Add support for Bay Trail CR / Dell Venue 10 Pro 5055 tablet

Message ID 20210402140747.174716-1-hdegoede@redhat.com (mailing list archive)
Headers show
Series ASoC: rt5670/Intel: Add support for Bay Trail CR / Dell Venue 10 Pro 5055 tablet | expand

Message

Hans de Goede April 2, 2021, 2:07 p.m. UTC 
Hi All,

Here is a patch series to enable sound on the Dell Venue 10 Pro 5055 tablet
this series also includes 2 generic improvements to rt5672 support:

1. Add support for boards using Bay Trail CR (SSP0) in combination with a rt5672 codec
2. Set the card's components string based on the DMI info, so that we don't need to
duplicate the DMI quirks in userspace (in the UCM profile)

I've a patch to add support for the components string to the UCM profile for
these boards available here:
https://github.com/jwrdegoede/alsa-ucm-conf/commit/fedacc2bdc530b6febac665db27aab60e03ec840

I will submit this upstream once the kernel side has landed.

Regards,

Hans


Hans de Goede (6):
  ASoC: Intel: Unify the thinkpad10 and aegex10 byt-match quirks
  ASoC: Intel: Baytrail: Add quirk for the Dell Venue 10 Pro 5055 tablet
  ASoC: Intel: cht_bsw_rt5672: Add support for Bay Trail CR / SSP0
  ASoC: rt5670: Add a quirk for the Dell Venue 10 Pro 5055
  ASoC: rt5670: Add a rt5670_components() helper
  ASoC: Intel: cht_bsw_rt5672: Set card.components string

 sound/soc/codecs/rt5670.c                     | 51 ++++++++++++
 sound/soc/codecs/rt5670.h                     |  2 +
 sound/soc/intel/boards/cht_bsw_rt5672.c       | 77 +++++++++++++++----
 .../intel/common/soc-acpi-intel-byt-match.c   | 40 +++++-----
 4 files changed, 136 insertions(+), 34 deletions(-)

Comments

Pierre-Louis Bossart April 2, 2021, 2:47 p.m. UTC | #1 
On 4/2/21 9:07 AM, Hans de Goede wrote:
> Hi All,
> 
> Here is a patch series to enable sound on the Dell Venue 10 Pro 5055 tablet
> this series also includes 2 generic improvements to rt5672 support:
> 
> 1. Add support for boards using Bay Trail CR (SSP0) in combination with a rt5672 codec
> 2. Set the card's components string based on the DMI info, so that we don't need to
> duplicate the DMI quirks in userspace (in the UCM profile)
> 
> I've a patch to add support for the components string to the UCM profile for
> these boards available here:
> https://github.com/jwrdegoede/alsa-ucm-conf/commit/fedacc2bdc530b6febac665db27aab60e03ec840
> 
> I will submit this upstream once the kernel side has landed.

LGTM, thanks Hans

Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Mark Brown April 2, 2021, 4:45 p.m. UTC | #2 
On Fri, 2 Apr 2021 16:07:41 +0200, Hans de Goede wrote:
> Here is a patch series to enable sound on the Dell Venue 10 Pro 5055 tablet
> this series also includes 2 generic improvements to rt5672 support:
> 
> 1. Add support for boards using Bay Trail CR (SSP0) in combination with a rt5672 codec
> 2. Set the card's components string based on the DMI info, so that we don't need to
> duplicate the DMI quirks in userspace (in the UCM profile)
> 
> [...]

Applied to

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

Thanks!

[1/6] ASoC: Intel: Unify the thinkpad10 and aegex10 byt-match quirks
      commit: ebbb165d2c0c44ffbf480e209f745ed4b0d5560a
[2/6] ASoC: Intel: Baytrail: Add quirk for the Dell Venue 10 Pro 5055 tablet
      commit: 17d49b07a8bb3fdc630a44240c7d7e2a18e14b93
[3/6] ASoC: Intel: cht_bsw_rt5672: Add support for Bay Trail CR / SSP0
      commit: c9b3c63392e578ea74411b29a720ace77ae9041f
[4/6] ASoC: rt5670: Add a quirk for the Dell Venue 10 Pro 5055
      commit: 84cb0d5581b6a7bd5d96013f67e9f2eb0c7b4378
[5/6] ASoC: rt5670: Add a rt5670_components() helper
      commit: 3d534537648bd7d7a82f2becc9ded99a4b228a6a
[6/6] ASoC: Intel: cht_bsw_rt5672: Set card.components string
      commit: e992a51b1d14317f414d4b9935966dca96ac0b36

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