mbox series

[0/2] regmap: Provide basic test coverage for raw I/O

Message ID 20230610-regcache-raw-kunit-v1-0-583112cd28ac@kernel.org
Headers
Series regmap: Provide basic test coverage for raw I/O |

Message

Mark Brown June 11, 2023, 1:25 p.m. UTC 
  Our existing coverage only deals with buses that provide single register
read and write operations, extend it to cover raw buses using a similar
approach with a RAM backed register map that the tests can inspect to
check operations.  This coverage could be more complete but provides a
good start.

Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (2):
      regmap: Provide a ram backed regmap with raw support
      regmap: Provide basic KUnit coverage for the raw register I/O

 drivers/base/regmap/Makefile         |   2 +-
 drivers/base/regmap/internal.h       |   8 +
 drivers/base/regmap/regmap-kunit.c   | 327 +++++++++++++++++++++++++++++++++++
 drivers/base/regmap/regmap-raw-ram.c | 133 ++++++++++++++
 4 files changed, 469 insertions(+), 1 deletion(-)
---
base-commit: 9561de3a55bed6bdd44a12820ba81ec416e705a7
change-id: 20230610-regcache-raw-kunit-3d866fb82485

Best regards,

Comments

Mark Brown June 12, 2023, 5:15 p.m. UTC | #1 
On Sun, 11 Jun 2023 14:25:01 +0100, Mark Brown wrote:
> Our existing coverage only deals with buses that provide single register
> read and write operations, extend it to cover raw buses using a similar
> approach with a RAM backed register map that the tests can inspect to
> check operations.  This coverage could be more complete but provides a
> good start.
> 
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/2] regmap: Provide a ram backed regmap with raw support
      commit: 65dd2f671875b1d97b6fa9bcf7677f5e1c55f776
[2/2] regmap: Provide basic KUnit coverage for the raw register I/O
      commit: 155a6bd6375b584c8bdbf963b8ddef672ff9aca3

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark