[PATCH v0] arm64: dts: Add APM X-Gene standby GPIO controller DTS entries

[PATCH v0] arm64: dts: Add APM X-Gene standby GPIO controller DTS entries

[Y Vo]

Add standby domain gpio controller for APM X-Gene SoC platform.

Signed-off-by: Y Vo <yvo@apm.com>
---
 arch/arm64/boot/dts/apm/apm-storm.dtsi |   13 +++++++++++++
 1 files changed, 13 insertions(+), 0 deletions(-)

diff --git a/arch/arm64/boot/dts/apm/apm-storm.dtsi b/arch/arm64/boot/dts/apm/apm-storm.dtsi
index f1ad9c2..2e1c438 100644
--- a/arch/arm64/boot/dts/apm/apm-storm.dtsi
+++ b/arch/arm64/boot/dts/apm/apm-storm.dtsi
@@ -587,6 +587,19 @@
 			phy-names = "sata-phy";
 		};
 
+		sbgpio: sbgpio at 17001000{
+			compatible = "apm,xgene-gpio-sb";
+			reg = <0x0 0x17001000 0x0 0x400>;
+			#gpio-cells = <2>;
+			gpio-controller;
+			interrupts = 	<0x0 0x28 0x1>,
+					<0x0 0x29 0x1>,
+					<0x0 0x2a 0x1>,
+					<0x0 0x2b 0x1>,
+					<0x0 0x2c 0x1>,
+					<0x0 0x2d 0x1>;
+		};
+
 		rtc: rtc at 10510000 {
 			compatible = "apm,xgene-rtc";
 			reg = <0x0 0x10510000 0x0 0x400>;
-- 
1.7.1

[PATCH v0] arm64: dts: Add APM X-Gene standby GPIO controller DTS entries

[Linus Walleij]

On Thu, Jun 4, 2015 at 9:19 AM, Y Vo <yvo@apm.com> wrote:

> Add standby domain gpio controller for APM X-Gene SoC platform.
>
> Signed-off-by: Y Vo <yvo@apm.com>

Acked-by: Linus Walleij <linus.walleij@linaro.org>

Please funnel this through the ARM SoC tree.

Yours,
Linus Walleij

[PATCH v0] arm64: dts: Add APM X-Gene standby GPIO controller DTS entries

[Olof Johansson]

On Thu, Jun 04, 2015 at 02:19:04PM +0700, Y Vo wrote:
> Add standby domain gpio controller for APM X-Gene SoC platform.
> 
> Signed-off-by: Y Vo <yvo@apm.com>

Hi,

What does patch v0 mean here? Is this just an RFC for comments or do
you want us to apply it?

Again, same comments as I made on another patch from APM developers
today: You all send patches to us without coordination. Please find one
maintainer of the common pieces and have him/her coordinate or at least
ack these patches so we have one submaintainer to deal with instead of
the whole team. (Over time that can of course be expanded to several
people, but it's easiest to start with a single person).


Thanks,

-Olof