[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <2fe78085-2ae1-42dc-ad96-b16703ca3abd@app.fastmail.com>
Date: Mon, 30 Jan 2023 15:03:15 +1030
From: "Andrew Jeffery" <andrew@...id.au>
To: "Joel Stanley" <joel@....id.au>,
"Linus Walleij" <linus.walleij@...aro.org>
Cc: "Billy Tsai" <billy_tsai@...eedtech.com>,
linux-aspeed@...ts.ozlabs.org, openbmc@...ts.ozlabs.org,
linux-gpio@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] pinctrl: aspeed: Force to disable the function's signal
On Mon, 30 Jan 2023, at 13:36, Joel Stanley wrote:
> On Fri, 27 Jan 2023 at 12:39, Linus Walleij <linus.walleij@...aro.org> wrote:
>>
>> On Thu, Jan 19, 2023 at 2:54 AM Joel Stanley <joel@....id.au> wrote:
>>
>> > As foreseen by Andrew, this caused a regression. On the Romulus
>> > machine the device tree contains a gpio hog for GPIO S7. With the
>> > patch applied:
>>
>> OK shall I just revert the patch?
>
> Yep! I was going to send a revert but I thought I should write up a
> commit message. If you're happy just putting a revert in with a note
> that it caused a regression that's enough for me.
Agree, let's revert this one for now.
Andrew
Powered by blists - more mailing lists