From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: barebox@lists.infradead.org
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>,
Nikita Yushchenko <nikita.yoush@cogentembedded.com>,
cphealy@gmail.com
Subject: [PATCH 1/4] gpio-imx: Do not use gpio_set_value()
Date: Mon, 22 May 2017 08:24:17 -0700 [thread overview]
Message-ID: <20170522152420.14443-1-andrew.smirnov@gmail.com> (raw)
Do not use gpio_set_value() in imx_gpio_direction_output() for two
reasons:
- Since we don't check gpio_set_value's result, using it
instead of imx_gpio_set_value doesn't seem to have any
advantages
- Using gpiolib's function at this level makes it hard to
implement 'active low' support (commit that follows) since
gpio driver is dealing with physical GPIO levels, whereas
gpiolib is explected to accept logical levels.
As a remedy swithch imx_gpio_direction_output() to using
imx_gpio_set_value().
Cc: cphealy@gmail.com
Cc: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com>
---
drivers/gpio/gpio-imx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/gpio-imx.c b/drivers/gpio/gpio-imx.c
index ab4f596..a9d44d4 100644
--- a/drivers/gpio/gpio-imx.c
+++ b/drivers/gpio/gpio-imx.c
@@ -93,7 +93,7 @@ static int imx_gpio_direction_output(struct gpio_chip *chip, unsigned gpio, int
void __iomem *base = imxgpio->base;
u32 val;
- gpio_set_value(gpio + chip->base, value);
+ imx_gpio_set_value(chip, gpio, value);
val = readl(base + imxgpio->regs->gdir);
val |= 1 << gpio;
--
2.9.3
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2017-05-22 15:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 15:24 Andrey Smirnov [this message]
2017-05-22 15:24 ` [PATCH 2/4] gpiolib: Add code to support "active low" GPIOs Andrey Smirnov
2017-05-23 6:30 ` Nikita Yushchenko
2017-05-23 8:33 ` Sascha Hauer
2017-05-24 0:16 ` Andrey Smirnov
2017-05-24 0:14 ` Andrey Smirnov
2017-05-24 7:26 ` Nikita Yushchenko
2017-05-24 18:16 ` Trent Piepho
2017-05-24 20:36 ` Andrey Smirnov
2017-05-25 6:36 ` Nikita Yushchenko
2017-05-25 17:10 ` Andrey Smirnov
2017-05-25 17:45 ` Sascha Hauer
2017-05-22 15:24 ` [PATCH 3/4] gpiolib: Add support for GPIO "hog" nodes Andrey Smirnov
2017-05-23 6:52 ` Nikita Yushchenko
2017-05-23 23:25 ` Andrey Smirnov
2017-05-24 6:43 ` Nikita Yushchenko
2017-05-30 14:38 ` Andrey Smirnov
2017-05-24 7:26 ` Sascha Hauer
2017-05-22 15:24 ` [PATCH 4/4] usb-nop-xceiv: Add support for 'reset-gpios' binding Andrey Smirnov
2017-05-23 6:55 ` Nikita Yushchenko
2017-05-24 0:17 ` Andrey Smirnov
2017-05-23 6:08 ` [PATCH 1/4] gpio-imx: Do not use gpio_set_value() Nikita Yushchenko
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=20170522152420.14443-1-andrew.smirnov@gmail.com \
--to=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=cphealy@gmail.com \
--cc=nikita.yoush@cogentembedded.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