From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: haibo.chen@nxp.com, linus.walleij@linaro.org, brgl@bgdev.pl
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-imx@nxp.com
Subject: Re: [PATCH] gpio: gpio-vf610: do not touch other bits when set the target bit
Date: Tue, 10 May 2022 17:02:27 +0800 [thread overview]
Message-ID: <4b18b894-8f81-8865-06c4-d112aaa85c8b@oss.nxp.com> (raw)
In-Reply-To: <1651920846-31721-1-git-send-email-haibo.chen@nxp.com>
On 2022/5/7 18:54, haibo.chen@nxp.com wrote:
> From: Haibo Chen <haibo.chen@nxp.com>
>
> For gpio controller contain register PDDR, when set one target bit,
> current logic will clear all other bits, this is wrong. Use operator
> '|=' to fix it.
>
A fixes tag required, since this is a fix. With fixes tag added:
Reviewed-by: Peng Fan <peng.fan@nxp.com>
Regards,
Peng.
> Signed-off-by: Haibo Chen <haibo.chen@nxp.com>
> ---
> drivers/gpio/gpio-vf610.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpio/gpio-vf610.c b/drivers/gpio/gpio-vf610.c
> index 20780c35da1b..23cddb265a0d 100644
> --- a/drivers/gpio/gpio-vf610.c
> +++ b/drivers/gpio/gpio-vf610.c
> @@ -125,9 +125,13 @@ static int vf610_gpio_direction_output(struct gpio_chip *chip, unsigned gpio,
> {
> struct vf610_gpio_port *port = gpiochip_get_data(chip);
> unsigned long mask = BIT(gpio);
> + u32 val;
>
> - if (port->sdata && port->sdata->have_paddr)
> - vf610_gpio_writel(mask, port->gpio_base + GPIO_PDDR);
> + if (port->sdata && port->sdata->have_paddr) {
> + val = vf610_gpio_readl(port->gpio_base + GPIO_PDDR);
> + val |= mask;
> + vf610_gpio_writel(val, port->gpio_base + GPIO_PDDR);
> + }
>
> vf610_gpio_set(chip, gpio, value);
>
>
prev parent reply other threads:[~2022-05-10 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 10:54 [PATCH] gpio: gpio-vf610: do not touch other bits when set the target bit haibo.chen
2022-05-10 9:02 ` Peng Fan (OSS) [this message]
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=4b18b894-8f81-8865-06c4-d112aaa85c8b@oss.nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=brgl@bgdev.pl \
--cc=haibo.chen@nxp.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@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 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).