From: Mark Brown <broonie@kernel.org>
To: Hector Martin <marcan@marcan.st>,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [PATCH 1/2] regmap: kunit: Fix marking of the range window as volatile
Date: Mon, 23 Oct 2023 18:19:11 +0100 [thread overview]
Message-ID: <20231023-regmap-test-window-cache-v1-1-d8a71f441968@kernel.org> (raw)
In-Reply-To: <20231023-regmap-test-window-cache-v1-0-d8a71f441968@kernel.org>
For some reason the regmap used for testing ranges was not including the
end of the range of paged registers as volatile since it found the end by
counting from the selector register rather than the base of the window.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
drivers/base/regmap/regmap-kunit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/base/regmap/regmap-kunit.c b/drivers/base/regmap/regmap-kunit.c
index 264d29b3fced..f79fd5ec187e 100644
--- a/drivers/base/regmap/regmap-kunit.c
+++ b/drivers/base/regmap/regmap-kunit.c
@@ -445,7 +445,7 @@ static struct regmap_range_cfg test_range = {
static bool test_range_volatile(struct device *dev, unsigned int reg)
{
if (reg >= test_range.window_start &&
- reg <= test_range.selector_reg + test_range.window_len)
+ reg <= test_range.window_start + test_range.window_len)
return true;
if (reg >= test_range.range_min && reg <= test_range.range_max)
--
2.30.2
next prev parent reply other threads:[~2023-10-23 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 17:19 [PATCH 0/2] regmap: kunit: Add test for cache sync interaction with range selectors Mark Brown
2023-10-23 17:19 ` Mark Brown [this message]
2023-10-23 17:19 ` [PATCH 2/2] regmap: kunit: Add test for cache sync interaction with ranges Mark Brown
2023-10-26 18:16 ` [PATCH 0/2] regmap: kunit: Add test for cache sync interaction with range selectors 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=20231023-regmap-test-window-cache-v1-1-d8a71f441968@kernel.org \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
/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