From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
Cc: "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>,
alsa-devel@alsa-project.org, patches@opensource.cirrus.com,
asahi@lists.linux.dev
Subject: Re: [PATCH 04/10] ASoC: cs35l35: Use maple tree register cache
Date: Tue, 13 Jun 2023 17:25:07 +0000 [thread overview]
Message-ID: <20230613172507.GQ68926@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <20230609-asoc-cirrus-maple-v1-4-b806c4cbd1d4@kernel.org>
On Sat, Jun 10, 2023 at 02:56:24PM +0100, Mark Brown wrote:
> The cs35l35 can only support single register read and write operations
> so does not benefit from block writes. This means it gets no benefit from
> using the rbtree register cache over the maple tree register cache so
> convert it to use maple trees instead, it is more modern.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
A little late to the party, but for what it is worth on this
cs35l35 one:
Tested-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Thanks,
Charles
next prev parent reply other threads:[~2023-06-13 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 13:56 [PATCH 00/10] ASoC: Use maple tree for Cirrus Logic devices Mark Brown
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 [this message]
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=20230613172507.GQ68926@ediswmail.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=asahi@lists.linux.dev \
--cc=broonie@kernel.org \
--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).