aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/nvdimm
diff options
context:
space:
mode:
authorJacek Anaszewski <jacek.anaszewski@gmail.com>2019-12-05 22:25:01 +0100
committerPavel <pavel@ucw.cz>2019-12-21 20:09:32 +0100
commit8e8d699b051f9ef86e31fb24569ccf3d869b54c4 (patch)
treec5d49438d687d58d8b147561c8fe6f74877a9b2f /drivers/nvdimm
parentLinux 5.5-rc2 (diff)
downloadlinux-dev-8e8d699b051f9ef86e31fb24569ccf3d869b54c4.tar.xz
linux-dev-8e8d699b051f9ef86e31fb24569ccf3d869b54c4.zip
leds: gpio: Fix uninitialized gpio label for fwnode based probe
When switching to using generic LED name composition mechanism via devm_led_classdev_register_ext() API the part of code initializing struct gpio_led's template name property was removed alongside. It was however overlooked that the property was also passed to devm_fwnode_get_gpiod_from_child() in place of "label" parameter, which when set to NULL, results in gpio label being initialized to '?'. It could be observed in debugfs and failed to properly identify gpio association with LED consumer. Fix this shortcoming by updating the GPIO label after the LED is registered and its final name is known. Fixes: d7235f5feaa0 ("leds: gpio: Use generic support for composing LED names") Cc: Russell King <linux@armlinux.org.uk> Reviewed-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Jacek Anaszewski <jacek.anaszewski@gmail.com> [fixed comment] Signed-off-by: Pavel Machek <pavel@ucw.cz>
Diffstat (limited to 'drivers/nvdimm')
0 files changed, 0 insertions, 0 deletions