aboutsummaryrefslogtreecommitdiff
path: root/drivers/gpio/gpio-brcmstb.c
diff options
context:
space:
mode:
authorGravatar Andy Shevchenko <andriy.shevchenko@linux.intel.com> 2024-02-21 23:31:56 +0200
committerGravatar Bartosz Golaszewski <bartosz.golaszewski@linaro.org> 2024-04-17 22:46:44 +0200
commit8a7a6103258715857310253ec2193bcc4d1d7082 (patch)
tree2d4eb722e036e87b3a313b525d5dbc4f82d2d612 /drivers/gpio/gpio-brcmstb.c
parentgpio: regmap: Use -ENOTSUPP consistently (diff)
downloadlinux-8a7a6103258715857310253ec2193bcc4d1d7082.tar.gz
linux-8a7a6103258715857310253ec2193bcc4d1d7082.tar.bz2
linux-8a7a6103258715857310253ec2193bcc4d1d7082.zip
gpiolib: Get rid of never false gpio_is_valid() calls
In the cases when gpio_is_valid() is called with unsigned parameter the result is always true in the GPIO library code, hence the check for false won't ever be true. Get rid of such calls. While at it, move GPIO device base to be unsigned to clearly show it won't ever be negative. This requires a new definition for the maximum GPIO number in the system. Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Reviewed-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Diffstat (limited to 'drivers/gpio/gpio-brcmstb.c')
0 files changed, 0 insertions, 0 deletions