From: subhasish@mistralsolutions.com (Subhasish Ghosh)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 6/9] da850: pruss CAN platform specific additions.
Date: Tue, 1 Feb 2011 20:17:44 +0530 [thread overview]
Message-ID: <1296571667-12049-7-git-send-email-subhasish@mistralsolutions.com> (raw)
In-Reply-To: <1296571667-12049-1-git-send-email-subhasish@mistralsolutions.com>
This patch adds the necessary pins for the pruss CAN.
Signed-off-by: Subhasish Ghosh <subhasish@mistralsolutions.com>
---
arch/arm/mach-davinci/da850.c | 4 ++++
arch/arm/mach-davinci/include/mach/mux.h | 4 ++++
2 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-davinci/da850.c b/arch/arm/mach-davinci/da850.c
index 341d836..11ce7ba 100644
--- a/arch/arm/mach-davinci/da850.c
+++ b/arch/arm/mach-davinci/da850.c
@@ -565,6 +565,10 @@ static const struct mux_config da850_pins[] = {
MUX_CFG(DA850, EMA_CLK, 6, 0, 15, 1, false)
MUX_CFG(DA850, EMA_WAIT_1, 6, 24, 15, 1, false)
MUX_CFG(DA850, NEMA_CS_2, 7, 0, 15, 1, false)
+ /* PRU functions for soft CAN */
+ MUX_CFG(DA850, PRUSS_PRU0_R31_0, 7, 28, 15, 0, false)
+ MUX_CFG(DA850, PRUSS_PRU1_R30_15, 12, 0, 15, 4, false)
+ MUX_CFG(DA850, PRUSS_PRU1_R31_18, 11, 20, 15, 0, false)
/* GPIO function */
MUX_CFG(DA850, GPIO2_4, 6, 12, 15, 8, false)
MUX_CFG(DA850, GPIO2_6, 6, 4, 15, 8, false)
diff --git a/arch/arm/mach-davinci/include/mach/mux.h b/arch/arm/mach-davinci/include/mach/mux.h
index 5d4e0fe..10f49f2 100644
--- a/arch/arm/mach-davinci/include/mach/mux.h
+++ b/arch/arm/mach-davinci/include/mach/mux.h
@@ -906,6 +906,10 @@ enum davinci_da850_index {
DA850_EMA_CLK,
DA850_EMA_WAIT_1,
DA850_NEMA_CS_2,
+ /* PRU I/O */
+ DA850_PRUSS_PRU0_R31_0,
+ DA850_PRUSS_PRU1_R30_15,
+ DA850_PRUSS_PRU1_R31_18,
/* GPIO function */
DA850_GPIO2_4,
--
1.7.2.3
next prev 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 ` Subhasish Ghosh [this message]
2011-02-02 12:03 ` [PATCH v1 6/9] da850: pruss CAN platform " 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 ` [PATCH v1 8/9] da850: pruss CAN board specific changes for gpios Subhasish Ghosh
2011-02-02 12:07 ` 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-7-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).