devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Gregory Clement <gregory.clement@bootlin.com>
Cc: linux-pwm@vger.kernel.org, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/4] ARM: dts: armada-38x: Fix compatible string for gpios
Date: Tue, 1 Nov 2022 23:44:25 +0100	[thread overview]
Message-ID: <20221101224425.huygrjriyhjwov5x@pali> (raw)
In-Reply-To: <20221009120558.nb6mxipaijrhszt6@pali>

PING?

On Sunday 09 October 2022 14:05:58 Pali Rohár wrote:
> PING
> 
> On Saturday 01 October 2022 01:34:53 Pali Rohár wrote:
> > Gregory: ping
> > 
> > On Thursday 14 July 2022 20:33:27 Pali Rohár wrote:
> > > Armada 38x supports per CPU interrupts for gpios, like Armada XP. Pre-XP
> > > variants like Armada 370 do not support per CPU interrupts for gpios.
> > > 
> > > So change compatible string for Armada 38x from "marvell,armada-370-gpio"
> > > which indicates pre-XP variant to "marvell,armadaxp-gpio" which indicates
> > > XP variant or new.
> > > 
> > > Driver gpio-mvebu.c which handles both pre-XP and XP variants already
> > > provides support for per CPU interrupts on XP and newer variants.
> > > 
> > > Signed-off-by: Pali Rohár <pali@kernel.org>
> > > Fixes: 7cb2acb3fbae ("ARM: dts: mvebu: Add PWM properties for armada-38x")
> > > ---
> > >  arch/arm/boot/dts/armada-38x.dtsi | 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/arch/arm/boot/dts/armada-38x.dtsi b/arch/arm/boot/dts/armada-38x.dtsi
> > > index df3c8d1d8f64..9343de6947b3 100644
> > > --- a/arch/arm/boot/dts/armada-38x.dtsi
> > > +++ b/arch/arm/boot/dts/armada-38x.dtsi
> > > @@ -292,7 +292,7 @@
> > >  			};
> > >  
> > >  			gpio0: gpio@18100 {
> > > -				compatible = "marvell,armada-370-gpio",
> > > +				compatible = "marvell,armadaxp-gpio",
> > >  					     "marvell,orion-gpio";
> > >  				reg = <0x18100 0x40>, <0x181c0 0x08>;
> > >  				reg-names = "gpio", "pwm";
> > > @@ -310,7 +310,7 @@
> > >  			};
> > >  
> > >  			gpio1: gpio@18140 {
> > > -				compatible = "marvell,armada-370-gpio",
> > > +				compatible = "marvell,armadaxp-gpio",
> > >  					     "marvell,orion-gpio";
> > >  				reg = <0x18140 0x40>, <0x181c8 0x08>;
> > >  				reg-names = "gpio", "pwm";
> > > -- 
> > > 2.20.1
> > > 

  reply	other threads:[~2022-11-01 22:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 11:55 [PATCH 1/4] gpio: mvebu: Fix check for pwm support on non-A8K platforms Pali Rohár
2022-07-14 11:55 ` [PATCH 2/4] doc: gpio-mvebu: Add information about Armada 38x and Armada 39x Pali Rohár
2022-07-14 11:55 ` [PATCH 3/4] ARM: dts: armada-38x: Fix compatible string for gpios Pali Rohár
2022-07-14 11:55 ` [PATCH 4/4] ARM: dts: armada-39x: " Pali Rohár
2022-07-14 13:14 ` [PATCH 1/4] gpio: mvebu: Fix check for pwm support on non-A8K platforms Baruch Siach
2022-07-14 13:19 ` Andrew Lunn
2022-07-14 18:33 ` [PATCH v2 " Pali Rohár
2022-07-14 18:33   ` [PATCH v2 2/4] doc: gpio-mvebu: Add information about Armada 38x and Armada 39x Pali Rohár
2022-07-18 21:18     ` Rob Herring
2022-07-14 18:33   ` [PATCH v2 3/4] ARM: dts: armada-38x: Fix compatible string for gpios Pali Rohár
2022-07-16 14:40     ` Uwe Kleine-König
2022-07-16 14:50       ` Pali Rohár
2022-07-16 15:07         ` Uwe Kleine-König
2022-07-16 16:09           ` Pali Rohár
2022-07-25 20:04             ` Uwe Kleine-König
2022-08-31 14:30               ` Pali Rohár
2022-09-30 23:34     ` Pali Rohár
2022-10-09 12:05       ` Pali Rohár
2022-11-01 22:44         ` Pali Rohár [this message]
2022-11-28  0:05     ` Gregory CLEMENT
2022-12-31  7:18       ` Klaus Kudielka
2022-11-28 20:24     ` Chris Packham
2022-07-14 18:33   ` [PATCH v2 4/4] ARM: dts: armada-39x: " Pali Rohár
2022-11-28  0:05     ` Gregory CLEMENT
2022-09-24 10:34   ` [PATCH v2 1/4] gpio: mvebu: Fix check for pwm support on non-A8K platforms Pali Rohár
2022-09-26  7:20   ` Bartosz Golaszewski

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=20221101224425.huygrjriyhjwov5x@pali \
    --to=pali@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).