Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Liao, Bard" <yung-chuan.liao@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
	Oder Chiou <oder_chiou@realtek.com>,
	Liam Girdwood <lgirdwood@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/8] ASoC: Use the maple tree register cache for RealTek SoundWire CODECs
Date: Wed, 14 Jun 2023 09:15:36 +0800	[thread overview]
Message-ID: <7af52548-a87a-dd18-5f28-6dc0f029e7ce@linux.intel.com> (raw)
In-Reply-To: <20230609-asoc-rt-sdw-maple-v1-0-85ee50c93905@kernel.org>

On 6/10/2023 10:27 PM, Mark Brown wrote:
> The RealTek SoundWire CODECs don't support bulk register operations so
> they gain no advantage from using the rbtree cache, convert them to use
> the maple tree cache instead - it is more modern.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>

Tested on a Dell laptop with rt1316, rt711-sdca, and rt715-sdca.

Tested-by: Bard Liao <yung-chuan.liao@linux.intel.com>

> ---
> Mark Brown (8):
>        ASoC: rt700: Use maple tree register cache
>        ASoC: rt711: Use maple tree register cache
>        ASoC: rt712: Use maple tree register cache
>        ASoC: rt715: Use maple tree register cache
>        ASoC: rt722: Use maple tree register cache
>        ASoC: rt1308: Use maple tree register cache
>        ASoC: rt1316: Use maple tree register cache
>        ASoC: rt1318: Use maple tree register cache
>
>   sound/soc/codecs/rt1308-sdw.c      | 2 +-
>   sound/soc/codecs/rt1316-sdw.c      | 2 +-
>   sound/soc/codecs/rt1318-sdw.c      | 2 +-
>   sound/soc/codecs/rt700-sdw.c       | 2 +-
>   sound/soc/codecs/rt711-sdca-sdw.c  | 4 ++--
>   sound/soc/codecs/rt711-sdw.c       | 2 +-
>   sound/soc/codecs/rt712-sdca-dmic.c | 4 ++--
>   sound/soc/codecs/rt712-sdca-sdw.c  | 4 ++--
>   sound/soc/codecs/rt715-sdca-sdw.c  | 4 ++--
>   sound/soc/codecs/rt722-sdca-sdw.c  | 4 ++--
>   10 files changed, 15 insertions(+), 15 deletions(-)
> ---
> base-commit: 08e6c4bb17087584261c4aff555d32fc1c620b81
> change-id: 20230609-asoc-rt-sdw-maple-fa6714ac4318
>
> Best regards,

  parent reply	other threads:[~2023-06-14  1:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10 14:27 [PATCH 0/8] ASoC: Use the maple tree register cache for RealTek SoundWire CODECs Mark Brown
2023-06-10 14:27 ` [PATCH 1/8] ASoC: rt700: Use maple tree register cache Mark Brown
2023-06-10 14:27 ` [PATCH 2/8] ASoC: rt711: " Mark Brown
2023-06-10 14:27 ` [PATCH 3/8] ASoC: rt712: " Mark Brown
2023-06-10 14:27 ` [PATCH 4/8] ASoC: rt715: " Mark Brown
2023-06-10 14:27 ` [PATCH 5/8] ASoC: rt722: " Mark Brown
2023-06-10 14:27 ` [PATCH 6/8] ASoC: rt1308: " Mark Brown
2023-06-10 14:27 ` [PATCH 7/8] ASoC: rt1316: " Mark Brown
2023-06-10 14:27 ` [PATCH 8/8] ASoC: rt1318: " Mark Brown
2023-06-14  1:15 ` Liao, Bard [this message]
2023-06-15 12:53 ` [PATCH 0/8] ASoC: Use the maple tree register cache for RealTek SoundWire CODECs Mark Brown
2023-06-26 13:30 ` [BUG] " Mukunda,Vijendar
2023-06-26 13:29   ` Mark Brown
2023-06-26 14:39     ` Mukunda,Vijendar
2023-06-27  5:20       ` Mukunda,Vijendar

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=7af52548-a87a-dd18-5f28-6dc0f029e7ce@linux.intel.com \
    --to=yung-chuan.liao@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.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