linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: subhasish@mistralsolutions.com (Subhasish Ghosh)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 8/9] da850: pruss CAN board specific changes for gpios.
Date: Tue,  1 Feb 2011 20:17:46 +0530	[thread overview]
Message-ID: <1296571667-12049-9-git-send-email-subhasish@mistralsolutions.com> (raw)
In-Reply-To: <1296571667-12049-1-git-send-email-subhasish@mistralsolutions.com>

This patch adds the GPIO modifications required for the pruss CAN.

Signed-off-by: Subhasish Ghosh <subhasish@mistralsolutions.com>
---
 arch/arm/mach-davinci/board-da850-evm.c |   11 ++++++++++-
 1 files changed, 10 insertions(+), 1 deletions(-)

diff --git a/arch/arm/mach-davinci/board-da850-evm.c b/arch/arm/mach-davinci/board-da850-evm.c
index 285545f..737df73 100644
--- a/arch/arm/mach-davinci/board-da850-evm.c
+++ b/arch/arm/mach-davinci/board-da850-evm.c
@@ -45,6 +45,7 @@
 
 #define DA850_MMCSD_CD_PIN		GPIO_TO_PIN(4, 0)
 #define DA850_MMCSD_WP_PIN		GPIO_TO_PIN(4, 1)
+#define DA850_PRUSS_CAN_TRX_PIN	GPIO_TO_PIN(2, 0)
 
 #define DA850_MII_MDIO_CLKEN_PIN	GPIO_TO_PIN(2, 6)
 
@@ -1055,7 +1056,7 @@ static __init int da850_evm_init_cpufreq(void) { return 0; }
 
 const short da850_pruss_can_pins[] = {
 	DA850_PRUSS_PRU0_R31_0, DA850_PRUSS_PRU1_R30_15,
-	DA850_PRUSS_PRU1_R31_18,
+	DA850_PRUSS_PRU1_R31_18, DA850_GPIO2_0,
 	-1
 };
 
@@ -1076,6 +1077,14 @@ static int __init da850_evm_setup_pruss_can(void)
 	val |= BIT(3);
 	__raw_writel(val, cfg_chip3_base);
 
+	/* value = 0 to enable the CAN transceiver */
+	ret = gpio_request_one(DA850_PRUSS_CAN_TRX_PIN,
+					GPIOF_OUT_INIT_LOW, "pruss_can_en");
+	if (ret) {
+		pr_warning("Cannot setup GPIO %d\n", DA850_PRUSS_CAN_TRX_PIN);
+		gpio_free(DA850_PRUSS_CAN_TRX_PIN);
+	}
+
 	return ret;
 }
 
-- 
1.7.2.3

  parent reply	other threads:[~2011-02-01 14:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 14:47 [PATCH v1 0/9] pruss mfd drivers Subhasish Ghosh
2011-02-01 14:47 ` [PATCH v1 1/9] mfd: pruss mfd driver Subhasish Ghosh
2011-02-01 14:47 ` [PATCH v1 2/9] da850: pruss board specific additions Subhasish Ghosh
2011-02-02 11:49   ` Sergei Shtylyov
2011-02-01 14:47 ` [PATCH v1 3/9] da850: pruss platform " Subhasish Ghosh
2011-02-02 11:55   ` Sergei Shtylyov
2011-02-01 14:47 ` [PATCH v1 4/9] can: pruss CAN driver Subhasish Ghosh
2011-02-03 16:14   ` Detlev Zundel
2011-02-01 14:47 ` [PATCH v1 5/9] da850: pruss CAN board specific additions Subhasish Ghosh
2011-02-02 12:01   ` Sergei Shtylyov
2011-02-01 14:47 ` [PATCH v1 6/9] da850: pruss CAN platform " Subhasish Ghosh
2011-02-02 12:03   ` Sergei Shtylyov
2011-02-01 14:47 ` [PATCH v1 7/9] mfd: pruss CAN private data Subhasish Ghosh
2011-02-02 12:05   ` Sergei Shtylyov
2011-02-01 14:47 ` Subhasish Ghosh [this message]
2011-02-02 12:07   ` [PATCH v1 8/9] da850: pruss CAN board specific changes for gpios Sergei Shtylyov
2011-02-01 14:47 ` [PATCH v1 9/9] da850: pruss CAN platform " Subhasish Ghosh
2011-02-02 12:08   ` Sergei Shtylyov
2011-02-02 16:13 ` [PATCH v1 0/9] pruss mfd drivers Nori, Sekhar
2011-02-02 16:20   ` Mark Brown
2011-02-02 16:36     ` Nori, Sekhar

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=1296571667-12049-9-git-send-email-subhasish@mistralsolutions.com \
    --to=subhasish@mistralsolutions.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).