From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Krzysztof Adamski <krzysztof.adamski@sonymobile.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Chen-Yu Tsai <wens@csie.org>, Hans de Goede <hdegoede@redhat.com>,
Hongzhou Yang <hongzhou.yang@mediatek.com>,
Rob Herring <robh@kernel.org>, Jens Kuske <jenskuske@gmail.com>,
Fabian Frederick <fabf@skynet.be>,
Vishnu Patekar <vishnupatekar0510@gmail.com>,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: sunxi: H3 requires irq_read_needs_mux
Date: Tue, 2 Feb 2016 14:24:21 +0100 [thread overview]
Message-ID: <20160202132421.GT4652@lukather> (raw)
In-Reply-To: <20160202100217.GA7483@box2.japko.eu>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
On Tue, Feb 02, 2016 at 11:03:03AM +0100, Krzysztof Adamski wrote:
> It seems that on H3, just like on A10, when GPIOs are configured as
> external interrupt data registers does not contain their value. When
> value is read, GPIO function must be temporary switched to input for
> reads.
>
> Signed-off-by: Krzysztof Adamski <k@japko.eu>
Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-02 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 10:03 [PATCH] pinctrl: sunxi: H3 requires irq_read_needs_mux Krzysztof Adamski
2016-02-02 13:24 ` Maxime Ripard [this message]
2016-02-11 12:01 ` 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=20160202132421.GT4652@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=fabf@skynet.be \
--cc=hdegoede@redhat.com \
--cc=hongzhou.yang@mediatek.com \
--cc=jenskuske@gmail.com \
--cc=krzysztof.adamski@sonymobile.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=vishnupatekar0510@gmail.com \
--cc=wens@csie.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).