diff options
| author | Lee Jones <[email protected]> | 2025-05-01 08:19:12 +0000 |
|---|---|---|
| committer | Lee Jones <[email protected]> | 2025-05-14 08:25:06 +0000 |
| commit | eb58933b78cdad9b879dc2dd248e7284341a1cfc (patch) | |
| tree | 42cf64d8633bbf688ea69417e2cdf59df025291e /drivers/fpga/tests/fpga-mgr-test.c | |
| parent | leds: led-test: Remove standard error checking after KUNIT_ASSERT_*() (diff) | |
| download | kernel-eb58933b78cdad9b879dc2dd248e7284341a1cfc.tar.gz kernel-eb58933b78cdad9b879dc2dd248e7284341a1cfc.zip | |
leds: led-test: Fill out the registration test to cover more test cases
Upon successful LED class device registration, it is expected that
certain attributes are filled out in pre-defined ways. For instance, if
provided, the .brightness_get() call-back should be called to populate
the class device 'brightness' attribute, 'max_brightness' should be
initialised as LED_FULL (at least until we can rid these pesky enums)
and the sysfs group should be created with the class device name
supplied by the caller.
If subsequent registrations take place that would result in name
conflicts, various outcomes are expected depending on which flags are
set. If LED_REJECT_NAME_CONFLICT is disabled, registration should
succeed resulting in an iteration on the provided name. Conversely, if
it's enabled, then registration is expected to fail outright.
We test for all of these scenarios here.
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Lee Jones <[email protected]>
Diffstat (limited to 'drivers/fpga/tests/fpga-mgr-test.c')
0 files changed, 0 insertions, 0 deletions