Changes in led-test.c

f088104d837a991c65e51fa30bb4196169b3244d - Merge drm/drm-next into drm-intel-gt-next

Tue, 16 Sep 2025 12:53:20 +0200

Merge drm/drm-next into drm-intel-gt-nextBackmerge in order to get the commit: 048832a3f400 ("drm/i915: Refactor shmem_pwrite() to use kiocb and write_iter")To drm-intel-gt-next as there are followup fixes to be applied.Signed-off-by: Joonas Lahtinen List of files: /linux/drivers/leds/led-test.c

ab93e0dd72c37d378dd936f031ffb83ff2bd87ce - Merge branch 'next' into for-linus

Wed, 06 Aug 2025 19:08:54 +0200

Merge branch 'next' into for-linusPrepare input updates for 6.17 merge window. List of files: /linux/drivers/leds/led-test.c

a7bee4e7f78089c101be2ad51f4b5ec64782053e - Merge tag 'ib-mfd-gpio-input-pwm-v6.17' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd into next

Mon, 04 Aug 2025 08:28:48 +0200

Merge tag 'ib-mfd-gpio-input-pwm-v6.17' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd into nextMerge an immutable branch between MFD, GPIO, Input and PWM to resolveconflicts for the merge window pull request. List of files: /linux/drivers/leds/led-test.c

e9ef810dfee7a2227da9d423aecb0ced35faddbe - Merge branch 'for-6.17/amd-sfh' into for-linus

Thu, 31 Jul 2025 22:36:25 +0200

Merge branch 'for-6.17/amd-sfh' into for-linus- add support for operating modes (Basavaraj Natikar) List of files: /linux/drivers/leds/led-test.c

74f1af95820fc2ee580a775a3a17c416db30b38c - Merge remote-tracking branch 'drm/drm-next' into msm-next

Sun, 29 Jun 2025 04:54:49 +0200

Merge remote-tracking branch 'drm/drm-next' into msm-nextBack-merge drm-next to (indirectly) get arm-smmu updates for makingstall-on-fault more reliable.Signed-off-by: Rob Clark List of files: /linux/drivers/leds/led-test.c

c598d5eb9fb331ba17bc9ad67ae9a2231ca5aca5 - Merge drm/drm-next into drm-misc-next

Wed, 11 Jun 2025 09:01:34 +0200

Merge drm/drm-next into drm-misc-nextBackmerging to forward to v6.16-rc1Signed-off-by: Thomas Zimmermann List of files: /linux/drivers/leds/led-test.c

86e2d052c2320bf12571a5d96b16c2745e1cfc5e - Merge drm/drm-next into drm-xe-next

Mon, 09 Jun 2025 18:26:55 +0200

Merge drm/drm-next into drm-xe-nextBackmerging to bring in 6.16Signed-off-by: Thomas Hellström List of files: /linux/drivers/leds/led-test.c

34c55367af96f62e89221444f04487440ebc6487 - Merge drm/drm-next into drm-intel-next

Mon, 09 Jun 2025 11:40:46 +0200

Merge drm/drm-next into drm-intel-nextSync to v6.16-rc1, among other things to get the fixed size GENMASK_U*()and BIT_U*() macros.Signed-off-by: Jani Nikula List of files: /linux/drivers/leds/led-test.c

b546608ea2151eebfca515d362bc400645e02d4f - Merge tag 'leds-next-6.16' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/leds

Tue, 03 Jun 2025 21:10:31 +0200

Merge tag 'leds-next-6.16' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/ledsPull LED updates from Lee Jones: "LED Triggers: - Allow writing "default" to the sysfs 'trigger' attribute to set an LED to its default trigger - If the default trigger is "none", writing "default" will remove the current trigger - Updated sysfs ABI documentation for the new "default" trigger functionality LED KUnit Testing: - Provide a skeleton KUnit test suite for the LEDs framework - Expand the LED class device registration KUnit test to cover more scenarios, including 'brightness_get' behavior - Add KUnit tests for the LED lookup and get API ('led_add_lookup', 'devm_led_get') LED Flash Class: - Add support for setting flash/strobe duration through a new 'duration_set' op and 'led_set_flash_duration()' function, aligning with 'V4L2_CID_FLASH_DURATION' Texas Instruments TPS6131x: - Add a new driver for the TPS61310/TPS61311 flash LED controllers - The driver supports the device's three constant-current sinks for flash and torch modes LED Core: - Prevent potential 'snprintf()' truncations in LED names by checking for buffer overflows ChromeOS EC LEDs: - Avoid a -Wflex-array-member-not-at-end GCC warning by replacing an on-stack flexible structure definition with a utility function call Multicolor LEDs: - Fix issue where setting multi_intensity while software blinking is active could stop blinking PCA955x LEDs: - Avoid potential buffer overflow when creating default labels by changing a field's type to 'u8' and updating format specifiers PCA995x LEDs: - Fix a typo (stray space) in an 'of_device_id' entry in the 'pca995x_of_match' table Kconfig: - Prevent LED drivers from being enabled by default when 'COMPILE_TEST' is set Device Property API: - Split 'device_get_child_node_count()' into a new helper 'fwnode_get_child_node_count()' that doesn't require a device struct, making the API more symmetrical Driver Modernization (using 'fwnode_get_child_node_count()'): - Update 'leds-pwm-multicolor', 'leds-ncp5623' and 'leds-ncp5623' to use the new 'fwnode_get_child_node_count()' helper, removing their custom implementation - As above in the USB Type-C TCPM driver Driver Modernization (using new GPIO setter callbacks): - Convert 'leds-lgm-sso' to use new GPIO line value setter callbacks which return an integer for error handling - Convert 'leds-pca955x', 'leds-pca9532' and 'leds-tca6507' to use new GPIO setter callbacks Documentation: - Remove the '.rst' extension for 'leds-st1202' in the documentation index for consistency LP8860 LEDs: - Use 'regmap_multi_reg_write()' for EEPROM writes instead of manual looping - Use scoped mutex guards and 'devm_mutex_init()' to simplify function exits and ensure automatic cleanup - Remove default register definitions that are unused when regmap caching is not active - Use 'devm_regulator_get_enable_optional()' to handle the optional regulator, simplifying enabling and removing manual disabling - Refactor 'lp8860_unlock_eeprom()' to only perform the unlock operation, removing the lock part and an unnecessary parameter - Use a 'devm' action to disable the enable-GPIO, simplifying cleanup and error paths, and remove the now-empty '.remove()' function Turris Omnia LEDs: - Drop unnecessary commas in terminator entries of 'struct attribute' and 'struct of_device_id' arrays MT6370 RGB LEDs: - Use the 'LINEAR_RANGE()' for defining 'struct linear_range' entries to improve robustness Texas Instruments TPS6131x: - Add new devicetree bindings for the TI TPS61310/TPS61311 flash LED driver"* tag 'leds-next-6.16' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/leds: (31 commits) leds: tps6131x: Add support for Texas Instruments TPS6131X flash LED driver dt-bindings: leds: Add Texas Instruments TPS6131x flash LED driver leds: flash: Add support for flash/strobe duration leds: rgb: leds-mt6370-rgb: Improve definition of some struct linear_range leds: led-test: Provide tests for the lookup and get infrastructure leds: led-test: Fill out the registration test to cover more test cases leds: led-test: Remove standard error checking after KUNIT_ASSERT_*() leds: pca995x: Fix typo in pca995x_of_match's of_device_id entry leds: Provide skeleton KUnit testing for the LEDs framework leds: tca6507: Use new GPIO line value setter callbacks leds: pca9532: Use new GPIO line value setter callbacks leds: pca955x: Use new GPIO line value setter callbacks leds: lgm-sso: Use new GPIO line value setter callbacks leds: Do not enable by default during compile testing leds: turris-omnia: Drop commas in the terminator entries leds: lp8860: Disable GPIO with devm action leds: lp8860: Only unlock in lp8860_unlock_eeprom() leds: lp8860: Enable regulator using enable_optional helper leds: lp8860: Remove default regs when not caching leds: lp8860: Use new mutex guards to cleanup function exits ... List of files: /linux/drivers/leds/led-test.c

cfa40f29df08c7ad296c81a2fac677830af83ec7 - leds: led-test: Provide tests for the lookup and get infrastructure

Thu, 01 May 2025 10:19:13 +0200

leds: led-test: Provide tests for the lookup and get infrastructureThis API allows providers to offer an specific LED to be looked-up by aconsumer. Consumers are then able to describe the aforementioned LEDand take a reference on it.For convenience, we're testing both sides of the API in just one testfunction here. In reality, both the provider and the consumer would belogistically orthogonal.CMD: tools/testing/kunit/kunit.py run --kunitconfig drivers/ledsRESULTS: [16:38:57] Configuring KUnit Kernel ... [16:38:57] Building KUnit Kernel ... Populating config with: $ make ARCH=um O=.kunit olddefconfig Building with: $ make all compile_commands.json scripts_gdb ARCH=um O=.kunit --jobs=20 [16:39:02] Starting KUnit Kernel (1/1)... [16:39:02] ============================================================ Running tests with: $ .kunit/linux kunit.enable=1 mem=1G console=tty kunit_shutdown=halt [16:39:03] ===================== led (2 subtests) ===================== [16:39:03] [PASSED] led_test_class_register [16:39:03] [PASSED] led_test_class_add_lookup_and_get [16:39:03] ======================= [PASSED] led ======================= [16:39:03] ============================================================ [16:39:03] Testing complete. Ran 2 tests: passed: 2 [16:39:03] Elapsed time: 6.255s total, 0.001s configuring, 5.131s building, 1.106s runningLink: https://lore.kernel.org/r/20250501081918.3621432-3-lee@kernel.orgSigned-off-by: Lee Jones List of files: /linux/drivers/leds/led-test.c

eb58933b78cdad9b879dc2dd248e7284341a1cfc - leds: led-test: Fill out the registration test to cover more test cases

Thu, 01 May 2025 10:19:12 +0200

leds: led-test: Fill out the registration test to cover more test casesUpon successful LED class device registration, it is expected thatcertain attributes are filled out in pre-defined ways. For instance, ifprovided, the .brightness_get() call-back should be called to populatethe class device 'brightness' attribute, 'max_brightness' should beinitialised as LED_FULL (at least until we can rid these pesky enums)and the sysfs group should be created with the class device namesupplied by the caller.If subsequent registrations take place that would result in nameconflicts, various outcomes are expected depending on which flags areset. If LED_REJECT_NAME_CONFLICT is disabled, registration shouldsucceed resulting in an iteration on the provided name. Conversely, ifit's enabled, then registration is expected to fail outright.We test for all of these scenarios here.Link: https://lore.kernel.org/r/20250501081918.3621432-2-lee@kernel.orgSigned-off-by: Lee Jones List of files: /linux/drivers/leds/led-test.c

1d7f25483c8791f395dd857cce8a6a65bcfa295f - leds: led-test: Remove standard error checking after KUNIT_ASSERT_*()

Thu, 01 May 2025 10:19:11 +0200

leds: led-test: Remove standard error checking after KUNIT_ASSERT_*()If a KUNIT_ASSERT_*() call ends up in an assertion, the test is markedas a failure and the subsequent error checking is never executed, makingit superfluous. Remove it for simplicity and to avoid confusion.Link: https://lore.kernel.org/r/20250501081918.3621432-1-lee@kernel.orgSigned-off-by: Lee Jones List of files: /linux/drivers/leds/led-test.c

5039a33fed8851fcf384fae2bcb8fd4858edd597 - leds: Provide skeleton KUnit testing for the LEDs framework

Thu, 24 Apr 2025 16:45:38 +0200

leds: Provide skeleton KUnit testing for the LEDs frameworkApply a very basic implementation of KUnit LED testing.More tests / use-cases will be added steadily over time.CMD: tools/testing/kunit/kunit.py run --kunitconfig drivers/ledsOUTPUT: [15:34:19] Configuring KUnit Kernel ... [15:34:19] Building KUnit Kernel ... Populating config with: $ make ARCH=um O=.kunit olddefconfig Building with: $ make all compile_commands.json scripts_gdb ARCH=um O=.kunit --jobs=20 [15:34:22] Starting KUnit Kernel (1/1)... [15:34:22] ============================================================ Running tests with: $ .kunit/linux kunit.enable=1 mem=1G console=tty kunit_shutdown=halt [15:34:23] ===================== led (1 subtest) ====================== [15:34:23] [PASSED] led_test_class_register [15:34:23] ======================= [PASSED] led ======================= [15:34:23] ============================================================ [15:34:23] Testing complete. Ran 1 tests: passed: 1 [15:34:23] Elapsed time: 4.268s total, 0.001s configuring, 3.048s building, 1.214s runningLink: https://lore.kernel.org/r/20250424144544.1438584-1-lee@kernel.orgSigned-off-by: Lee Jones List of files: /linux/drivers/leds/led-test.c