From: Laxman Dewangan <ldewangan@nvidia.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"linus.walleij@stericsson.com" <linus.walleij@stericsson.com>,
"w.sang@pengutronix.de" <w.sang@pengutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V1] gpio: fix bits conflict for gpio flags
Date: Mon, 14 May 2012 22:34:45 +0530 [thread overview]
Message-ID: <4FB13B2D.1000906@nvidia.com> (raw)
In-Reply-To: <1336386338-20353-1-git-send-email-ldewangan@nvidia.com>
Grant,
On Monday 07 May 2012 03:55 PM, Laxman Dewangan wrote:
> The bit 2 and 3 in GPIO flag are allocated for the
> flag OPEN_DRAIN/OPEN_SOURCE. These bits are reused
> for the flag EXPORT/EXPORT_CHANGEABLE and so creating
> conflict.
> Fix this conflict by allocating bit 4 and 5 for the
> flag EXPORT/EXPORT_CHANGEABLE.
>
> Signed-off-by: Laxman Dewangan<ldewangan@nvidia.com>
> ---
> This is broken by commit
> commit fc3a1f04f5040255cbc086c419e4237f29f89f88
> Author: Wolfram Sang<w.sang@pengutronix.de>
>
> gpio: add flags to export GPIOs when requesting
>
It would be good if it go to 3.5.
Thanks,
Laxman
prev parent reply other threads:[~2012-05-14 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 10:25 [PATCH V1] gpio: fix bits conflict for gpio flags Laxman Dewangan
2012-05-14 17:04 ` Laxman Dewangan [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=4FB13B2D.1000906@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=w.sang@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;
as well as URLs for NNTP newsgroup(s).