From: Zhiyong Tao <zhiyong.tao@mediatek.com>
To: robh+dt@kernel.org, linus.walleij@linaro.org,
mark.rutland@arm.com, matthias.bgg@gmail.com
Cc: srv_heupstream@mediatek.com, liguo.zhang@mediatek.com,
yingjoe.chen@mediatek.com, hongkun.cao@mediatek.com,
biao.huang@mediatek.com, yt.shen@mediatek.com,
hongzhou.yang@mediatek.com, erin.lo@mediatek.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-gpio@vger.kernel.org,
Zhiyong Tao <zhiyong.tao@mediatek.com>
Subject: [PATCH v3 2/4] arm64: dts: mt2712: add pintcrl device node.
Date: Mon, 5 Mar 2018 19:35:43 +0800 [thread overview]
Message-ID: <1520249745-6757-3-git-send-email-zhiyong.tao@mediatek.com> (raw)
In-Reply-To: <1520249745-6757-1-git-send-email-zhiyong.tao@mediatek.com>
This patch adds pintcrl device node for mt2712.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
---
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
index d7688bc..fb3b051 100644
--- a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
+++ b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
@@ -9,6 +9,7 @@
#include <dt-bindings/interrupt-controller/irq.h>
#include <dt-bindings/interrupt-controller/arm-gic.h>
#include <dt-bindings/power/mt2712-power.h>
+#include "mt2712-pinfunc.h"
/ {
compatible = "mediatek,mt2712";
@@ -258,6 +259,23 @@
#clock-cells = <1>;
};
+ syscfg_pctl_a: syscfg_pctl_a@10005000 {
+ compatible = "mediatek,mt2712-pctl-a-syscfg", "syscon";
+ reg = <0 0x10005000 0 0x1000>;
+ };
+
+ pio: pinctrl@10005000 {
+ compatible = "mediatek,mt2712-pinctrl";
+ reg = <0 0x1000b000 0 0x1000>;
+ mediatek,pctl-regmap = <&syscfg_pctl_a>;
+ pins-are-numbered;
+ gpio-controller;
+ #gpio-cells = <2>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ interrupts = <GIC_SPI 153 IRQ_TYPE_LEVEL_HIGH>;
+ };
+
scpsys: scpsys@10006000 {
compatible = "mediatek,mt2712-scpsys", "syscon";
#power-domain-cells = <1>;
--
1.9.1
next prev parent reply other threads:[~2018-03-05 11:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 11:35 [PATCH v3 0/4] PINCTRL: Mediatek pinctrl driver for mt2712 Zhiyong Tao
2018-03-05 11:35 ` [PATCH v3 1/4] arm64: dts: mt2712: add pintcrl file Zhiyong Tao
2018-03-07 22:28 ` Rob Herring
2018-03-05 11:35 ` Zhiyong Tao [this message]
2018-03-05 11:35 ` [PATCH v3 3/4] pinctrl: add mt2712 pinctrl driver Zhiyong Tao
2018-03-05 11:35 ` [PATCH v3 4/4] pintcrl: support bias-disable of generic and special pins simultaneously Zhiyong Tao
[not found] ` <1520249745-6757-1-git-send-email-zhiyong.tao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-03-08 3:08 ` [PATCH v3 0/4] PINCTRL: Mediatek pinctrl driver for mt2712 Sean Wang
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=1520249745-6757-3-git-send-email-zhiyong.tao@mediatek.com \
--to=zhiyong.tao@mediatek.com \
--cc=biao.huang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=erin.lo@mediatek.com \
--cc=hongkun.cao@mediatek.com \
--cc=hongzhou.yang@mediatek.com \
--cc=liguo.zhang@mediatek.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-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=yingjoe.chen@mediatek.com \
--cc=yt.shen@mediatek.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).