On Fri, Jan 7, 2011 at 6:37 PM, S.Ghosh ghosh.subhas...@gmail.com wrote:
On Fri, Jan 7, 2011 at 6:19 PM, Nori, Sekhar nsek...@ti.com wrote:
On Fri, Jan 07, 2011 at 17:14:36, S.Ghosh wrote:
[SG] -- There are other modules as well which use this API (atleast
audio)
Changing
Hi Sekhar,
I observed that sram_alloc is allocating memory from the Arm Internal Memory
(0x ) and
not the Shared Memory (0x8000 ). In that case, we cannot use sram_alloc.
On Wed, Jan 5, 2011 at 2:48 PM, S.Ghosh ghosh.subhas...@gmail.com wrote:
On Wed, Dec 15, 2010 at 5:41 PM,
Hi S.Ghosh,
On Fri, Jan 07, 2011 at 16:09:32, S.Ghosh wrote:
Hi Sekhar,
I observed that sram_alloc is allocating memory from the Arm Internal
Memory (0x ) and
not the Shared Memory (0x8000 ). In that case, we cannot use
sram_alloc.
I don't think sram_alloc() can allocate
On Fri, Jan 7, 2011 at 4:25 PM, Nori, Sekhar nsek...@ti.com wrote:
Hi S.Ghosh,
On Fri, Jan 07, 2011 at 16:09:32, S.Ghosh wrote:
Hi Sekhar,
I observed that sram_alloc is allocating memory from the Arm Internal
Memory (0x ) and
not the Shared Memory (0x8000 ). In that case,
On Fri, Jan 7, 2011 at 6:19 PM, Nori, Sekhar nsek...@ti.com wrote:
On Fri, Jan 07, 2011 at 17:14:36, S.Ghosh wrote:
[SG] -- There are other modules as well which use this API (atleast
audio)
Changing the sram_alloc API to allocate from the shared
memory may
On Thu, Jan 6, 2011 at 3:06 AM, Kevin Hilman khil...@ti.com wrote:
Nori, Sekhar nsek...@ti.com writes:
[...]
[SG] -- This McASP clock is bound with the McASP driver by the device
ID. This device ID (davinci-mcasp.0) is not
available to the SUART driver.
You can also look up the
On Wed, Jan 5, 2011 at 6:01 PM, Nori, Sekhar nsek...@ti.com wrote:
Hi Subhasish,
On Wed, Jan 05, 2011 at 14:48:00, S.Ghosh wrote:
+static struct clk mcasp_pru_clk = {
+ .name = mcasp_pru,
+ .parent = pll0_sysclk2,
+
On Wed, Dec 15, 2010 at 5:41 PM, Nori, Sekhar nsek...@ti.com wrote:
On Fri, Dec 03, 2010 at 20:41:47, Subhasish Ghosh wrote:
The patch adds support for emulated UART controllers
on the programmable realtime unit (PRU) available on OMAPL138.
This defines the system resource requirements
On Wed, Dec 15, 2010 at 7:53 PM, Nori, Sekhar nsek...@ti.com wrote:
On Wed, Dec 15, 2010 at 18:31:43, Sergei Shtylyov wrote:
Hello.
On 03-12-2010 18:11, Subhasish Ghosh wrote:
The patch adds support for emulated UART controllers
on the programmable realtime unit (PRU) available on
On Wed, Dec 15, 2010 at 6:31 PM, Sergei Shtylyov sshtyl...@mvista.comwrote:
Hello.
On 03-12-2010 18:11, Subhasish Ghosh wrote:
The patch adds support for emulated UART controllers
on the programmable realtime unit (PRU) available on OMAPL138.
This defines the system resource requirements
Nori, Sekhar nsek...@ti.com writes:
[...]
[SG] -- This McASP clock is bound with the McASP driver by the device
ID. This device ID (davinci-mcasp.0) is not
available to the SUART driver.
You can also look up the clock using con_id if not dev_id. Duplicating
clock structure is definitely
Nori, Sekhar nsek...@ti.com writes:
Hi Kevin,
On Sat, Dec 11, 2010 at 06:01:19, Kevin Hilman wrote:
Subhasish Ghosh ghosh.subhas...@gmail.com writes:
The patch adds support for emulated UART controllers
on the programmable realtime unit (PRU) available on OMAPL138.
This defines the
On Fri, Dec 03, 2010 at 20:41:47, Subhasish Ghosh wrote:
The patch adds support for emulated UART controllers
on the programmable realtime unit (PRU) available on OMAPL138.
This defines the system resource requirements such as pin mux,
clock, iomem, interrupt etc and registers the platform
Hello.
On 03-12-2010 18:11, Subhasish Ghosh wrote:
The patch adds support for emulated UART controllers
on the programmable realtime unit (PRU) available on OMAPL138.
This defines the system resource requirements such as pin mux,
clock, iomem, interrupt etc and registers the platform device
as
On Wed, Dec 15, 2010 at 18:31:43, Sergei Shtylyov wrote:
Hello.
On 03-12-2010 18:11, Subhasish Ghosh wrote:
The patch adds support for emulated UART controllers
on the programmable realtime unit (PRU) available on OMAPL138.
This defines the system resource requirements such as pin mux,
Subhasish Ghosh ghosh.subhas...@gmail.com writes:
The patch adds support for emulated UART controllers
on the programmable realtime unit (PRU) available on OMAPL138.
This defines the system resource requirements such as pin mux,
clock, iomem, interrupt etc and registers the platform device
Hello.
On 03-12-2010 18:11, Subhasish Ghosh wrote:
The patch adds support for emulated UART controllers
on the programmable realtime unit (PRU) available on OMAPL138.
This defines the system resource requirements such as pin mux,
clock, iomem, interrupt etc and registers the platform device
as
The patch adds support for emulated UART controllers
on the programmable realtime unit (PRU) available on OMAPL138.
This defines the system resource requirements such as pin mux,
clock, iomem, interrupt etc and registers the platform device
as per the Linux driver model.
Signed-off-by: Subhasish
I am still receiving the alignment problems with CLK and
da8xx_register_pru_suart, but the actual patch does not have them, would
really appreciate any help. Not sure if this is any problem with the mail
client.
Attached the original patch file for reference.
The CAN and UART patches are not
19 matches
Mail list logo
