Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Simon Trimmer <simont@opensource.cirrus.com>
To: broonie@kernel.org
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@opensource.cirrus.com, Vijendar.Mukunda@amd.com,
	syed.sabakareem@amd.com,
	Simon Trimmer <simont@opensource.cirrus.com>
Subject: [PATCH 0/4] ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts
Date: Tue, 27 Jan 2026 17:34:45 +0000	[thread overview]
Message-ID: <cover.1769534442.git.simont@opensource.cirrus.com> (raw)

This patch series adds a number of ACP7.0 match table entries that are
being used in customer products.

Some of the configurations are very similar so the series begins with
renaming and sorting the existing structures so that the end result is
easier to manage.

Simon Trimmer (4):
  ASoC: amd: acp: Sort match table into most specific first
  ASoC: amd: acp: Rename Cirrus Logic component match entries to include
    link and uid
  ASoC: amd: acp: Sort Cirrus Logic match entries
  ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts

 sound/soc/amd/acp/amd-acp70-acpi-match.c | 328 ++++++++++++++++++++---
 1 file changed, 292 insertions(+), 36 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-01-27 17:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27 17:34 Simon Trimmer [this message]
2026-01-27 17:34 ` [PATCH 1/4] ASoC: amd: acp: Sort match table into most specific first Simon Trimmer
2026-01-27 17:34 ` [PATCH 2/4] ASoC: amd: acp: Rename Cirrus Logic component match entries to include link and uid Simon Trimmer
2026-01-27 17:34 ` [PATCH 3/4] ASoC: amd: acp: Sort Cirrus Logic match entries Simon Trimmer
2026-01-27 17:34 ` [PATCH 4/4] ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts Simon Trimmer
2026-02-03 12:05 ` [PATCH 0/4] " 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=cover.1769534442.git.simont@opensource.cirrus.com \
    --to=simont@opensource.cirrus.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=syed.sabakareem@amd.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