From: sshtylyov@mvista.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/2] Defines DA850/AM18xx/OMAPL1-38 SOC resources used by PRUSS UIO driver
Date: Mon, 28 Feb 2011 13:27:34 +0300 [thread overview]
Message-ID: <4D6B7896.6000703@mvista.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593024BF3591A@dbde02.ent.ti.com>
Hello.
On 28-02-2011 7:46, TK, Pratheesh Gangadhar wrote:
>>> This patch defines PRUSS, ECAP clocks, memory and IRQ resources
>>> used by PRUSS UIO driver in DA850/AM18xx/OMAPL1-38 devices. UIO
>> It's OMAP-L138.
> Ok.
>>> 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.
>>> Signed-off-by: Pratheesh Gangadhar<pratheesh@ti.com>
[...]
>>> 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,
>>> + },
>>> + [2] = {
>>> + .start = 0,
>>> + .end = SZ_256K - 1,
>> Huh? I don't see where it's filled...
> The current use is only to indicate memory block size to the PRUSS UIO driver when we allocate DDR memory using dma_alloc_coherent.
Why not pass this size via the platform data? There shouldn't be "dummy"
resources.
> sram_alloc is changed to use L3_RAM (128KB) instead of ARM RAM (8KB) in Mistral patch set - I need to follow the same convention
> for L3 RAM as well if I need to align with that patch. Is there a better
way to do this?
Didn't understand about L3 RAM.
Also, please wrap your text at 80 columns.
WBR, Sergei
next prev parent reply other threads:[~2011-02-28 10:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 14:06 [PATCH v4 0/2] Add PRUSS UIO driver support Pratheesh Gangadhar
2011-02-24 14:06 ` [PATCH v4 1/2] " Pratheesh Gangadhar
2011-02-24 14:06 ` [PATCH v4 2/2] Defines DA850/AM18xx/OMAPL1-38 SOC resources used by PRUSS UIO driver Pratheesh Gangadhar
2011-02-25 11:47 ` Sergei Shtylyov
2011-02-25 13:02 ` Hans J. Koch
2011-02-25 13:22 ` Sergei Shtylyov
2011-02-28 4:46 ` TK, Pratheesh Gangadhar
2011-02-28 10:08 ` Nori, Sekhar
2011-02-28 10:27 ` Sergei Shtylyov [this message]
2011-02-24 14:28 ` [PATCH v4 1/2] PRUSS UIO driver support Thomas Gleixner
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=4D6B7896.6000703@mvista.com \
--to=sshtylyov@mvista.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