From: andrej.skvortzov@gmail.com (Andrey Skvortsov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: dts: add core2 padconf region for am3517
Date: Mon, 11 May 2015 18:02:13 +0300 [thread overview]
Message-ID: <1431356533-7737-1-git-send-email-andrej.skvortzov@gmail.com> (raw)
In-Reply-To: <554FF488.5090805@ti.com>
According to the technical reference manual for AM35xx system
controller module (SCM) PADCONFS core registers are divided in two
regions: 0x48002030..0x48002268 and 0x480025D8..0x480025FC.
First region is the same for all omap3 SoC and is described in
omap3.dtsi.
The second region is the same as in omap34xx and omap35xx.
The patch adds missing description for the second region.
This patch was tested on AM3517.
Signed-off-by: Andrey Skvortsov <andrej.skvortzov@gmail.com>
---
v2:
move omap3_pmx_core2 under l4_core -> scm
arch/arm/boot/dts/am3517.dtsi | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/am3517.dtsi b/arch/arm/boot/dts/am3517.dtsi
index f164dce..99b322e 100644
--- a/arch/arm/boot/dts/am3517.dtsi
+++ b/arch/arm/boot/dts/am3517.dtsi
@@ -63,6 +63,20 @@
};
};
+&scm {
+ omap3_pmx_core2: pinmux at 05D8 {
+ compatible = "ti,omap3-padconf",
+ "pinctrl-single";
+ reg = <0x05D8 0x24>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ #interrupt-cells = <1>;
+ interrupt-controller;
+ pinctrl-single,register-width = <16>;
+ pinctrl-single,function-mask = <0xff1f>;
+ };
+};
+
&iva {
status = "disabled";
};
--
2.1.4
next prev parent reply other threads:[~2015-05-11 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 21:27 [PATCH] ARM: dts: add core2 padconf region for am3517 Andrey Skvortsov
2015-05-11 0:15 ` Nishanth Menon
2015-05-11 15:02 ` Andrey Skvortsov [this message]
2015-05-20 17:11 ` Tony Lindgren
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=1431356533-7737-1-git-send-email-andrej.skvortzov@gmail.com \
--to=andrej.skvortzov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).