[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <874jszih5f.fsf@BL-laptop>
Date: Mon, 09 Jan 2023 21:31:40 +0100
From: Gregory CLEMENT <gregory.clement@...tlin.com>
To: Andrew Lunn <andrew@...n.ch>,
Klaus Kudielka <klaus.kudielka@...il.com>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Pali Rohár <pali@...nel.org>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Chris Packham <chris.packham@...iedtelesis.co.nz>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] Revert "ARM: dts: armada-39x: Fix compatible
string for gpios"
Andrew Lunn <andrew@...n.ch> writes:
> On Sat, Jan 07, 2023 at 03:41:49PM +0100, Klaus Kudielka wrote:
>> This reverts commit d10886a4e6f85ee18d47a1066a52168461370ded.
>>
>> If compatible = "marvell,armadaxp-gpio", the reg property requires a
>> second (address, size) pair, which points to the per-CPU interrupt
>> registers <0x18800 0x30> / <0x18840 0x30>.
>>
>> Furthermore:
>> Commit 5f79c651e81e explains very well, why the gpio-mvebu driver does not
>> work reliably with per-CPU interrupts.
>> Commit 988c8c0cd04d deprecates compatible = marvell,armadaxp-gpio for this
>> reason.
>>
>> Signed-off-by: Klaus Kudielka <klaus.kudielka@...il.com>
>
> Reviewed-by: Andrew Lunn <andrew@...n.ch>
Applied on mvebu/fixes
Thanks,
Gregory
>
> Andrew
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
Powered by blists - more mailing lists