From: Mark Brown <broonie@kernel.org>
To: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: [PATCH 0/3] regmap: Add interface for checking if a register is cached
Date: Mon, 17 Jul 2023 21:33:02 +0100 [thread overview]
Message-ID: <20230717-regmap-cache-check-v1-0-73ef688afae3@kernel.org> (raw)
HDA has a use case for checking if a register is present in the cache
which it awkwardly open codes with use of _cache_only() and a read,
provide a direct API for this.
---
Mark Brown (3):
regmap: Let users check if a register is cached
regmap: Provide test for regcache_reg_present()
ALSA: hda: Use regcache_reg_cached() rather than open coding
drivers/base/regmap/regcache.c | 23 ++++++++++++++++++++++
drivers/base/regmap/regmap-kunit.c | 40 ++++++++++++++++++++++++++++++++++++++
include/linux/regmap.h | 1 +
sound/hda/hdac_regmap.c | 9 +++------
4 files changed, 67 insertions(+), 6 deletions(-)
---
base-commit: 3953d5c79c21defa716624a8623c4157c0f2fee0
change-id: 20230716-regmap-cache-check-6f6939f41ed5
Best regards,
--
Mark Brown <broonie@kernel.org>
next reply other threads:[~2023-07-17 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 20:33 Mark Brown [this message]
2023-07-17 20:33 ` [PATCH 1/3] regmap: Let users check if a register is cached Mark Brown
2023-07-17 20:33 ` [PATCH 2/3] regmap: Provide test for regcache_reg_present() Mark Brown
2023-07-17 20:33 ` [PATCH 3/3] ALSA: hda: Use regcache_reg_cached() rather than open coding Mark Brown
2023-07-18 5:46 ` [PATCH 0/3] regmap: Add interface for checking if a register is cached Takashi Iwai
2023-07-18 13:56 ` Mark Brown
2023-07-19 13:33 ` 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=20230717-regmap-cache-check-v1-0-73ef688afae3@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.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