From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/3] gpiolib: introduce gpio initializer
Date: Mon, 9 Oct 2017 21:27:05 +0200 [thread overview]
Message-ID: <20171009192705.4qlbv6twvw7xklw4@pengutronix.de> (raw)
In-Reply-To: <20171006042900.nqfe5vsmgogcoxxh@pengutronix.de>
Hello Sascha,
On Fri, Oct 06, 2017 at 06:29:00AM +0200, Sascha Hauer wrote:
> On Tue, Sep 26, 2017 at 11:26:43PM +0200, Uwe Kleine-König wrote:
> > the target of this series is to allow gpios to be initialized but
> > without the side effect that the gpios are unusable then (as is the case
> > with gpio-hogs).
> >
> > This can for example be used to prevent debug pins from floating when
> > unused or keep a chip in reset until a matching driver is available.
> >
> > I already tried to fix the binding, no feedback so far.
> > See http://patchwork.ozlabs.org/patch/817695/ .
>
> I'm delaying this for some time in the hope that upstream settles to
> some solution.
IMHO patches 1 and 2 can already go in. They are clean up and
optimisation that are IMOH worth to have even without the last patch.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-10-09 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 21:26 Uwe Kleine-König
2017-09-26 21:26 ` [PATCH 1/3] gpiolib: reorder functions Uwe Kleine-König
2017-09-26 21:26 ` [PATCH 2/3] gpiolib: introduce helper functions working on gpio_info structs Uwe Kleine-König
2017-09-26 21:26 ` [PATCH 3/3] gpiolib: introduce gpio initializer Uwe Kleine-König
2017-10-06 4:29 ` [PATCH 0/3] " Sascha Hauer
2017-10-09 19:27 ` Uwe Kleine-König [this message]
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=20171009192705.4qlbv6twvw7xklw4@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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