From: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
To: Andrey Smirnov <andrew.smirnov@gmail.com>,
Trent Piepho <tpiepho@kymetacorp.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>,
"cphealy@gmail.com" <cphealy@gmail.com>
Subject: Re: [PATCH 2/4] gpiolib: Add code to support "active low" GPIOs
Date: Thu, 25 May 2017 09:36:09 +0300 [thread overview]
Message-ID: <38ca9996-beb8-19a2-99ee-2a4fa7a82232@cogentembedded.com> (raw)
In-Reply-To: <CAHQ1cqEoXNdQA=1kCtxpC3dmJhYGiBY5PBxAOFCwBbZyJ5nj+w@mail.gmail.com>
> IMHO, whether any of likes it or not, OF_GPIO_ACTIVE_LOW is an
> existing feature and the only technical question is if it should be
> supported by Barebox on per-driver basis or if there should be a
> central API for it.
>
> Sascha, are you still OK with me proceeding with making and using an
> API, or should I just scrap that and handle this as a part of my
> "usb-no-xcev"?
Is support for case when this usb-no-xcev's gpio is active high needed?
If yes, then your questions above are valid.
If no, then there is third option, completely ignore this aspect of
device tree and just assume that gpio is active low.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-05-25 6:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 15:24 [PATCH 1/4] gpio-imx: Do not use gpio_set_value() Andrey Smirnov
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 [this message]
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=38ca9996-beb8-19a2-99ee-2a4fa7a82232@cogentembedded.com \
--to=nikita.yoush@cogentembedded.com \
--cc=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=cphealy@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=tpiepho@kymetacorp.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