[PATCH] mxc/gpio: make _set_value work with values != 0/1
Uwe Kleine-König
u.kleine-koenig at pengutronix.de
Mon Oct 11 08:15:11 EDT 2010
Hallali,
On Mon, Oct 11, 2010 at 01:59:05PM +0200, Peter Korsgaard wrote:
> Documentation/gpio.txt specifies that the value argument to
> gpio_set_value() should be handled as a boolean (E.G. != 0 is high),
> so use the same logic as in _set_direction().
>
> Signed-off-by: Peter Korsgaard <jacmet at sunsite.dk>
> ---
> arch/arm/plat-mxc/gpio.c | 7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/plat-mxc/gpio.c b/arch/arm/plat-mxc/gpio.c
> index 57ec4a8..e226801 100644
> --- a/arch/arm/plat-mxc/gpio.c
> +++ b/arch/arm/plat-mxc/gpio.c
> @@ -234,8 +234,13 @@ static void mxc_gpio_set(struct gpio_chip *chip, unsigned offset, int value)
> u32 l;
> unsigned long flags;
>
> +
> spin_lock_irqsave(&port->lock, flags);
> - l = (__raw_readl(reg) & (~(1 << offset))) | (value << offset);
> + l = __raw_readl(reg);
> + if (value)
> + l |= 1 << offset;
> + else
> + l &= ~(1 << offset);
Why not just
l = (__raw_readl(reg) & (~(1 << offset))) | (!!value << offset);
?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
More information about the linux-arm-kernel
mailing list