summaryrefslogtreecommitdiffstats
path: root/drivers/scsi/hptiop.h
diff options
context:
space:
mode:
authorStephen Boyd <swboyd@chromium.org>2024-02-23 07:52:53 +0100
committerBartosz Golaszewski <bartosz.golaszewski@linaro.org>2024-02-27 14:17:38 +0100
commit0d776cfd5e5b559fdf2e38285c2aea4b7048acbd (patch)
tree64996d7580bfceb943773a09842ceb4ff3f7dafd /drivers/scsi/hptiop.h
parentgpio: sim: use for_each_hwgpio() (diff)
downloadlinux-0d776cfd5e5b559fdf2e38285c2aea4b7048acbd.tar.xz
linux-0d776cfd5e5b559fdf2e38285c2aea4b7048acbd.zip
gpiolib: Pass consumer device through to core in devm_fwnode_gpiod_get_index()
This devm API takes a consumer device as an argument to setup the devm action, but throws it away when calling further into gpiolib. This leads to odd debug messages like this: (NULL device *): using DT '/gpio-keys/switch-pen-insert' for '(null)' GPIO lookup Let's pass the consumer device down, by directly calling what fwnode_gpiod_get_index() calls but pass the device used for devm. This changes the message to look like this instead: gpio-keys gpio-keys: using DT '/gpio-keys/switch-pen-insert' for '(null)' GPIO lookup Note that callers of fwnode_gpiod_get_index() will still see the NULL device pointer debug message, but there's not much we can do about that because the API doesn't take a struct device. Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com> Fixes: 8eb1f71e7acc ("gpiolib: consolidate GPIO lookups") Signed-off-by: Stephen Boyd <swboyd@chromium.org> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Diffstat (limited to 'drivers/scsi/hptiop.h')
0 files changed, 0 insertions, 0 deletions