From: Yendapally Reddy Dhananjaya Reddy <yendapally.reddy@broadcom.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Pramod Kumar <pramodku@broadcom.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
Yendapally Reddy Dhananjaya Reddy
<yendapally.reddy@broadcom.com>
Subject: [PATCH 3/3] ARM: dts: enable pinctrl for Broadcom NS2 SoC
Date: Thu, 3 Mar 2016 06:41:43 -0500 [thread overview]
Message-ID: <1457005303-26829-4-git-send-email-yendapally.reddy@broadcom.com> (raw)
In-Reply-To: <1457005303-26829-1-git-send-email-yendapally.reddy@broadcom.com>
This enables the pinctrl support for Broadcom NS2 SoC
Signed-off-by: Yendapally Reddy Dhananjaya Reddy <yendapally.reddy@broadcom.com>
---
arch/arm64/boot/dts/broadcom/ns2-svk.dts | 9 +++++++++
arch/arm64/boot/dts/broadcom/ns2.dtsi | 7 +++++++
2 files changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/broadcom/ns2-svk.dts b/arch/arm64/boot/dts/broadcom/ns2-svk.dts
index 6bb3d4d..d1c8ccc 100644
--- a/arch/arm64/boot/dts/broadcom/ns2-svk.dts
+++ b/arch/arm64/boot/dts/broadcom/ns2-svk.dts
@@ -75,3 +75,12 @@
#size-cells = <1>;
};
};
+
+&pinctrl {
+ pinctrl-names = "default";
+ pinctrl-0 = <&nand_sel>;
+ nand_sel: nand_sel {
+ function = "nand";
+ groups = "nand_grp";
+ };
+};
diff --git a/arch/arm64/boot/dts/broadcom/ns2.dtsi b/arch/arm64/boot/dts/broadcom/ns2.dtsi
index a510d3a..a3b267c 100644
--- a/arch/arm64/boot/dts/broadcom/ns2.dtsi
+++ b/arch/arm64/boot/dts/broadcom/ns2.dtsi
@@ -234,6 +234,13 @@
"chimp", "port", "sdio";
};
+ pinctrl: pinctrl@6501d130 {
+ compatible = "brcm,ns2-pinmux";
+ reg = <0x6501d130 0x08>,
+ <0x660a0028 0x04>,
+ <0x660009b0 0x40>;
+ };
+
crmu: crmu@65024000 {
compatible = "syscon";
reg = <0x65024000 0x100>;
--
2.1.0
prev parent reply other threads:[~2016-03-03 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 11:41 [PATCH 0/3] pinmux support " Yendapally Reddy Dhananjaya Reddy
2016-03-03 11:41 ` [PATCH 1/3] pinctrl: Broadcom Northstar2 pinctrl device tree bindings Yendapally Reddy Dhananjaya Reddy
2016-03-05 4:29 ` Rob Herring
2016-03-09 10:58 ` Linus Walleij
2016-03-03 11:41 ` [PATCH 2/3] pinctrl: ns2: add pinmux driver support for Broadcom NS2 SoC Yendapally Reddy Dhananjaya Reddy
2016-03-09 11:04 ` Linus Walleij
2016-03-09 17:50 ` Stephen Warren
2016-03-09 21:07 ` Ray Jui
2016-03-03 11:41 ` Yendapally Reddy Dhananjaya Reddy [this message]
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=1457005303-26829-4-git-send-email-yendapally.reddy@broadcom.com \
--to=yendapally.reddy@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--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=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=pramodku@broadcom.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.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
all inboxes | Powered by JetHome®