mirror of
https://github.com/torvalds/linux
synced 2024-10-07 20:05:15 +00:00
06188bc80c
The root devices show some odd behaviours compared to regular "bus" devices that have been probed through the usual mechanism, so let's create kunit tests to exercise those paths and odd cases. It's not clear whether root devices are even allowed to use device managed resources, but the fact that it works in some cases but not others like shown in that test suite shouldn't happen either way: we want to make it consistent and documented. These tests will (after the following patches) ensure that consistency and effectively document that it's allowed. If it ever turns out to be a bad idea, we can always roll back and modify the tests then. Reviewed-by: David Gow <davidgow@google.com> Signed-off-by: Maxime Ripard <mripard@kernel.org> Link: https://lore.kernel.org/r/20230720-kunit-devm-inconsistencies-test-v3-1-6aa7e074f373@kernel.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
20 lines
591 B
Plaintext
20 lines
591 B
Plaintext
# SPDX-License-Identifier: GPL-2.0
|
|
config TEST_ASYNC_DRIVER_PROBE
|
|
tristate "Build kernel module to test asynchronous driver probing"
|
|
depends on m
|
|
help
|
|
Enabling this option produces a kernel module that allows
|
|
testing asynchronous driver probing by the device core.
|
|
The module name will be test_async_driver_probe.ko
|
|
|
|
If unsure say N.
|
|
|
|
config DM_KUNIT_TEST
|
|
tristate "KUnit Tests for the device model" if !KUNIT_ALL_TESTS
|
|
depends on KUNIT
|
|
|
|
config DRIVER_PE_KUNIT_TEST
|
|
bool "KUnit Tests for property entry API" if !KUNIT_ALL_TESTS
|
|
depends on KUNIT=y
|
|
default KUNIT_ALL_TESTS
|