From: Linus Walleij <linus.walleij@linaro.org>
To: Axel Lin <axel.lin@ingics.com>
Cc: Alexandre Courbot <gnurou@gmail.com>,
Gerhard Sittig <gsi@denx.de>, Fabian Vogt <fabian@ritter-vogt.de>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v2] gpio: zevio: Get correct gpio output value
Date: Tue, 22 Apr 2014 14:29:19 +0200 [thread overview]
Message-ID: <CACRpkdbFMPLbTfbUHMOX-GDZFAN3xGooy58evn+KEowUoHDn3Q@mail.gmail.com> (raw)
In-Reply-To: <1396915179.4729.1.camel@phoenix>
On Tue, Apr 8, 2014 at 1:59 AM, Axel Lin <axel.lin@ingics.com> wrote:
> Read gpio output value from ZEVIO_GPIO_OUTPUT.
> The spin_lock is required to ensure the direction is not changed before reading
> input/ouput value.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
OK out of patience waiting for ACKs, v2 patch applied.
Yours,
Linus Walleij
prev parent reply other threads:[~2014-04-22 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 23:59 [PATCH v2] gpio: zevio: Get correct gpio output value Axel Lin
2014-04-10 17:56 ` Linus Walleij
2014-04-11 0:16 ` Axel Lin
2014-04-22 12:29 ` Linus Walleij [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=CACRpkdbFMPLbTfbUHMOX-GDZFAN3xGooy58evn+KEowUoHDn3Q@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=axel.lin@ingics.com \
--cc=fabian@ritter-vogt.de \
--cc=gnurou@gmail.com \
--cc=gsi@denx.de \
--cc=linux-gpio@vger.kernel.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).