public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda: Use maple tree register cache
Date: Tue, 13 Jun 2023 16:24:28 +0200	[thread overview]
Message-ID: <87v8frcueb.wl-tiwai@suse.de> (raw)
In-Reply-To: <e48bbd3b-544d-43d5-82a1-8fbbcb8cd1a4@sirena.org.uk>

On Tue, 13 Jun 2023 15:59:14 +0200,
Mark Brown wrote:
> 
> On Tue, Jun 13, 2023 at 09:36:34AM +0200, Takashi Iwai wrote:
> 
> > This is an error from regache_sync_val(), and it indicates that the
> > synced register is write-only; regcache_maple_sync() tries to sync all
> > cached values no matter whether it's writable or not, then hitting
> > this.
> 
> BTW I was just looking at reg_raw_update_once() and I can't figure out
> why it's trying to do what it's doing - it does a read to check if it's
> seen the register before and then does an _update_bits() if the register
> hasn't been cached yet, apparently trying suppress duplicate writes but
> possibly deliberately discarding changes to multiple bitfields in the
> same register.  That's not what the non-regmap path does, it'll only
> discard noop changes to the same bitfield.

Yes, it's a quite hackish way of optimization of the initialization.

Since HD-audio codec has no known default values unlike normal codecs,
it needs to initialize itself only at the first access, and this
helper does it.


Takashi

  reply	other threads:[~2023-06-13 14:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10 14:26 [PATCH] ALSA: hda: Use maple tree register cache Mark Brown
2023-06-11  7:37 ` Takashi Iwai
2023-06-13  7:36   ` Takashi Iwai
2023-06-13 13:59     ` Mark Brown
2023-06-13 14:24       ` Takashi Iwai [this message]
2023-06-13 15:49         ` Mark Brown
2023-06-13 16:15           ` Takashi Iwai
2023-06-13 16:41             ` Mark Brown
2023-06-13 17:05               ` Takashi Iwai
2023-06-13 17:29                 ` Mark Brown
2023-06-14  5:56                   ` Takashi Iwai

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=87v8frcueb.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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