mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Tzung-Bi Shih <tzungbi@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	 Danilo Krummrich <dakr@kernel.org>,
	Johan Hovold <johan@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	 Randy Dunlap <rdunlap@infradead.org>,
	Bartosz Golaszewski <brgl@kernel.org>,
	Linus Walleij <linusw@kernel.org>,
	 driver-core@lists.linux.dev, linux-kernel@vger.kernel.org,
	 linux-gpio@vger.kernel.org
Subject: Re: [PATCH v14 4/5] reset: Add KUnit test cases
Date: Mon, 19 Oct 2026 15:32:12 +0200	[thread overview]
Message-ID: <986d1b636fc7a96b3c2e05e8725a693a496d2f62.camel@pengutronix.de> (raw)
In-Reply-To: <20261011121246.162759-5-tzungbi@kernel.org>

On So, 2026-10-11 at 20:12 +0800, Tzung-Bi Shih wrote:
> Since commit 9035073d0ef1 ("reset: convert reset core to using firmware
> nodes"), reset suppliers and consumers can be wired up using software
> nodes without requiring Device Tree or hardware devices.  Leverage this
> to add KUnit test cases for the reset controller framework.
> 
> The test cases cover the following scenarios:
> 
> - Basic: Verifies that a consumer can acquire a reset control via
>   fwnode and perform reset, assert, deassert, status, release, and
>   acquire operations.
> - Use After Unregister: Verifies that after the supplier unregisters
>   the reset_controller_dev while a consumer still holds a reset_control
>   handle, subsequent consumer operations fail safely with -ENODEV.
> - Concurrent Unregister: Verifies that unregistering the
>   reset_controller_dev concurrently with an in-flight reset operation
>   waits for the active operation to complete before returning.
> 
> Signed-off-by: Tzung-Bi Shih <tzungbi@kernel.org>

It looks like the Kunit tests are independent from the reset of the
series and could be sent individually.

Is there any dependency that I am missing?

> ---
> Test:
> $ ./tools/testing/kunit/kunit.py run \
>         --kconfig_add CONFIG_RESET_CONTROLLER=y \
>         --kconfig_add CONFIG_RESET_KUNIT_TEST=y \
>         reset_test
> 
> $ ./tools/testing/kunit/kunit.py run \
>         --kconfig_add CONFIG_RESET_CONTROLLER=y \
>         --kconfig_add CONFIG_RESET_KUNIT_TEST=y \
>         --kconfig_add CONFIG_PROVE_LOCKING=y \
>         --kconfig_add CONFIG_DEBUG_KERNEL=y \
>         --kconfig_add CONFIG_KASAN=y \
>         --arch=x86_64 \
>         reset_test
> ---
> v14:
> - New to the series.
> ---
>  drivers/reset/Kconfig     |   5 +
>  drivers/reset/Makefile    |   2 +
>  drivers/reset/core-test.c | 329 ++++++++++++++++++++++++++++++++++++++
>  3 files changed, 336 insertions(+)
>  create mode 100644 drivers/reset/core-test.c
> 
> diff --git a/drivers/reset/Kconfig b/drivers/reset/Kconfig
> index eda9c698a95f..c7dceec8f58c 100644
> --- a/drivers/reset/Kconfig
> +++ b/drivers/reset/Kconfig
> @@ -457,4 +457,9 @@ source "drivers/reset/starfive/Kconfig"
>  source "drivers/reset/sti/Kconfig"
>  source "drivers/reset/tegra/Kconfig"
>  
> +config RESET_KUNIT_TEST
> +	tristate "KUnit tests for reset controller" if !KUNIT_ALL_TESTS
> +	depends on KUNIT
> +	default KUNIT_ALL_TESTS
> +
>  endif
> diff --git a/drivers/reset/Makefile b/drivers/reset/Makefile
> index 489fafd6bbe3..bb01198d495b 100644
> --- a/drivers/reset/Makefile
> +++ b/drivers/reset/Makefile
> @@ -55,3 +55,5 @@ obj-$(CONFIG_RESET_UNIPHIER) += reset-uniphier.o
>  obj-$(CONFIG_RESET_UNIPHIER_GLUE) += reset-uniphier-glue.o
>  obj-$(CONFIG_RESET_ZYNQ) += reset-zynq.o
>  obj-$(CONFIG_RESET_ZYNQMP) += reset-zynqmp.o
> +
> +obj-$(CONFIG_RESET_KUNIT_TEST) += core-test.o
> diff --git a/drivers/reset/core-test.c b/drivers/reset/core-test.c
> new file mode 100644
> index 000000000000..834556322b23
> --- /dev/null
> +++ b/drivers/reset/core-test.c
> @@ -0,0 +1,329 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright 2026 Google LLC
> + *
> + * KUnit tests for the reset controller.
> + *
> + * The test cases cover the following scenarios:
> + *
> + * - Basic: Verifies that a consumer can acquire a reset control via
> + *   fwnode and perform reset, assert, deassert, status, release, and
> + *   acquire operations.
> + *
> + * - Use After Unregister: Verifies that after the supplier unregisters
> + *   the reset_controller_dev while a consumer still holds a reset_control
> + *   handle, subsequent consumer operations fail safely with -ENODEV.
> + *
> + * - Concurrent Unregister: Verifies that unregistering the
> + *   reset_controller_dev concurrently with an in-flight reset operation
> + *   waits for the active operation to complete before returning.
> + */
> +
> +#include <kunit/fwnode.h>
> +#include <kunit/test.h>
> +
> +#include <linux/completion.h>
> +#include <linux/fwnode.h>
> +#include <linux/iopoll.h>
> +#include <linux/kthread.h>
> +#include <linux/property.h>
> +#include <linux/reset-controller.h>
> +#include <linux/reset.h>
> +#include <linux/sched/task.h>
> +
> +struct reset_test_context {
> +	struct fwnode_handle *supp_fwnode;
> +	struct fwnode_handle *cons_fwnode;
> +	struct reset_controller_dev rcdev;
> +	struct reset_control *rstc;
> +
> +	int reset_count;
> +	int assert_count;
> +	int deassert_count;
> +	int status_count;
> +
> +	void *priv;
> +};
> +
> +static int reset_test_op_reset(struct reset_controller_dev *rcdev,
> +			       unsigned long id)
> +{
> +	struct reset_test_context *ctx = container_of(rcdev, typeof(*ctx), rcdev);
> +
> +	ctx->reset_count++;
> +	return 0;
> +}
> +
> +static int reset_test_op_assert(struct reset_controller_dev *rcdev,
> +				unsigned long id)
> +{
> +	struct reset_test_context *ctx = container_of(rcdev, typeof(*ctx), rcdev);
> +
> +	ctx->assert_count++;
> +	return 0;
> +}
> +
> +static int reset_test_op_deassert(struct reset_controller_dev *rcdev,
> +				  unsigned long id)
> +{
> +	struct reset_test_context *ctx = container_of(rcdev, typeof(*ctx), rcdev);
> +
> +	ctx->deassert_count++;
> +	return 0;
> +}
> +
> +static int reset_test_op_status(struct reset_controller_dev *rcdev,
> +				unsigned long id)
> +{
> +	struct reset_test_context *ctx = container_of(rcdev, typeof(*ctx), rcdev);
> +
> +	ctx->status_count++;
> +	return 0;
> +}
> +
> +static const struct reset_control_ops reset_test_ops = {
> +	.reset = reset_test_op_reset,
> +	.assert = reset_test_op_assert,
> +	.deassert = reset_test_op_deassert,
> +	.status = reset_test_op_status,
> +};
> +
> +static int reset_test_init(struct kunit *test)
> +{
> +	static const struct property_entry supp_props[] = {
> +		PROPERTY_ENTRY_U32("#reset-cells", 1),
> +		{}
> +	};
> +	static const struct software_node supp_swnode = {
> +		.name = "reset-test-supplier",
> +		.properties = supp_props,
> +	};
> +	static const struct software_node_ref_args refs[] = {
> +		SOFTWARE_NODE_REFERENCE(&supp_swnode, 0),
> +	};
> +	static const struct property_entry cons_props[] = {
> +		PROPERTY_ENTRY_REF_ARRAY("resets", refs),
> +		{}
> +	};
> +
> +	struct reset_test_context *ctx;
> +	int ret;
> +
> +	ctx = kunit_kzalloc(test, sizeof(*ctx), GFP_KERNEL);
> +	KUNIT_ASSERT_NOT_NULL(test, ctx);
> +
> +	ctx->supp_fwnode = kunit_software_node_register(test, &supp_swnode);
> +	KUNIT_ASSERT_NOT_ERR_OR_NULL(test, ctx->supp_fwnode);
> +
> +	ctx->cons_fwnode = kunit_fwnode_create_software_node(test, cons_props,
> +							     NULL);
> +	KUNIT_ASSERT_NOT_ERR_OR_NULL(test, ctx->cons_fwnode);
> +
> +	ctx->rcdev.ops = &reset_test_ops;
> +	ctx->rcdev.nr_resets = 1;
> +	ctx->rcdev.fwnode = ctx->supp_fwnode;
> +
> +	ret = reset_controller_register(&ctx->rcdev);
> +	KUNIT_ASSERT_EQ(test, ret, 0);
> +
> +	ctx->rstc = __fwnode_reset_control_get(ctx->cons_fwnode, NULL, 0,
> +					       RESET_CONTROL_EXCLUSIVE);
> +	KUNIT_ASSERT_NOT_ERR_OR_NULL(test, ctx->rstc);
> +
> +	test->priv = ctx;

The rcdev and rstc could be cleaned up in .exit for the error cases.

> +	return 0;
> +}
> +
> +static void reset_test_basic(struct kunit *test)
> +{
> +	struct reset_test_context *ctx = test->priv;
> +	struct reset_control *rstc = ctx->rstc;
> +
> +	KUNIT_EXPECT_EQ(test, ctx->reset_count, 0);
> +	KUNIT_EXPECT_EQ(test, reset_control_reset(rstc), 0);
> +	KUNIT_EXPECT_EQ(test, ctx->reset_count, 1);
> +
> +	KUNIT_EXPECT_EQ(test, ctx->assert_count, 0);
> +	KUNIT_EXPECT_EQ(test, reset_control_assert(rstc), 0);
> +	KUNIT_EXPECT_EQ(test, ctx->assert_count, 1);
> +
> +	KUNIT_EXPECT_EQ(test, ctx->deassert_count, 0);
> +	KUNIT_EXPECT_EQ(test, reset_control_deassert(rstc), 0);
> +	KUNIT_EXPECT_EQ(test, ctx->deassert_count, 1);
> +
> +	KUNIT_EXPECT_EQ(test, ctx->status_count, 0);
> +	KUNIT_EXPECT_EQ(test, reset_control_status(rstc), 0);
> +	KUNIT_EXPECT_EQ(test, ctx->status_count, 1);
> +
> +	reset_control_release(rstc);
> +	KUNIT_EXPECT_EQ(test, reset_control_acquire(rstc), 0);
> +
> +	reset_control_put(rstc);
> +	reset_controller_unregister(&ctx->rcdev);

Could be cleaned up by .exit.

> +}
> +
> +static void reset_test_use_after_unregister(struct kunit *test)
> +{
> +	struct reset_test_context *ctx = test->priv;
> +	struct reset_control *rstc = ctx->rstc;
> +
> +	KUNIT_EXPECT_EQ(test, ctx->reset_count, 0);
> +	KUNIT_EXPECT_EQ(test, reset_control_reset(rstc), 0);
> +	KUNIT_EXPECT_EQ(test, ctx->reset_count, 1);
> +
> +	/* Unregister supplier while consumer still holds rstc. */
> +	reset_controller_unregister(&ctx->rcdev);

If you allocate rcdev on its own instead of embedding it in the
context, you could

	reset_controller_unregister(ctx->rcdev);
	ctx->rcdev = NULL;

here and still have normal cleanup if not NULL in .exit.

> +
> +	KUNIT_EXPECT_EQ(test, ctx->reset_count, 1);
> +	KUNIT_EXPECT_EQ(test, reset_control_reset(rstc), -ENODEV);
> +	KUNIT_EXPECT_EQ(test, ctx->reset_count, 1);
> +
> +	KUNIT_EXPECT_EQ(test, reset_control_assert(rstc), -ENODEV);
> +	KUNIT_EXPECT_EQ(test, reset_control_deassert(rstc), -ENODEV);
> +	KUNIT_EXPECT_EQ(test, reset_control_status(rstc), -ENODEV);
> +
> +	reset_control_release(rstc);
> +	KUNIT_EXPECT_EQ(test, reset_control_acquire(rstc), -ENODEV);
> +
> +	reset_control_put(rstc);

This would not be required either.

> +}
> +
> +struct test_concurrent_unregister_context {
> +	struct kunit *test;
> +	struct completion started, enter;
> +	struct task_struct *thread;
> +
> +	/* Used by test consumer. */
> +	struct completion entered, exit;
> +	int expected_ret;
> +};
> +
> +static int test_concurrent_unregister_supplier(void *data)
> +{
> +	struct test_concurrent_unregister_context *ctx = data;
> +	struct reset_test_context *rtc = ctx->test->priv;
> +
> +	complete(&ctx->started);
> +
> +	wait_for_completion(&ctx->enter);
> +	reset_controller_unregister(&rtc->rcdev);
> +
> +	return 0;
> +}
> +
> +static int test_concurrent_unregister_consumer(void *data)
> +{
> +	struct test_concurrent_unregister_context *ctx = data;
> +	struct reset_test_context *rtc = ctx->test->priv;
> +	int ret;
> +
> +	complete(&ctx->started);
> +
> +	wait_for_completion(&ctx->enter);
> +
> +	ret = reset_control_reset(rtc->rstc);
> +	KUNIT_EXPECT_EQ(ctx->test, ret, ctx->expected_ret);
> +
> +	return 0;
> +}
> +
> +static int
> +reset_test_concurrent_unregister_op_reset(struct reset_controller_dev *rcdev,
> +					  unsigned long id)
> +{
> +	struct reset_test_context *rtc = container_of(rcdev, typeof(*rtc), rcdev);
> +	struct test_concurrent_unregister_context *ctx = rtc->priv;
> +
> +	rtc->reset_count++;
> +	complete(&ctx->entered);
> +
> +	wait_for_completion(&ctx->exit);
> +	return ctx->expected_ret;
> +}
> +
> +static const struct reset_control_ops reset_test_concurrent_unregister_ops = {
> +	.reset = reset_test_concurrent_unregister_op_reset,
> +};
> +
> +static void reset_test_concurrent_unregister(struct kunit *test)
> +{
> +	struct reset_test_context *rtc = test->priv;
> +	struct test_concurrent_unregister_context *ctx;
> +	int i, ret, val;
> +
> +	rtc->rcdev.ops = &reset_test_concurrent_unregister_ops;
> +
> +	ctx = kunit_kmalloc_array(test, 3, sizeof(*ctx), GFP_KERNEL);
> +	KUNIT_ASSERT_NOT_NULL(test, ctx);
> +
> +	for (i = 0; i < 3; ++i) {
> +		ctx[i].test = test;
> +		init_completion(&ctx[i].started);
> +		init_completion(&ctx[i].enter);
> +
> +		if (i == 0) {
> +			ctx[i].thread = kthread_run(
> +				test_concurrent_unregister_supplier, ctx + i,
> +				"supplier%d", i);
> +		} else {
> +			init_completion(&ctx[i].entered);
> +			init_completion(&ctx[i].exit);
> +
> +			ctx[i].thread = kthread_run(
> +				test_concurrent_unregister_consumer, ctx + i,
> +				"consumer%d", i);
> +		}
> +		KUNIT_ASSERT_FALSE(test, IS_ERR(ctx[i].thread));

Isn't this missing kthread cleanup in the error cases?

> +		get_task_struct(ctx[i].thread);
> +
> +		wait_for_completion(&ctx[i].started);
> +	}
> +
> +	rtc->priv = &ctx[1];
> +	ctx[1].expected_ret = 0x12345678;
> +	/* consumer1 enters reset(). */
> +	KUNIT_EXPECT_EQ(test, rtc->reset_count, 0);
> +	complete(&ctx[1].enter);
> +	wait_for_completion(&ctx[1].entered);
> +	KUNIT_EXPECT_EQ(test, rtc->reset_count, 1);
> +
> +	/* supplier0 unregisters. */
> +	complete(&ctx[0].enter);
> +	ret = read_poll_timeout(reset_control_status, val, val == -ENODEV,
> +				1000, 100000, false, rtc->rstc);
> +	KUNIT_ASSERT_EQ(test, ret, 0);
> +	/* supplier0 can't exit.  It's waiting for all consumers. */
> +
> +	ctx[2].expected_ret = -ENODEV;
> +	/* consumer2 must see -ENODEV. */
> +	complete(&ctx[2].enter);
> +	kthread_stop_put(ctx[2].thread);
> +
> +	/* consumer1 exits reset(). */
> +	complete(&ctx[1].exit);
> +	kthread_stop_put(ctx[1].thread);
> +	kthread_stop_put(ctx[0].thread);
> +
> +	/* Subsequent access must see -ENODEV. */
> +	KUNIT_EXPECT_EQ(test, reset_control_reset(rtc->rstc), -ENODEV);
> +	reset_control_put(rtc->rstc);

reset_control_put() could be done by .exit.

regards
Philipp

  reply	other threads:[~2026-10-19 13:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-11 12:12 [PATCH v14 0/5] drivers/base: Introduce revocable Tzung-Bi Shih
2026-10-11 12:12 ` [PATCH v14 1/5] revocable: Revocable resource management Tzung-Bi Shih
2026-10-11 12:12 ` [PATCH v14 2/5] revocable: Add KUnit test cases Tzung-Bi Shih
2026-10-11 12:12 ` [PATCH v14 3/5] gpio: Leverage revocable for accessing struct gpio_chip Tzung-Bi Shih
2026-10-11 12:12 ` [PATCH v14 4/5] reset: Add KUnit test cases Tzung-Bi Shih
2026-10-19 13:32   ` Philipp Zabel [this message]
2026-10-11 12:12 ` [PATCH v14 5/5] reset: Leverage revocable for accessing struct reset_controller_dev Tzung-Bi Shih
2026-10-15  9:49   ` Bartosz Golaszewski
2026-10-19 11:53     ` Tzung-Bi Shih
2026-10-19 12:41       ` Philipp Zabel
2026-10-19 14:05         ` Bartosz Golaszewski

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=986d1b636fc7a96b3c2e05e8725a693a496d2f62.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=brgl@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tzungbi@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

all inboxes | Powered by JetHome®