[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1ebc15b559d74ace9a1171548f79f978@svr-chch-ex1.atlnz.lc>
Date: Wed, 16 May 2018 20:58:35 +0000
From: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To: Linus Walleij <linus.walleij@...aro.org>
CC: Gregory Clement <gregory.clement@...tlin.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jason Cooper <jason@...edaemon.net>,
"Andrew Lunn" <andrew@...n.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] pinctrl: mvebu: use correct MPP sel value for dev pins
On 17/05/18 00:55, Linus Walleij wrote:
> On Mon, May 7, 2018 at 4:25 AM, Chris Packham
> <chris.packham@...iedtelesis.co.nz> wrote:
>
>> The "dev" function is selected with the value 0x4 not 0x01.
>>
>> Fixes: commit d7ae8f8dee7f ("pinctrl: mvebu: pinctrl driver for 98DX3236 SoC")
>> Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz>
>
> Patch applied.
>
> Does it need to go into fixes? Stable?
By "fixes" do you mean into 4.17? Yes please.
Stable would be good. Although all the boards I'm aware of rely on the
pin configuration being done by the bootloader so I've not heard of
anyone experiencing problems.
Powered by blists - more mailing lists