From: Mark Brown <broonie@kernel.org>
To: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [PATCH 0/3] regmap: Add KUnit tests for read/write checking
Date: Tue, 13 Jun 2023 21:17:41 +0100 [thread overview]
Message-ID: <20230613-regmap-kunit-read-write-v1-0-2db337c52827@kernel.org> (raw)
Since Takashi found an issue with maple tree syncing registers it
shouldn't do add some test cases that catch that case and some more
potential issues, ideally we'd run through the combination of
readability with all possible I/O calls but that's lifting for another
day. We did find one issue with missing readability checks which will
be fixed separately.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (3):
regmap: Add test that writes to write only registers are prevented
regmap: Add a test case for write only registers
regmap: Add test to make sure we don't sync to read only registers
drivers/base/regmap/regmap-kunit.c | 115 +++++++++++++++++++++++++++++++++++++
1 file changed, 115 insertions(+)
---
base-commit: ecfb8ce26d02ec136b4e1ae8c5a77d22d335057b
change-id: 20230613-regmap-kunit-read-write-024393cdbef0
Best regards,
--
Mark Brown <broonie@kernel.org>
next reply other threads:[~2023-06-13 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 20:17 Mark Brown [this message]
2023-06-13 20:17 ` [PATCH 1/3] regmap: Add test that writes to write only registers are prevented Mark Brown
2023-06-13 20:17 ` [PATCH 2/3] regmap: Add a test case for write only registers Mark Brown
2023-06-13 20:17 ` [PATCH 3/3] regmap: Add test to make sure we don't sync to read " Mark Brown
2023-06-14 17:36 ` [PATCH 0/3] regmap: Add KUnit tests for read/write checking 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=20230613-regmap-kunit-read-write-v1-0-2db337c52827@kernel.org \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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