[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160205134317.GE12071@box2.japko.eu>
Date: Fri, 5 Feb 2016 14:43:18 +0100
From: Krzysztof Adamski <k@...ko.eu>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Maxime Ripard <maxime.ripard@...e-electrons.com>,
Chen-Yu Tsai <wens@...e.org>,
Hans de Goede <hdegoede@...hat.com>,
Lee Jones <lee@...nel.org>, Rob Herring <robh@...nel.org>,
Jens Kuske <jenskuske@...il.com>,
Fabian Frederick <fabf@...net.be>,
Vishnu Patekar <vishnupatekar0510@...il.com>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-sunxi <linux-sunxi@...glegroups.com>
Subject: Re: [PATCH v2] pinctrl: sunxi: H3 requires irq_read_needs_mux
On Fri, Feb 05, 2016 at 02:39:23PM +0100, Linus Walleij wrote:
>On Wed, Feb 3, 2016 at 8:57 AM, Krzysztof Adamski <k@...ko.eu> 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@...ko.eu>
>
>2. Is this a regression that need to go in to fixes?
Not sure what you mean by that. H3 support was added recently without
this flag so it never worked properly on this SoC. With this patch it
does. So it's just a normal bug fix, not a regression.
Best regards,
Krzysztof Adamski
Powered by blists - more mailing lists