asahi.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "James Schulman" <james.schulman@cirrus.com>,
	"David Rhodes" <david.rhodes@cirrus.com>,
	"Richard Fitzgerald" <rf@opensource.cirrus.com>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Martin Povišer" <povik+lin@cutebit.org>
Cc: alsa-devel@alsa-project.org, patches@opensource.cirrus.com,
	 asahi@lists.linux.dev, Mark Brown <broonie@kernel.org>
Subject: [PATCH 00/10] ASoC: Use maple tree for Cirrus Logic devices
Date: Sat, 10 Jun 2023 14:56:20 +0100	[thread overview]
Message-ID: <20230609-asoc-cirrus-maple-v1-0-b806c4cbd1d4@kernel.org> (raw)

A lot of the Cirrus Logic devices only support single register
read/write operations so they get no benefit from using the rbtree cache
over the more modern maple tree cache, convert them to use maple tree.

Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (10):
      ASoC: cs35l32: Use maple tree register cache
      ASoC: cs35l33: Use maple tree register cache
      ASoC: cs35l34: Use maple tree register cache
      ASoC: cs35l35: Use maple tree register cache
      ASoC: cs4234: Use maple tree register cache
      ASoC: cs42l42: Use maple tree register cache
      ASoC: cs42l73: Use maple tree register cache
      ASoC: cs42l83: Use maple tree register cache
      ASoC: cs43130: Use maple tree register cache
      ASoC: cs35l30: Use maple tree register cache

 sound/soc/codecs/cs35l32.c     | 2 +-
 sound/soc/codecs/cs35l33.c     | 2 +-
 sound/soc/codecs/cs35l34.c     | 2 +-
 sound/soc/codecs/cs35l35.c     | 2 +-
 sound/soc/codecs/cs4234.c      | 2 +-
 sound/soc/codecs/cs42l42.c     | 2 +-
 sound/soc/codecs/cs42l73.c     | 2 +-
 sound/soc/codecs/cs42l83-i2c.c | 2 +-
 sound/soc/codecs/cs43130.c     | 2 +-
 sound/soc/codecs/cs53l30.c     | 2 +-
 10 files changed, 10 insertions(+), 10 deletions(-)
---
base-commit: 9561de3a55bed6bdd44a12820ba81ec416e705a7
change-id: 20230609-asoc-cirrus-maple-0aba1f5c18b8

Best regards,
-- 
Mark Brown <broonie@kernel.org>


             reply	other threads:[~2023-06-10 13:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10 13:56 Mark Brown [this message]
2023-06-10 13:56 ` [PATCH 01/10] ASoC: cs35l32: Use maple tree register cache Mark Brown
2023-06-10 13:56 ` [PATCH 02/10] ASoC: cs35l33: " Mark Brown
2023-06-10 13:56 ` [PATCH 03/10] ASoC: cs35l34: " Mark Brown
2023-06-10 13:56 ` [PATCH 04/10] ASoC: cs35l35: " Mark Brown
2023-06-13 17:25   ` Charles Keepax
2023-06-10 13:56 ` [PATCH 05/10] ASoC: cs4234: " Mark Brown
2023-06-10 13:56 ` [PATCH 06/10] ASoC: cs42l42: " Mark Brown
2023-06-10 13:56 ` [PATCH 07/10] ASoC: cs42l73: " Mark Brown
2023-06-10 13:56 ` [PATCH 08/10] ASoC: cs42l83: " Mark Brown
2023-06-10 13:56 ` [PATCH 09/10] ASoC: cs43130: " Mark Brown
2023-06-10 13:56 ` [PATCH 10/10] ASoC: cs35l30: " Mark Brown
2023-06-12 18:01 ` [PATCH 00/10] ASoC: Use maple tree for Cirrus Logic devices Rhodes, David
2023-06-13 16:18 ` 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=20230609-asoc-cirrus-maple-v1-0-b806c4cbd1d4@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=asahi@lists.linux.dev \
    --cc=david.rhodes@cirrus.com \
    --cc=james.schulman@cirrus.com \
    --cc=lgirdwood@gmail.com \
    --cc=patches@opensource.cirrus.com \
    --cc=povik+lin@cutebit.org \
    --cc=rf@opensource.cirrus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).