From: Andrew Lunn <andrew@lunn.ch>
To: Klaus Kudielka <klaus.kudielka@gmail.com>
Cc: "Gregory Clement" <gregory.clement@bootlin.com>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Pali Rohár" <pali@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Chris Packham" <chris.packham@alliedtelesis.co.nz>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Revert "ARM: dts: armada-39x: Fix compatible string for gpios"
Date: Sat, 7 Jan 2023 18:18:36 +0100 [thread overview]
Message-ID: <Y7mpbOUmRYWw+8Wj@lunn.ch> (raw)
In-Reply-To: <20230107144149.5743-2-klaus.kudielka@gmail.com>
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@gmail.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2023-01-07 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 14:41 [PATCH v2 1/2] Revert "ARM: dts: armada-38x: Fix compatible string for gpios" Klaus Kudielka
2023-01-07 14:41 ` [PATCH v2 2/2] Revert "ARM: dts: armada-39x: " Klaus Kudielka
2023-01-07 17:18 ` Andrew Lunn [this message]
2023-01-09 20:31 ` Gregory CLEMENT
2023-01-07 17:18 ` [PATCH v2 1/2] Revert "ARM: dts: armada-38x: " Andrew Lunn
2023-01-14 15:58 ` Pali Rohár
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y7mpbOUmRYWw+8Wj@lunn.ch \
--to=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=klaus.kudielka@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=u.kleine-koenig@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox