public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Bhuvanchandra DV <bhuvanchandra.dv@toradex.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH RFT] gpio: vybrid: Fix up setting output value in vybrid_gpio_direction_output
Date: Tue, 9 Jun 2015 18:28:23 +0530	[thread overview]
Message-ID: <5576E2EF.6080400@toradex.com> (raw)
In-Reply-To: <1433841302.4157.1.camel@ingics.com>

Hello Axel,

On 06/09/2015 02:45 PM, Axel Lin wrote:
> Pass correct gpio argument to gpio_set_value().
> The calcualation of gpio = gpio + (gpios->chip * VYBRID_GPIO_COUNT);
> is required for calling imx_iomux_gpio_* functions so move them close to
> improve readability.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> Hi Bhuvanchandra,
> I think current code does not pass correct gpio argument to gpio_set_value()
> in vybrid_gpio_direction_output(). It only works if gpios->chip is 0.
> I don't have the h/w to test, can you double check this?
gpio_set_value() needs the actual gpio number to be passed not the gpio 
offset of gpio chip.

The calculation is for getting the actual gpio number from gpio offset, 
which we will need for both imx_iomux_gpio* and gpio_*_* functions.

Tested on Colibri VF50 and VF61 modules.
> Thanks,
> Axel
>   drivers/gpio/vybrid_gpio.c | 5 +++--
>   1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpio/vybrid_gpio.c b/drivers/gpio/vybrid_gpio.c
> index 6eaf0a9..33bbf54 100644
> --- a/drivers/gpio/vybrid_gpio.c
> +++ b/drivers/gpio/vybrid_gpio.c
> @@ -36,8 +36,9 @@ static int vybrid_gpio_direction_output(struct udevice *dev, unsigned gpio,
>   {
>   	const struct vybrid_gpios *gpios = dev_get_priv(dev);
>
> -	gpio = gpio + (gpios->chip * VYBRID_GPIO_COUNT);
>   	gpio_set_value(gpio, value);
> +
> +	gpio = gpio + (gpios->chip * VYBRID_GPIO_COUNT);
>   	imx_iomux_gpio_set_direction(gpio, VF610_GPIO_DIRECTION_OUT);
>
>   	return 0;
> @@ -54,6 +55,7 @@ static int vybrid_gpio_set_value(struct udevice *dev, unsigned gpio,
>   				  int value)
>   {
>   	const struct vybrid_gpios *gpios = dev_get_priv(dev);
> +
>   	if (value)
>   		writel((1 << gpio), &gpios->reg->gpio_psor);
>   	else
> @@ -68,7 +70,6 @@ static int vybrid_gpio_get_function(struct udevice *dev, unsigned gpio)
>   	u32 g_state = 0;
>
>   	gpio = gpio + (gpios->chip * VYBRID_GPIO_COUNT);
> -
>   	imx_iomux_gpio_get_function(gpio, &g_state);
>
>   	if (((g_state & (0x07 << PAD_MUX_MODE_SHIFT)) >> PAD_MUX_MODE_SHIFT) > 0)
>

Best regards,
Bhuvan

  reply	other threads:[~2015-06-09 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09  9:15 [U-Boot] [PATCH RFT] gpio: vybrid: Fix up setting output value in vybrid_gpio_direction_output Axel Lin
2015-06-09 12:58 ` Bhuvanchandra DV [this message]
2015-06-09 13:19   ` Axel Lin
2015-06-09 13:53     ` Bhuvanchandra DV
2015-06-09 14:03       ` Axel Lin

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=5576E2EF.6080400@toradex.com \
    --to=bhuvanchandra.dv@toradex.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