From: AnilKumar Ch <anilkumar@ti.com>
To: linux-omap@vger.kernel.org
Cc: tony@atomide.com, b-cousson@ti.com,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
AnilKumar Ch <anilkumar@ti.com>
Subject: [PATCH v2 1/2] arm/dts: Add AM33XX basic pinctrl support
Date: Fri, 20 Jul 2012 13:01:47 +0530 [thread overview]
Message-ID: <1342769508-24810-2-git-send-email-anilkumar@ti.com> (raw)
In-Reply-To: <1342769508-24810-1-git-send-email-anilkumar@ti.com>
Add basic pinctrl support for AM33XX family of devices by adding DT
data to am33xx dtsi file. These patches are based on pinctrl-single
driver and tested on am335x-evm & am335x-bone devices.
Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
---
arch/arm/boot/dts/am33xx.dtsi | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 59509c4..9b974dc 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
+++ b/arch/arm/boot/dts/am33xx.dtsi
@@ -40,6 +40,15 @@
};
};
+ am3358_pinmux: pinmux@44E10800 {
+ compatible = "pinctrl-single";
+ reg = <0x44E10800 0x0338>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ pinctrl-single,register-width = <32>;
+ pinctrl-single,function-mask = <0x7F>;
+ };
+
/*
* XXX: Use a flat representation of the AM33XX interconnect.
* The real AM33XX interconnect network is quite complex.Since
--
1.7.0.4
next prev parent reply other threads:[~2012-07-20 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 7:31 [PATCH v2 0/2] Add pinctrl support to AM33XX family of devices AnilKumar Ch
2012-07-20 7:31 ` AnilKumar Ch [this message]
2012-07-24 8:32 ` [PATCH v2 1/2] arm/dts: Add AM33XX basic pinctrl support Tony Lindgren
2012-07-24 9:10 ` AnilKumar, Chimata
2012-07-20 7:31 ` [PATCH v2 2/2] arm/dts: Configure pinmuxs for user leds control on Bone AnilKumar Ch
2012-07-24 8:30 ` Tony Lindgren
[not found] ` <20120724083007.GU6522-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2012-07-24 9:11 ` AnilKumar, Chimata
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=1342769508-24810-2-git-send-email-anilkumar@ti.com \
--to=anilkumar@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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).