[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1503446048.7266.28.camel@aj.id.au>
Date: Wed, 23 Aug 2017 09:24:08 +0930
From: Andrew Jeffery <andrew@...id.au>
To: Linus Walleij <linus.walleij@...aro.org>,
Yong Li <sdliyong@...il.com>
Cc: Joel Stanley <joel@....id.au>, Arnd Bergmann <arnd@...db.de>,
Rick Altherr <raltherr@...gle.com>,
Rob Herring <robh@...nel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] pinctrl: aspeed: Fix ast2500 strap register write
logic
Hi Linus,
On Tue, 2017-08-22 at 14:52 +0200, Linus Walleij wrote:
> > On Tue, Aug 15, 2017 at 6:21 PM, Yong Li <sdliyong@...il.com> wrote:
>
> > On AST2500, the hardware strap register(SCU70) only accepts write ‘1’,
> > to clear it to ‘0’, must set bits(write ‘1’) to SCU7C
> >
> > Signed-off-by: Yong Li <sdliyong@...il.com>
>
> Patch applied with Andrew's review/test tags.
I realised after I sent the tags on v3 that I'd made a mistake: There's a
slightly awkward to test bug in the v3 implementation. I followed up on v3 with
this:
https://lkml.org/lkml/2017/8/16/905
And Yong sent out a corresponding v4:
https://patchwork.ozlabs.org/patch/802946/
I see you've pushed Yong's v3 in pinctrl/devel - can we revert/remove that and
apply v4?
Sorry for the confusion.
Andrew
>
> Yours,
> Linus Walleij
Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)
Powered by blists - more mailing lists