linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: anilkumar@ti.com (AnilKumar Ch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] arm/dts: AM33XX: Configure pinmuxs for D_CAN1 on AM335x-EVM
Date: Wed, 25 Jul 2012 17:53:32 +0530	[thread overview]
Message-ID: <1343219012-19472-3-git-send-email-anilkumar@ti.com> (raw)
In-Reply-To: <1343219012-19472-1-git-send-email-anilkumar@ti.com>

Add D_CAN1 pinctrl node to am3358_pinmux master node to export
D_CAN functionality on AM335x EVM according to pinctrl-single
driver.

Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
---
 arch/arm/boot/dts/am335x-evm.dts |   13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/arch/arm/boot/dts/am335x-evm.dts b/arch/arm/boot/dts/am335x-evm.dts
index e4e1ccb..7f0fd6c 100644
--- a/arch/arm/boot/dts/am335x-evm.dts
+++ b/arch/arm/boot/dts/am335x-evm.dts
@@ -46,3 +46,16 @@
 	regulator-boot-on;
 	regulator-always-on;
 };
+
+&am3358_pinmux {
+
+	pinctrl-names = "default";
+	pinctrl-0 = <&d_can1_pins>;
+
+	d_can1_pins: pinmux_d_can_pins {
+		pinctrl-single,pins = <
+			0x168 0x2	/* uart0_ctsn.d_can1_tx, OUTPUT | MODE2 */
+			0x16C 0x32	/* uart0_rtsn.d_can1_rx, INPUT_PULLUP | MODE2 */
+		>;
+	};
+};
-- 
1.7.9.5

      parent reply	other threads:[~2012-07-25 12:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25 12:23 [PATCH v2 0/2] Add D_CAN device tree data to AM335x-EVM AnilKumar Ch
2012-07-25 12:23 ` [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data AnilKumar Ch
2012-07-25 12:43   ` Sergei Shtylyov
2012-07-26  8:36     ` Daniel Mack
2012-07-26 13:04       ` Sergei Shtylyov
2012-08-03  9:14         ` Vaibhav Hiremath
2012-07-26  8:46   ` Koen Kooi
2012-07-26  9:03     ` AnilKumar, Chimata
2012-07-26  9:14       ` Marc Kleine-Budde
2012-07-26  9:35       ` Koen Kooi
2012-08-03  6:28   ` Vaibhav Hiremath
2012-08-07 11:40     ` AnilKumar, Chimata
2012-07-25 12:23 ` AnilKumar Ch [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=1343219012-19472-3-git-send-email-anilkumar@ti.com \
    --to=anilkumar@ti.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).