linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mpa@pengutronix.de (Markus Pargmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] gpiolib: Initializing GPIOs using DT property gpio-initval
Date: Wed, 19 Aug 2015 12:35:58 +0200	[thread overview]
Message-ID: <20150819103558.GP11161@pengutronix.de> (raw)
In-Reply-To: <1439979512-3894-1-git-send-email-mpa@pengutronix.de>

On Wed, Aug 19, 2015 at 12:18:29PM +0200, Markus Pargmann wrote:
> Hi,
> 
> This series adds a gpio-initval property to the devicetree. It provides a way
> to initialize GPIOs to a defined value.
> 
> The previous patch was '[PATCH v2] gpio: Allow hogged gpios to be requested'
> which would have allowed to request hogged GPIOs. Linus suggested a separate DT
> property as hogged gpios should not be requested.
> 
> There are 3 patches. The first two simplify the function gpiod_hog. The third
> reuses the gpiod_hog()_code for a new gpiod_initialize() and adds the parsing
> of the DT.
> 
> This series is based on the series
> "[PATCH v3 0/9] gpiolib: Add GPIO name support".

Messed up all the author/signed-off-bys. I will fix it in v2 but will
wait for some feedback first.

Best regards,

Markus

> 
> Best regards,
> 
> Markus
> 
> 
> Markus Pargmann (3):
>   gpio: Use __gpiod_request directly
>   gpiolib: gpiod_hog remove separate name argument
>   gpiolib: Add GPIO initialization
> 
>  Documentation/devicetree/bindings/gpio/gpio.txt | 29 ++++++----
>  drivers/gpio/gpiolib-of.c                       | 11 +++-
>  drivers/gpio/gpiolib.c                          | 74 +++++++++++++++++--------
>  drivers/gpio/gpiolib.h                          |  6 +-
>  4 files changed, 83 insertions(+), 37 deletions(-)
> 
> -- 
> 2.4.6
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150819/bbf71c15/attachment.sig>

  parent reply	other threads:[~2015-08-19 10:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 10:18 [PATCH 0/3] gpiolib: Initializing GPIOs using DT property gpio-initval Markus Pargmann
2015-08-19 10:18 ` [PATCH 1/3] gpio: Use __gpiod_request directly Markus Pargmann
2015-09-07  8:05   ` Uwe Kleine-König
2015-08-19 10:18 ` [PATCH 2/3] gpiolib: gpiod_hog remove separate name argument Markus Pargmann
2015-09-07  8:08   ` Uwe Kleine-König
2015-09-15  8:50     ` Markus Pargmann
2015-08-19 10:18 ` [PATCH 3/3] gpiolib: Add GPIO initialization Markus Pargmann
2015-08-26 12:08   ` Linus Walleij
2015-08-19 10:35 ` Markus Pargmann [this message]
2015-09-07  9:47 ` [PATCH 0/3] gpiolib: Initializing GPIOs using DT property gpio-initval Russell King - ARM Linux

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=20150819103558.GP11161@pengutronix.de \
    --to=mpa@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).