From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Andrew Ruder <andy@aeruder.net>
Cc: linux-gpio@vger.kernel.org, Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] gpio: pca953x: fix gpio input on gpio offsets >= 8
Date: Mon, 12 Aug 2013 12:27:49 +0200 [thread overview]
Message-ID: <5208B8A5.3030702@free-electrons.com> (raw)
In-Reply-To: <20130807215240.GA31924@gmail.com>
On 07/08/2013 23:52, Andrew Ruder wrote:
> This change fixes a regression introduced by commit
> f5f0b7aa8 (gpio: pca953x: make the register access by GPIO bank)
>
> When the pca953x driver was converted to using 8-bit reads/writes
> the bitmask in pca953x_gpio_get_value wasn't adjusted with a
> modulus BANK_SZ and consequently looks at the wrong bits in the
> input register.
Good catch. I forgot this one and as on my board I wasn't able to
test the input I didn't noticed it.
Thanks
Reviewed-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
>
> Signed-off-by: Andrew Ruder <andrew.ruder@elecsyscorp.com>
> ---
>
> drivers/gpio/gpio-pca953x.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpio/gpio-pca953x.c b/drivers/gpio/gpio-pca953x.c
> index 426c51d..1a7ab13 100644
> --- a/drivers/gpio/gpio-pca953x.c
> +++ b/drivers/gpio/gpio-pca953x.c
> @@ -308,7 +308,7 @@ static int pca953x_gpio_get_value(struct gpio_chip *gc, unsigned off)
> return 0;
> }
>
> - return (reg_val & (1u << off)) ? 1 : 0;
> + return (reg_val & (1u << (off % BANK_SZ))) ? 1 : 0;
> }
>
> static void pca953x_gpio_set_value(struct gpio_chip *gc, unsigned off, int val)
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next parent reply other threads:[~2013-08-12 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130807215240.GA31924@gmail.com>
2013-08-12 10:27 ` Gregory CLEMENT [this message]
2013-08-14 13:44 ` [PATCH] gpio: pca953x: fix gpio input on gpio offsets >= 8 Andrew Ruder
2013-08-16 15:19 ` Linus Walleij
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=5208B8A5.3030702@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=andy@aeruder.net \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.