From: Grant Likely <grant.likely@secretlab.ca>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: broonie@opensource.wolfsonmicro.com,
linus.walleij@stericsson.com, rdunlap@xenotime.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH V2 0/3] Open drain/open source support from gpio library
Date: Mon, 5 Mar 2012 07:50:14 -0700 [thread overview]
Message-ID: <20120305145014.GA27229@ponder.secretlab.ca> (raw)
In-Reply-To: <1329490582-22107-1-git-send-email-ldewangan@nvidia.com>
On Fri, Feb 17, 2012 at 08:26:18PM +0530, Laxman Dewangan wrote:
> This patch is as per discussion on the patch
> [PATCH V1] regulator: fixed: Support for open-drain gpio
> where it was suggested to push the handling of open drain gpios
> into the gpio libray.
>
> This is series of patches to add support of the open drain and open
> source gpios in standard gpio library.
> - Added GPIOF_OPEN_DRAIN flag so that client can request the
> gpio with this flag. Handle open drain gpio configuration properly.
> - Added GPIOF_OPEN_SOURCE flag so that client can request the
> gpio with this flag. Handle open source gpio configuration properly.
> - Gpio documentation changes to have support for open-drain.
>
> From the patch series of V1, it is discussed to
> - remove the sysfs interface supportsi for open drain.
> - Added open source support as a new change.
>
> Laxman Dewangan (3):
> Documentation: gpio: Add details of open-drain/source configuration
> gpio: gpiolib: Support for open drain/collector gpios
> gpio: gpiolib: Support for open source/emitter gpios
Applied, thanks
g.
>
> Documentation/gpio.txt | 17 +++++++++-
> drivers/gpio/gpiolib.c | 83 ++++++++++++++++++++++++++++++++++++++++++++++-
> include/linux/gpio.h | 6 +++
> 3 files changed, 102 insertions(+), 4 deletions(-)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2012-03-05 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 14:56 [PATCH V2 0/3] Open drain/open source support from gpio library Laxman Dewangan
[not found] ` <1329490582-22107-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-02-17 14:56 ` Laxman Dewangan
[not found] ` <1329490582-22107-2-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-02-17 18:21 ` Linus Walleij
2012-02-27 12:45 ` Laxman Dewangan
2012-02-17 14:56 ` [PATCH V2 1/3] Documentation: gpio: Add details of open-drain/source configuration Laxman Dewangan
2012-02-17 14:56 ` [PATCH V2 2/3] gpio: gpiolib: Support for open drain/collector gpios Laxman Dewangan
[not found] ` <1329490582-22107-4-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-02-17 16:37 ` Mark Brown
2012-02-17 14:56 ` [PATCH V2 3/3] gpio: gpiolib: Support for open source/emitter gpios Laxman Dewangan
[not found] ` <1329490582-22107-5-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-02-17 16:30 ` Mark Brown
2012-03-05 14:50 ` Grant Likely [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=20120305145014.GA27229@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=ldewangan@nvidia.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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).