From: Patrice CHOTARD <patrice.chotard@st.com>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] gpio: stm32: correct the bias management
Date: Wed, 25 Nov 2020 09:43:55 +0000 [thread overview]
Message-ID: <d016ded8-fe38-4676-29ed-baf12ce4e00b@st.com> (raw)
In-Reply-To: <20201028094908.11031-2-patrick.delaunay@st.com>
Hi Patrick
On 10/28/20 10:49 AM, Patrick Delaunay wrote:
> Use the bias configuration for all the GPIO configurations and not
> only for input GPIO, as indicated in Reference manual
> (Table 81. Port bit configuration table).
>
> Fixes: 43efbb6a3ebf0223f9eab8d45916f602d876319f ("gpio: stm32: add ops get_dir_flags")
> Fixes: f13ff88b61c32ac8f0e9068c41328b265ef619eb ("gpio: stm32: add ops set_dir_flags")
> Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
> ---
>
> drivers/gpio/stm32_gpio.c | 28 ++++++++++++++--------------
> 1 file changed, 14 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/gpio/stm32_gpio.c b/drivers/gpio/stm32_gpio.c
> index b885cfb57e..51e1efd701 100644
> --- a/drivers/gpio/stm32_gpio.c
> +++ b/drivers/gpio/stm32_gpio.c
> @@ -212,11 +212,11 @@ static int stm32_gpio_set_dir_flags(struct udevice *dev, unsigned int offset,
>
> } else if (flags & GPIOD_IS_IN) {
> stm32_gpio_set_moder(regs, idx, STM32_GPIO_MODE_IN);
> - if (flags & GPIOD_PULL_UP)
> - stm32_gpio_set_pupd(regs, idx, STM32_GPIO_PUPD_UP);
> - else if (flags & GPIOD_PULL_DOWN)
> - stm32_gpio_set_pupd(regs, idx, STM32_GPIO_PUPD_DOWN);
> }
> + if (flags & GPIOD_PULL_UP)
> + stm32_gpio_set_pupd(regs, idx, STM32_GPIO_PUPD_UP);
> + else if (flags & GPIOD_PULL_DOWN)
> + stm32_gpio_set_pupd(regs, idx, STM32_GPIO_PUPD_DOWN);
>
> return 0;
> }
> @@ -243,16 +243,16 @@ static int stm32_gpio_get_dir_flags(struct udevice *dev, unsigned int offset,
> break;
> case STM32_GPIO_MODE_IN:
> dir_flags |= GPIOD_IS_IN;
> - switch (stm32_gpio_get_pupd(regs, idx)) {
> - case STM32_GPIO_PUPD_UP:
> - dir_flags |= GPIOD_PULL_UP;
> - break;
> - case STM32_GPIO_PUPD_DOWN:
> - dir_flags |= GPIOD_PULL_DOWN;
> - break;
> - default:
> - break;
> - }
> + break;
> + default:
> + break;
> + }
> + switch (stm32_gpio_get_pupd(regs, idx)) {
> + case STM32_GPIO_PUPD_UP:
> + dir_flags |= GPIOD_PULL_UP;
> + break;
> + case STM32_GPIO_PUPD_DOWN:
> + dir_flags |= GPIOD_PULL_DOWN;
> break;
> default:
> break;
Reviewed-by: Patrice Chotard <patrice.chotard@st.com>
Thanks
Patrice
next prev parent reply other threads:[~2020-11-25 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 9:49 [PATCH 1/2] pinctrl: stm32: display bias information for all pins Patrick Delaunay
2020-10-28 9:49 ` [PATCH 2/2] gpio: stm32: correct the bias management Patrick Delaunay
2020-10-28 10:15 ` Patrick DELAUNAY
2020-11-25 9:43 ` Patrice CHOTARD [this message]
2020-11-25 11:03 ` Patrick DELAUNAY
2020-11-25 9:43 ` [PATCH 1/2] pinctrl: stm32: display bias information for all pins Patrice CHOTARD
2020-11-25 11:03 ` Patrick DELAUNAY
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=d016ded8-fe38-4676-29ed-baf12ce4e00b@st.com \
--to=patrice.chotard@st.com \
--cc=u-boot@lists.denx.de \
/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