From: Michal Simek <michal.simek@xilinx.com>
To: Paul Thomas <pthomas8589@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Michal Simek <michal.simek@xilinx.com>,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Shubhrajyoti Datta <shubhraj@xilinx.com>
Subject: Re: [PATCH] GPIO, Fix bug where the wrong GPIO register is written to
Date: Mon, 27 Jan 2020 08:42:17 +0100 [thread overview]
Message-ID: <68610131-32f9-6ebb-705a-7d9303f21d3a@xilinx.com> (raw)
In-Reply-To: <20200125221410.8022-1-pthomas8589@gmail.com>
On 25. 01. 20 23:14, Paul Thomas wrote:
> Care is taken with "index", however with the current version
> the actual xgpio_writereg is using index for data but
> xgpio_regoffset(chip, i) for the offset. And since i is already
> incremented it is incorrect. This patch fixes it so that index
> is used for the offset too.
>
> Signed-off-by: Paul Thomas <pthomas8589@gmail.com>
> ---
> There are many different ways to correct this, I'd just like it to get
> fixed. I've tested this with a 5.2 kernel, but this patch is against
> 5.5rc7.
>
> drivers/gpio/gpio-xilinx.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpio/gpio-xilinx.c b/drivers/gpio/gpio-xilinx.c
> index a9748b5198e6..67f9f82e0db0 100644
> --- a/drivers/gpio/gpio-xilinx.c
> +++ b/drivers/gpio/gpio-xilinx.c
> @@ -147,9 +147,10 @@ static void xgpio_set_multiple(struct gpio_chip *gc, unsigned long *mask,
> for (i = 0; i < gc->ngpio; i++) {
> if (*mask == 0)
> break;
> + /* Once finished with an index write it out to the register */
> if (index != xgpio_index(chip, i)) {
> xgpio_writereg(chip->regs + XGPIO_DATA_OFFSET +
> - xgpio_regoffset(chip, i),
> + index * XGPIO_CHANNEL_OFFSET,
> chip->gpio_state[index]);
> spin_unlock_irqrestore(&chip->gpio_lock[index], flags);
> index = xgpio_index(chip, i);
> @@ -165,7 +166,7 @@ static void xgpio_set_multiple(struct gpio_chip *gc, unsigned long *mask,
> }
>
> xgpio_writereg(chip->regs + XGPIO_DATA_OFFSET +
> - xgpio_regoffset(chip, i), chip->gpio_state[index]);
> + index * XGPIO_CHANNEL_OFFSET, chip->gpio_state[index]);
>
> spin_unlock_irqrestore(&chip->gpio_lock[index], flags);
> }
>
Shubhrajyoti: Please take a look.
Thanks,
Michal
next prev parent reply other threads:[~2020-01-27 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 22:14 Paul Thomas
2020-01-26 21:31 ` Andrew Lunn
2020-01-27 7:42 ` Michal Simek [this message]
2020-02-10 11:52 ` Linus Walleij
2020-02-18 7:28 ` Paul Thomas
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=68610131-32f9-6ebb-705a-7d9303f21d3a@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pthomas8589@gmail.com \
--cc=shubhraj@xilinx.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
all inboxes | Powered by JetHome®