From: Faiz Abbas <faiz_abbas@ti.com>
To: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: <will@kernel.org>, <robh+dt@kernel.org>, <nm@ti.com>,
<t-kristo@ti.com>, <faiz_abbas@ti.com>
Subject: [PATCH 2/8] arm64: dts: ti: k3-j7200: Add gpio nodes in wakeup domain
Date: Fri, 2 Oct 2020 00:35:35 +0530 [thread overview]
Message-ID: <20201001190541.6364-3-faiz_abbas@ti.com> (raw)
In-Reply-To: <20201001190541.6364-1-faiz_abbas@ti.com>
Similar to the gpio groups in main domain, there is one gpio group in
wakeup domain with 2 mdoules instances in it. The gpio group pins out
73 pins (5 banks). Add DT nodes for these 2 gpio module instances.
Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>
---
.../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 32 +++++++++++++++++++
1 file changed, 32 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
index eb2a78a53512..5ee64d4ee41f 100644
--- a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
@@ -107,6 +107,38 @@
ti,interrupt-ranges = <16 960 16>;
};
+ wkup_gpio0: gpio@42110000 {
+ compatible = "ti,j721e-gpio", "ti,keystone-gpio";
+ reg = <0x00 0x42110000 0x00 0x100>;
+ gpio-controller;
+ #gpio-cells = <2>;
+ interrupt-parent = <&wkup_gpio_intr>;
+ interrupts = <103>, <104>, <105>, <106>, <107>, <108>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ ti,ngpio = <73>;
+ ti,davinci-gpio-unbanked = <0>;
+ power-domains = <&k3_pds 113 TI_SCI_PD_EXCLUSIVE>;
+ clocks = <&k3_clks 113 0>;
+ clock-names = "gpio";
+ };
+
+ wkup_gpio1: gpio@42100000 {
+ compatible = "ti,j721e-gpio", "ti,keystone-gpio";
+ reg = <0x00 0x42100000 0x00 0x100>;
+ gpio-controller;
+ #gpio-cells = <2>;
+ interrupt-parent = <&wkup_gpio_intr>;
+ interrupts = <112>, <113>, <114>, <115>, <116>, <117>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ ti,ngpio = <73>;
+ ti,davinci-gpio-unbanked = <0>;
+ power-domains = <&k3_pds 114 TI_SCI_PD_EXCLUSIVE>;
+ clocks = <&k3_clks 114 0>;
+ clock-names = "gpio";
+ };
+
mcu_navss: bus@28380000 {
compatible = "simple-mfd";
#address-cells = <2>;
--
2.17.1
next prev parent reply other threads:[~2020-10-01 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 19:05 [PATCH 0/8] Add support for UHS modes in TI's J721e and J7200 boards Faiz Abbas
2020-10-01 19:05 ` [PATCH 1/8] arm64: dts: ti: k3-j7200-main: Add gpio nodes in main domain Faiz Abbas
2020-10-01 19:05 ` Faiz Abbas [this message]
2020-10-01 19:05 ` [PATCH 3/8] arm64: dts: ti: k3-j7200-common-proc-board: Disable unused gpio modules Faiz Abbas
2020-10-01 19:05 ` [PATCH 4/8] arm64: dts: ti: k3-j721e-main: Add output tap delay values Faiz Abbas
2020-10-01 19:05 ` [PATCH 5/8] arm64: dts: ti: k3-j721e-common-proc-board: Add support SD card UHS modes Faiz Abbas
2020-10-01 19:05 ` [PATCH 6/8] arm64: dts: ti: k3-j7200-common-proc-board: " Faiz Abbas
2020-10-01 19:13 ` [PATCH 0/8] Add support for UHS modes in TI's J721e and J7200 boards Nishanth Menon
2020-10-02 4:44 ` Faiz Abbas
2020-10-02 12:49 ` Nishanth Menon
2020-10-02 16:09 ` Faiz Abbas
2020-10-26 14:55 ` Nishanth Menon
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=20201001190541.6364-3-faiz_abbas@ti.com \
--to=faiz_abbas@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
--cc=will@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).