From: Roger Quadros <rogerq@ti.com>
To: tony@atomide.com
Cc: wg@grandegger.com, mkl@pengutronix.de, wsa@the-dreams.de,
mugunthanvnm@ti.com, george.cherian@ti.com, balbi@ti.com,
nsekhar@ti.comnm@ti.com, sergei.shtylyov@cogentembedded.com,
linux-omap@vger.kernel.org, linux-can@vger.kernel.org,
devicetree@vger.kernel.org, Roger Quadros <rogerq@ti.com>
Subject: [PATCH v3 07/10] arm: dts: am437x-gp: Add dcan support
Date: Tue, 4 Nov 2014 12:48:51 +0200 [thread overview]
Message-ID: <1415098134-26405-8-git-send-email-rogerq@ti.com> (raw)
In-Reply-To: <1415098134-26405-1-git-send-email-rogerq@ti.com>
From: Mugunthan V N <mugunthanvnm@ti.com>
Add DCAN support for AM437x GP EVM with both DCAN instances.
[Roger Q] Updated output pin to not use pull up.
Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com>
Signed-off-by: George Cherian <george.cherian@ti.com>
Signed-off-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Roger Quadros <rogerq@ti.com>
---
arch/arm/boot/dts/am437x-gp-evm.dts | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/arch/arm/boot/dts/am437x-gp-evm.dts b/arch/arm/boot/dts/am437x-gp-evm.dts
index e7ac47f..58594fd 100644
--- a/arch/arm/boot/dts/am437x-gp-evm.dts
+++ b/arch/arm/boot/dts/am437x-gp-evm.dts
@@ -254,6 +254,20 @@
0x238 (PIN_OUTPUT_PULLUP | MUX_MODE7)
>;
};
+
+ dcan0_default: dcan0_default_pins {
+ pinctrl-single,pins = <
+ 0x178 (PIN_OUTPUT | MUX_MODE2) /* uart1_ctsn.d_can0_tx */
+ 0x17c (PIN_INPUT_PULLUP | MUX_MODE2) /* uart1_rtsn.d_can0_rx */
+ >;
+ };
+
+ dcan1_default: dcan1_default_pins {
+ pinctrl-single,pins = <
+ 0x180 (PIN_OUTPUT | MUX_MODE2) /* uart1_rxd.d_can1_tx */
+ 0x184 (PIN_INPUT_PULLUP | MUX_MODE2) /* uart1_txd.d_can1_rx */
+ >;
+ };
};
&i2c0 {
@@ -511,3 +525,15 @@
};
};
};
+
+&dcan0 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&dcan0_default>;
+ status = "okay";
+};
+
+&dcan1 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&dcan1_default>;
+ status = "okay";
+};
--
1.8.3.2
next prev parent reply other threads:[~2014-11-04 10:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 10:48 [PATCH v3 00/10] ARM: dts: TI: Add CAN support Roger Quadros
2014-11-04 10:48 ` [PATCH v3 01/10] ARM: dts: dra7: Add syscon regmap for CORE CONTROL area Roger Quadros
2014-11-04 10:48 ` [PATCH v3 02/10] ARM: dts: DRA7: Add DCAN nodes Roger Quadros
2014-11-04 10:48 ` [PATCH v3 03/10] ARM: dts: dra7-evm: Add CAN support Roger Quadros
2014-11-04 10:48 ` [PATCH v3 04/10] ARM: dts: dra72-evm: " Roger Quadros
2014-11-04 10:48 ` [PATCH v3 05/10] ARM: dts: am4372: Add control module syscon node Roger Quadros
2014-11-04 10:48 ` [PATCH v3 06/10] ARM: dts: am4372: Add DCAN nodes Roger Quadros
2014-11-04 10:48 ` Roger Quadros [this message]
2014-11-04 10:48 ` [PATCH v3 08/10] ARM: dts: am33xx: Add control module syscon node Roger Quadros
2014-11-04 10:48 ` [PATCH v3 09/10] ARM: dts: am33xx: Update DCAN nodes Roger Quadros
2014-11-04 10:48 ` [PATCH v3 10/10] ARM: dts: am335x-evm: Add DCAN1 details Roger Quadros
2014-11-04 15:55 ` [PATCH v3 00/10] ARM: dts: TI: Add CAN support Tony Lindgren
2014-11-05 11:06 ` Roger Quadros
2014-11-05 18:49 ` Tony Lindgren
2014-11-07 12:44 ` Roger Quadros
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=1415098134-26405-8-git-send-email-rogerq@ti.com \
--to=rogerq@ti.com \
--cc=balbi@ti.com \
--cc=george.cherian@ti.com \
--cc=mkl@pengutronix.de \
--cc=mugunthanvnm@ti.com \
--cc=nsekhar@ti.comnm \
--cc=tony@atomide.com \
--cc=wg@grandegger.com \
--cc=wsa@the-dreams.de \
/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).