Message ID | 20250203141051.2361323-1-cezary.rojewski@intel.com (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: Intel: avs: Add support for MalibouLake configuration | expand |
On Mon, 03 Feb 2025 15:10:40 +0100, Cezary Rojewski wrote: > The avs-driver is the go-to driver for Intel Automotive. MalibouLake > (MBL) and RedondoLake (RDL) are representatives of the project. These > inherit majority of the featureset from RaptorLake-M (RPL-M) and > AlderLake-N (ADL-N) respectively. The onboard codec for these is TI's > pcm3168a. > > In summary, the patchset: > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/11] ASoC: codecs: pcm3168a: Add ACPI match table commit: dc561ab16d8be9cbe8f07a49a7b2f5428fbcfeea [02/11] ASoC: codecs: pcm3168a: Relax probing conditions commit: e92f042642aed6f6206caace892d9df2d0166841 [03/11] ASoC: codecs: pcm3168a: Allow for 24-bit in provider mode commit: 7d92a38d67e5d937b64b20aa4fd14451ee1772f3 [04/11] ASoC: Intel: avs: Add pcm3168a machine board commit: 79ebb596201c86712fe38b0ef73d25d07b932664 [05/11] ASoC: Intel: avs: pcm3168a board selection commit: b9fb91692af881736f8fa1741fa0dbadf07d99ee [06/11] ASoC: Intel: avs: Move DSP-boot steps into individual functions commit: e995c51903384be1c7aead246dc30cb5244179ac [07/11] ASoC: Intel: avs: Configure basefw on TGL-based platforms commit: cbe37a4d2b3c25d2e2a94097e09b6d87461b8833 [08/11] ASoC: Intel: avs: New gateway configuration mechanism commit: f0173cbe7fa79eafbdf32eed32337209f84ddacd [09/11] ASoC: Intel: avs: Remove unused gateway configuration code commit: 320155a61f7fc810a915644e9e2a451bdcea90b1 [10/11] ASoC: Intel: avs: Add WHM module support commit: 4343af66b8e1df1d3a2e6f1f8612506cb45b2afd [11/11] ALSA: hda: Select avs-driver by default on MBL commit: 856366dc924a9561dae39f252b45dfd6cc6895ce 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