From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Pratheesh Gangadhar <pratheesh@ti.com>
Cc: davinci-linux-open-source@linux.davincidsp.com, gregkh@suse.de,
amit.chatterjee@ti.com, hjk@linutronix.de,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] Defines DA850/AM18xx/OMAPL1-38 SOC resources used by PRUSS UIO driver
Date: Mon, 21 Feb 2011 20:10:26 +0300 [thread overview]
Message-ID: <4D629C82.3080906@mvista.com> (raw)
In-Reply-To: <1298041530-26855-3-git-send-email-pratheesh@ti.com>
Hello.
Pratheesh Gangadhar wrote:
> Signed-off-by: Pratheesh Gangadhar <pratheesh@ti.com>
Signoff should follow the change log, not precede it. "From:" line may
precede the change log.
> This patch defines PRUSS, ECAP clocks, memory and IRQ resources
> used by PRUSS UIO driver in DA850/AM18xx/OMAPL1-38 devices. UIO
> driver exports 64K I/O region of PRUSS, 128KB L3 RAM and 256KB
> DDR buffer to user space. PRUSS has 8 host event interrupt lines
> mapped to IRQ_DA8XX_EVTOUT0..7 of ARM9 INTC.These in conjunction
> with shared memory can be used to implement IPC between ARM9 and
> PRUSS.
> diff --git a/arch/arm/mach-davinci/board-da850-evm.c b/arch/arm/mach-davinci/board-da850-evm.c
> index 11f986b..ddcbac8 100644
> --- a/arch/arm/mach-davinci/board-da850-evm.c
> +++ b/arch/arm/mach-davinci/board-da850-evm.c
> @@ -1077,6 +1077,10 @@ static __init void da850_evm_init(void)
> pr_warning("da850_evm_init: i2c0 registration failed: %d\n",
> ret);
>
> + ret = da8xx_register_pruss();
> + if (ret)
> + pr_warning("da850_evm_init: pruss registration failed: %d\n",
> + ret);
>
> ret = da8xx_register_watchdog();
> if (ret)
I'd put this into a pacth of its own, to have the SoC level changes
separated from board-level changes...
> diff --git a/arch/arm/mach-davinci/da850.c b/arch/arm/mach-davinci/da850.c
> index 3443d97..0096d4f 100644
> --- a/arch/arm/mach-davinci/da850.c
> +++ b/arch/arm/mach-davinci/da850.c
> @@ -238,6 +238,13 @@ static struct clk tptc2_clk = {
> .flags = ALWAYS_ENABLED,
> };
>
> +static struct clk pruss_clk = {
> + .name = "pruss",
> + .parent = &pll0_sysclk2,
> + .lpsc = DA8XX_LPSC0_DMAX,
We have patch submitted by TI that renames this #define to DA8XX_LPSC0_PRUSS...
> + .flags = ALWAYS_ENABLED,
> +};
> +
We already have patch submitted by TI that defines this clock. It would be
nice if you coordinated your efforts to avoid such conflicts.
Again, I'd put the part adding the clocks into a patch of its own.
> diff --git a/arch/arm/mach-davinci/devices-da8xx.c b/arch/arm/mach-davinci/devices-da8xx.c
> index beda8a4..4ea3d1f 100644
> --- a/arch/arm/mach-davinci/devices-da8xx.c
> +++ b/arch/arm/mach-davinci/devices-da8xx.c
> @@ -725,3 +725,76 @@ int __init da8xx_register_cpuidle(void)
>
> return platform_device_register(&da8xx_cpuidle_device);
> }
> +static struct resource pruss_resources[] = {
> + [0] = {
> + .start = DA8XX_PRUSS_BASE,
> + .end = DA8XX_PRUSS_BASE + SZ_64K - 1,
> + .flags = IORESOURCE_MEM,
> + },
> + [1] = {
> + .start = DA8XX_L3RAM_BASE,
> + .end = DA8XX_L3RAM_BASE + SZ_128K - 1,
> + .flags = IORESOURCE_MEM,
Are you going to use all SRAM?
> + },
> + [2] = {
> + .start = 0,
> + .end = SZ_256K - 1,
> + .flags = IORESOURCE_MEM,
> + },
> +
> + [3] = {
> + .start = IRQ_DA8XX_EVTOUT0,
> + .end = IRQ_DA8XX_EVTOUT0,
> + .flags = IORESOURCE_IRQ,
> + },
> + [4] = {
> + .start = IRQ_DA8XX_EVTOUT1,
> + .end = IRQ_DA8XX_EVTOUT1,
> + .flags = IORESOURCE_IRQ,
> + },
> + [5] = {
> + .start = IRQ_DA8XX_EVTOUT2,
> + .end = IRQ_DA8XX_EVTOUT2,
> + .flags = IORESOURCE_IRQ,
> + },
> + [6] = {
> + .start = IRQ_DA8XX_EVTOUT3,
> + .end = IRQ_DA8XX_EVTOUT3,
> + .flags = IORESOURCE_IRQ,
> + },
> + [7] = {
> + .start = IRQ_DA8XX_EVTOUT4,
> + .end = IRQ_DA8XX_EVTOUT4,
> + .flags = IORESOURCE_IRQ,
> + },
> + [8] = {
> + .start = IRQ_DA8XX_EVTOUT5,
> + .end = IRQ_DA8XX_EVTOUT5,
> + .flags = IORESOURCE_IRQ,
> + },
> + [9] = {
> + .start = IRQ_DA8XX_EVTOUT6,
> + .end = IRQ_DA8XX_EVTOUT6,
> + .flags = IORESOURCE_IRQ,
> + },
> + [10] = {
> + .start = IRQ_DA8XX_EVTOUT7,
> + .end = IRQ_DA8XX_EVTOUT7,
> + .flags = IORESOURCE_IRQ,
> + },
> +};
> +
> +static struct platform_device pruss_device = {
> + .name = "pruss",
> + .id = 0,
> + .num_resources = ARRAY_SIZE(pruss_resources),
> + .resource = pruss_resources,
> + .dev = {
> + .coherent_dma_mask = 0xffffffff,
> + }
> +};
> +
> +int __init da8xx_register_pruss()
> +{
> + return platform_device_register(&pruss_device);
> +}
Again, there's TI patch that adds this device already...
WBR, Sergei
next prev parent reply other threads:[~2011-02-21 17:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 15:05 [PATCH 0/2] Add PRUSS UIO driver support Pratheesh Gangadhar
2011-02-18 15:05 ` [PATCH 1/2] " Pratheesh Gangadhar
2011-02-18 15:05 ` [PATCH 2/2] Defines DA850/AM18xx/OMAPL1-38 SOC resources used by PRUSS UIO driver Pratheesh Gangadhar
2011-02-21 17:10 ` Sergei Shtylyov [this message]
2011-02-22 11:38 ` TK, Pratheesh Gangadhar
2011-02-18 15:44 ` [PATCH 1/2] PRUSS UIO driver support Arnd Bergmann
2011-02-18 16:15 ` Thomas Gleixner
2011-02-18 16:31 ` Arnd Bergmann
2011-02-18 17:03 ` Thomas Gleixner
2011-02-19 15:40 ` TK, Pratheesh Gangadhar
2011-02-19 18:34 ` Hans J. Koch
2011-02-21 3:57 ` TK, Pratheesh Gangadhar
2011-02-21 19:33 ` Hans J. Koch
2011-02-21 19:37 ` Thomas Gleixner
2011-02-21 19:53 ` Sergei Shtylyov
2011-02-22 12:06 ` TK, Pratheesh Gangadhar
2011-02-19 10:19 ` TK, Pratheesh Gangadhar
2011-02-18 16:31 ` Hans J. Koch
2011-02-18 17:05 ` Greg KH
2011-02-19 16:06 ` TK, Pratheesh Gangadhar
2011-02-19 11:30 ` TK, Pratheesh Gangadhar
2011-02-18 16:51 ` Thomas Gleixner
2011-02-19 12:47 ` TK, Pratheesh Gangadhar
2011-02-19 13:26 ` Russell King - ARM Linux
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=4D629C82.3080906@mvista.com \
--to=sshtylyov@mvista.com \
--cc=amit.chatterjee@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=gregkh@suse.de \
--cc=hjk@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pratheesh@ti.com \
/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