Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Cezary Rojewski <cezary.rojewski@intel.com>
To: alsa-devel@alsa-project.org, broonie@kernel.org
Cc: tiwai@suse.com, perex@perex.cz, zhuning@everest-semi.com,
	amadeuszx.slawinski@linux.intel.com,
	pierre-louis.bossart@linux.intel.com, hdegoede@redhat.com,
	Cezary Rojewski <cezary.rojewski@intel.com>
Subject: [PATCH 0/8] ASoC: Intel: avs: New boards and fixes to existing ones
Date: Thu, 29 Jun 2023 13:24:41 +0200	[thread overview]
Message-ID: <20230629112449.1755928-1-cezary.rojewski@intel.com> (raw)

Series adds support for two boards: es8336 and rt5663. The former is
utilized by some KBL-based tablets whereas the latter unlocks
Chromebooks with rt5663 i2c codecs.

As existing implementation of es8336 (es8316.c) codec driver is not
prepared to cope with KBL-based platforms, couple of small,
clock-related changes precede anything avs-driver related.

The tail of patchset cleans up existing implementation of rt5682.

Amadeusz Sławiński (2):
  ASoC: Intel: avs: Add rt5663 machine board
  ASoC: Intel: avs: Load rt5663 board on KBL-based platforms

Cezary Rojewski (6):
  ASoC: codecs: es8316: Add support for 24 MHz MCLK
  ASoC: codecs: es8316: Add support for S24_3LE format
  ASoC: Intel: avs: Add es8336 machine board
  ASoC: Intel: avs: Load es8336 board on KBL-based platforms
  ASoC: Intel: avs: rt5682: Add missing components
  ASoC: Intel: avs: rt5682: Tidy up hw_params()

 sound/soc/codecs/es8316.c             |   5 +-
 sound/soc/intel/avs/board_selection.c |  16 ++
 sound/soc/intel/avs/boards/Kconfig    |  20 ++
 sound/soc/intel/avs/boards/Makefile   |   4 +
 sound/soc/intel/avs/boards/es8336.c   | 315 ++++++++++++++++++++++++++
 sound/soc/intel/avs/boards/rt5663.c   | 254 +++++++++++++++++++++
 sound/soc/intel/avs/boards/rt5682.c   |  67 +++---
 7 files changed, 652 insertions(+), 29 deletions(-)
 create mode 100644 sound/soc/intel/avs/boards/es8336.c
 create mode 100644 sound/soc/intel/avs/boards/rt5663.c

-- 
2.25.1


             reply	other threads:[~2023-06-29 11:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 11:24 Cezary Rojewski [this message]
2023-06-29 11:24 ` [PATCH 1/8] ASoC: codecs: es8316: Add support for 24 MHz MCLK Cezary Rojewski
2023-06-29 11:24 ` [PATCH 2/8] ASoC: codecs: es8316: Add support for S24_3LE format Cezary Rojewski
2023-06-29 11:24 ` [PATCH 3/8] ASoC: Intel: avs: Add es8336 machine board Cezary Rojewski
2023-06-29 11:24 ` [PATCH 4/8] ASoC: Intel: avs: Load es8336 board on KBL-based platforms Cezary Rojewski
2023-06-29 11:24 ` [PATCH 5/8] ASoC: Intel: avs: Add rt5663 machine board Cezary Rojewski
2023-06-29 11:24 ` [PATCH 6/8] ASoC: Intel: avs: Load rt5663 board on KBL-based platforms Cezary Rojewski
2023-06-29 11:24 ` [PATCH 7/8] ASoC: Intel: avs: rt5682: Add missing components Cezary Rojewski
2023-06-29 11:24 ` [PATCH 8/8] ASoC: Intel: avs: rt5682: Tidy up hw_params() Cezary Rojewski
2023-07-12 11:46 ` [PATCH 0/8] ASoC: Intel: avs: New boards and fixes to existing ones Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230629112449.1755928-1-cezary.rojewski@intel.com \
    --to=cezary.rojewski@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.com \
    --cc=zhuning@everest-semi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox