From: subhasish@mistralsolutions.com (Subhasish Ghosh)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 5/9] da850: pruss CAN board specific additions.
Date: Tue, 1 Feb 2011 20:17:43 +0530 [thread overview]
Message-ID: <1296571667-12049-6-git-send-email-subhasish@mistralsolutions.com> (raw)
In-Reply-To: <1296571667-12049-1-git-send-email-subhasish@mistralsolutions.com>
This patch adds the pruss CAN pin mux and registers the device
with the pruss mfd driver.
Signed-off-by: Subhasish Ghosh <subhasish@mistralsolutions.com>
---
arch/arm/mach-davinci/board-da850-evm.c | 40 ++++++++++++++++++++++++++++++-
1 files changed, 39 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-davinci/board-da850-evm.c b/arch/arm/mach-davinci/board-da850-evm.c
index 7938c6d..285545f 100644
--- a/arch/arm/mach-davinci/board-da850-evm.c
+++ b/arch/arm/mach-davinci/board-da850-evm.c
@@ -1053,8 +1053,46 @@ static __init int da850_evm_init_cpufreq(void)
static __init int da850_evm_init_cpufreq(void) { return 0; }
#endif
+const short da850_pruss_can_pins[] = {
+ DA850_PRUSS_PRU0_R31_0, DA850_PRUSS_PRU1_R30_15,
+ DA850_PRUSS_PRU1_R31_18,
+ -1
+};
+
+static int __init da850_evm_setup_pruss_can(void)
+{
+ int ret, val = 0;
+ void __iomem *cfg_chip3_base;
+
+ if (!machine_is_davinci_da850_evm())
+ return 0;
+
+ ret = davinci_cfg_reg_list(da850_pruss_can_pins);
+ if (ret)
+ pr_warning("%s: da850_pruss_can_pins mux setup "
+ "failed:%d\n", __func__, ret);
+ cfg_chip3_base = DA8XX_SYSCFG0_VIRT(DA8XX_CFGCHIP3_REG);
+ val = __raw_readl(cfg_chip3_base);
+ val |= BIT(3);
+ __raw_writel(val, cfg_chip3_base);
+
+ return ret;
+}
+
+static struct da8xx_pruss_can_data can_data = {
+ .version = 1,
+};
+
static struct da8xx_pruss_devices pruss_devices[] = {
- {.dev_name = NULL,},
+ {
+ .dev_name = "da8xx_pruss_can",
+ .pdata = &can_data,
+ .pdata_size = sizeof(can_data),
+ .setup = da850_evm_setup_pruss_can,
+ },
+ {
+ .dev_name = NULL,
+ },
};
static int __init da8xx_evm_setup_pruss(void)
--
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 ` Subhasish Ghosh [this message]
2011-02-02 12:01 ` [PATCH v1 5/9] da850: pruss CAN board specific additions 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 ` [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-6-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).