From: Linus Walleij <linus.walleij@linaro.org>
To: linux-gpio@vger.kernel.org, Thierry Reding <treding@nvidia.com>,
Daniel Krueger <daniel.krueger@systec-electronic.com>,
Jean Delvare <jdelvare@suse.de>
Cc: Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH 14/54] gpio: pch: Be sure to clamp return value
Date: Tue, 22 Dec 2015 15:20:54 +0100 [thread overview]
Message-ID: <1450794054-22948-1-git-send-email-linus.walleij@linaro.org> (raw)
As we want gpio_chip .get() calls to be able to return negative
error codes and propagate to drivers, we need to go over all
drivers and make sure their return values are clamped to [0,1].
We do this by using the ret = !!(val) design pattern.
Cc: Thierry Reding <treding@nvidia.com>
Cc: Daniel Krueger <daniel.krueger@systec-electronic.com>
Cc: Jean Delvare <jdelvare@suse.de>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
drivers/gpio/gpio-pch.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/gpio-pch.c b/drivers/gpio/gpio-pch.c
index af0715f8524b..8c45b74dcf21 100644
--- a/drivers/gpio/gpio-pch.c
+++ b/drivers/gpio/gpio-pch.c
@@ -127,7 +127,7 @@ static int pch_gpio_get(struct gpio_chip *gpio, unsigned nr)
{
struct pch_gpio *chip = container_of(gpio, struct pch_gpio, gpio);
- return ioread32(&chip->reg->pi) & (1 << nr);
+ return !!(ioread32(&chip->reg->pi) & (1 << nr));
}
static int pch_gpio_direction_output(struct gpio_chip *gpio, unsigned nr,
--
2.4.3
next reply other threads:[~2015-12-22 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 14:20 Linus Walleij [this message]
2016-01-04 9:41 ` [PATCH 14/54] gpio: pch: Be sure to clamp return value Jean Delvare
2016-01-05 9:46 ` Linus Walleij
2016-01-05 13:21 ` Jean Delvare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1450794054-22948-1-git-send-email-linus.walleij@linaro.org \
--to=linus.walleij@linaro.org \
--cc=daniel.krueger@systec-electronic.com \
--cc=jdelvare@suse.de \
--cc=linux-gpio@vger.kernel.org \
--cc=treding@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).