From: Vinod Koul <vkoul@kernel.org>
To: Andy Gross <andy.gross@linaro.org>, David Brown <david.brown@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Vinod Koul <vkoul@kernel.org>
Subject: [PATCH 11/17] arm64: dts: qcom: pms405: add gpios
Date: Tue, 30 Oct 2018 15:41:02 +0530 [thread overview]
Message-ID: <20181030101108.11041-12-vkoul@kernel.org> (raw)
In-Reply-To: <20181030101108.11041-1-vkoul@kernel.org>
Add the GPIOs present on PMS405 chip.
Signed-off-by: Vinod Koul <vkoul@kernel.org>
---
arch/arm64/boot/dts/qcom/pms405.dtsi | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/pms405.dtsi b/arch/arm64/boot/dts/qcom/pms405.dtsi
index cdb4547c998b..18410d9f0f8f 100644
--- a/arch/arm64/boot/dts/qcom/pms405.dtsi
+++ b/arch/arm64/boot/dts/qcom/pms405.dtsi
@@ -17,5 +17,21 @@
reg-names = "rtc", "alarm";
interrupts = <0x0 0x61 0x1 IRQ_TYPE_NONE>;
};
+
+ pms405_gpios: gpios@c000 {
+ compatible = "qcom,pms405-gpio";
+ reg = <0xc000>;
+ gpio-controller;
+ #gpio-cells = <2>;
+ interrupts = <0 0xc1 0 IRQ_TYPE_NONE>,
+ <0 0xc2 0 IRQ_TYPE_NONE>,
+ <0 0xc3 0 IRQ_TYPE_NONE>,
+ <0 0xc4 0 IRQ_TYPE_NONE>,
+ <0 0xc5 0 IRQ_TYPE_NONE>,
+ <0 0xc6 0 IRQ_TYPE_NONE>,
+ <0 0xc7 0 IRQ_TYPE_NONE>,
+ <0 0xca 0 IRQ_TYPE_NONE>,
+ <0 0xcb 0 IRQ_TYPE_NONE>;
+ };
};
};
--
2.14.4
next prev parent reply other threads:[~2018-10-30 10:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 10:10 [PATCH 00/17] arm64: dts: qcom: qcs404: Add Device tree nodes Vinod Koul
2018-10-30 10:10 ` [PATCH 01/17] arm64: dts: qcom: qcs404: add base dts files Vinod Koul
2018-10-30 10:10 ` [PATCH 02/17] arm64: dts: qcom: qcs404: Add reserved-memory regions Vinod Koul
2018-10-30 10:10 ` [PATCH 03/17] arm64: dts: qcom: qcs404: Add RPM GLINK related nodes Vinod Koul
2018-10-30 10:10 ` [PATCH 04/17] arm64: dts: qcom: qcs404: Add PMS405 RPM regulators Vinod Koul
2018-10-30 10:10 ` [PATCH 05/17] arm64: dts: qcom: qcs404: add smp2p nodes Vinod Koul
2018-10-30 10:10 ` [PATCH 06/17] arm64: dts: qcom: qcs404: Add TLMM pinctrl node Vinod Koul
2018-10-30 10:10 ` [PATCH 07/17] arm64: dts: qcom: qcs404: Add sdcc1 node Vinod Koul
2018-10-30 10:10 ` [PATCH 08/17] arm64: dts: qcom: pms405: add spmi node Vinod Koul
2018-10-30 10:11 ` [PATCH 09/17] arm64: dts: qcom: qcs404: " Vinod Koul
2018-10-30 10:11 ` [PATCH 10/17] arm64: dts: qcom: pms405: add rtc node Vinod Koul
2018-10-30 10:11 ` Vinod Koul [this message]
2018-10-30 10:11 ` [PATCH 12/17] arm64: dts: qcom: qcs404: Add scm firmware node Vinod Koul
2018-10-30 10:11 ` [PATCH 13/17] arm64: dts: qcom: qcs404: Add remoteproc nodes Vinod Koul
2018-10-30 10:11 ` [PATCH 14/17] arm64: dts: qcom: qcs404: add prng-ee node Vinod Koul
2018-10-30 10:11 ` [PATCH 15/17] arm64: dts: qcom: qcs404: Add BAM DMA node Vinod Koul
2018-10-30 10:11 ` [PATCH 16/17] arm64: dts: qcom: qcs404: Use BAM DMA for serial uart2 Vinod Koul
2018-10-30 10:11 ` [PATCH 17/17] arm64: dts: qcom: pms405: Add pon and pwrkey nodes Vinod Koul
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=20181030101108.11041-12-vkoul@kernel.org \
--to=vkoul@kernel.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).