From: Markus Pargmann <mpa-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Alexandre Courbot
<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
Markus Pargmann <mpa-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Subject: [PATCH v3 0/2] gpiolib: Initializing GPIOs using DT property gpio-initval
Date: Tue, 17 Nov 2015 11:07:56 +0100 [thread overview]
Message-ID: <1447754878-21099-1-git-send-email-mpa@pengutronix.de> (raw)
Hi,
I completely forgot this series. Here is an update.
This series adds a gpio-initval property to the devicetree. It provides a way
to initialize GPIOs to a defined value.
In v3 I splitted the patch into dt-bindings and the gpiolib patch. This series
is now based on v4.4-rc1. gpiod_initialize() does not use common code with
gpiod_hog anymore.
Best Regards,
Markus
Markus Pargmann (2):
dt-bindings: GPIO: Add gpio-initval
gpiolib: Add GPIO initialization
Documentation/devicetree/bindings/gpio/gpio.txt | 34 ++++++++++++++++---------
drivers/gpio/gpiolib-of.c | 13 ++++++----
drivers/gpio/gpiolib.c | 24 +++++++++++++++++
drivers/gpio/gpiolib.h | 2 ++
4 files changed, 56 insertions(+), 17 deletions(-)
--
2.6.2
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2015-11-17 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 10:07 Markus Pargmann [this message]
[not found] ` <1447754878-21099-1-git-send-email-mpa-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-11-17 10:07 ` [PATCH v3 1/2] dt-bindings: GPIO: Add gpio-initval Markus Pargmann
2015-11-17 20:35 ` Rob Herring
2015-11-18 10:20 ` Linus Walleij
2015-11-17 10:07 ` [PATCH v3 2/2] gpiolib: Add GPIO initialization Markus Pargmann
2015-11-17 10:21 ` Markus Pargmann
2015-11-29 21:32 ` Linus Walleij
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=1447754878-21099-1-git-send-email-mpa@pengutronix.de \
--to=mpa-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).