From: Saravanan Sekar <sravanhome@gmail.com>
To: manivannan.sadhasivam@linaro.org, linus.walleij@linaro.org,
robh+dt@kernel.org, mark.rutland@arm.com, afaerber@suse.de,
catalin.marinas@arm.com, will.deacon@arm.com
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, pn@denx.de,
mp-cs@actions-semi.com, jeff.chen@actions-semi.com,
thomas.liau@actions-semi.com, linux@cubietech.com,
Saravanan Sekar <sravanhome@gmail.com>
Subject: [PATCH v4 5/5] arm64: dts: actions: Add pinctrl node for Actions Semi S700
Date: Tue, 31 Jul 2018 21:47:43 +0200 [thread overview]
Message-ID: <20180731194743.13678-6-sravanhome@gmail.com> (raw)
In-Reply-To: <20180731194743.13678-1-sravanhome@gmail.com>
Add pinctrl nodes for Actions Semi S700 SoC
Signed-off-by: Parthiban Nallathambi <pn@denx.de>
Signed-off-by: Saravanan Sekar <sravanhome@gmail.com>
---
arch/arm64/boot/dts/actions/s700.dtsi | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/actions/s700.dtsi b/arch/arm64/boot/dts/actions/s700.dtsi
index 59d29e4ca404..9a2c617703e5 100644
--- a/arch/arm64/boot/dts/actions/s700.dtsi
+++ b/arch/arm64/boot/dts/actions/s700.dtsi
@@ -179,5 +179,21 @@
interrupts = <GIC_SPI 11 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "timer1";
};
+
+ pinctrl: pinctrl@e01b0000 {
+ compatible = "actions,s700-pinctrl";
+ reg = <0x0 0xe01b0000 0x0 0x1000>;
+ clocks = <&cmu CLK_GPIO>;
+ gpio-controller;
+ gpio-ranges = <&pinctrl 0 0 136>;
+ #gpio-cells = <2>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ interrupts = <GIC_SPI 36 IRQ_TYPE_LEVEL_HIGH>,
+ <GIC_SPI 37 IRQ_TYPE_LEVEL_HIGH>,
+ <GIC_SPI 38 IRQ_TYPE_LEVEL_HIGH>,
+ <GIC_SPI 39 IRQ_TYPE_LEVEL_HIGH>,
+ <GIC_SPI 40 IRQ_TYPE_LEVEL_HIGH>;
+ };
};
};
--
2.18.0
next prev parent reply other threads:[~2018-07-31 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0180729200038.11795-1-sravanhome@gmail.com>
2018-07-31 19:47 ` [PATCH v4 0/5] Add Actions Semi S700 pinctrl support Saravanan Sekar
2018-07-31 19:47 ` [PATCH v4 1/5] pinctrl: actions: define constructor generic to Actions Semi SoC's Saravanan Sekar
2018-07-31 19:47 ` [PATCH v4 2/5] pinctrl: actions: define pad control configurtion to SoC specific Saravanan Sekar
2018-07-31 19:47 ` [PATCH v4 3/5] dt-bindings: pinctrl: Add bindings for Actions Semi S700 SoC Saravanan Sekar
2018-07-31 19:47 ` [PATCH v4 4/5] pinctrl: actions: Add Actions Semi S700 pinctrl driver Saravanan Sekar
2018-07-31 19:47 ` Saravanan Sekar [this message]
2018-08-01 0:45 ` [PATCH v4 5/5] arm64: dts: actions: Add pinctrl node for Actions Semi S700 kbuild test robot
2018-08-01 8:39 ` Parthiban Nallathambi
2018-08-29 7:35 ` [PATCH v4 0/5] Add Actions Semi S700 pinctrl support Linus Walleij
2018-08-29 7:41 ` Manivannan Sadhasivam
2018-08-29 7:55 ` Parthiban Nallathambi
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=20180731194743.13678-6-sravanhome@gmail.com \
--to=sravanhome@gmail.com \
--cc=afaerber@suse.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jeff.chen@actions-semi.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@cubietech.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mark.rutland@arm.com \
--cc=mp-cs@actions-semi.com \
--cc=pn@denx.de \
--cc=robh+dt@kernel.org \
--cc=thomas.liau@actions-semi.com \
--cc=will.deacon@arm.com \
/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).