Ohad,
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Ohad Ben-Cohen
> Sent: Tuesday, November 23, 2010 9:09 PM
> To: linux-omap@vger.kernel.org; linux-ker...@vger.kernel.org; linux-arm-
> ker...@lists.infradead.org
>
> -Original Message-
> From: Cousson, Benoit
> Sent: Tuesday, November 23, 2010 11:21 PM
> To: DebBarma, Tarun Kanti
> Cc: linux-omap@vger.kernel.org; Gopinath, Thara; Basak, Partha
> Subject: Re: [PATCHv4 11/14] OMAP2+: dmtimer: convert to platform devices
>
> On 11/20/2010 3:39 AM, Tarun
Signed-off-by: Axel Lin
---
sound/soc/omap/osk5912.c | 11 ---
1 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/sound/soc/omap/osk5912.c b/sound/soc/omap/osk5912.c
index 18d053d..7e75e77 100644
--- a/sound/soc/omap/osk5912.c
+++ b/sound/soc/omap/osk5912.c
@@ -177,7 +177,8
Return PTR_ERR(omap3pandora_dac_reg) instead of 0 if regulator_get failed.
Signed-off-by: Axel Lin
---
sound/soc/omap/omap3pandora.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/sound/soc/omap/omap3pandora.c b/sound/soc/omap/omap3pandora.c
index bff9864..8047c52 10064
> -Original Message-
> From: Cousson, Benoit
> Sent: Tuesday, November 23, 2010 8:52 PM
> To: DebBarma, Tarun Kanti
> Cc: linux-omap@vger.kernel.org
> Subject: Re: [PATCHv4 7/14] OMAP: dmtimer: use list instead of static
> array
>
> On 11/20/2010 3:39 AM, Tarun Kanti DebBarma wrote:
> > Co
> -Original Message-
> From: Cousson, Benoit
> Sent: Tuesday, November 23, 2010 8:19 PM
> To: DebBarma, Tarun Kanti
> Cc: linux-omap@vger.kernel.org; Gopinath, Thara
> Subject: Re: [PATCHv4 2/14] OMAP: dmtimer: infrastructure to support hwmod
>
> On 11/20/2010 3:39 AM, DebBarma, Tarun Kant
> -Original Message-
> From: TAO HU [mailto:tgh...@motorola.com]
> Sent: Wednesday, November 24, 2010 11:40 AM
> To: Santosh Shilimkar
> Cc: TAO HU; Bryan Wu; linux-omap
> Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort
>
> Hi, Santosh
>
> Could you point out the specific
Hi, Santosh
Could you point out the specific kernel option for "L3 error debugging"?
On Wed, Nov 24, 2010 at 1:40 PM, Santosh Shilimkar
wrote:
> TAO,
>> -Original Message-
>> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
>> ow...@vger.kernel.org] On Behalf Of TAO HU
>> Sent:
TAO,
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of TAO HU
> Sent: Wednesday, November 24, 2010 10:05 AM
> To: Bryan Wu
> Cc: TAO HU; linux-omap
> Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort
>
>
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Kevin Hilman
> Sent: Wednesday, November 24, 2010 2:06 AM
> To: Santosh Shilimkar
> Cc: Nishanth Menon; linux-omap; Jean Pihet; Vishwanath Sripathy; Tony
> Subject: Re: [P
On Wed, Nov 24, 2010 at 02:56, Hari Kanigeri wrote:
> In the current mailbox driver, the mailbox internal pointer for
> callback can be directly manipulated by the Users, so a second
> User can easily corrupt the first user's callback pointer.
> The initial effort to correct this issue can be refe
On Wed, Nov 24, 2010 at 02:56, Hari Kanigeri wrote:
> Schedule the Tasklet to send only when mailbox fifo is full and there are
> pending messages in kifo, else send the message directly in the Process
Typo -> kifo
> context. This would avoid needless scheduling of Tasklet for every message
> tr
On Wed, Nov 24, 2010 at 02:56, Hari Kanigeri wrote:
> From: Fernando Guzman Lugo
>
> The variable rq_full flag is a global variable, so if there are multiple
> mailbox users there will be conflicts. Now there is a full flag per
> mailbox queue.
>
> Reported-by: Ohad Ben-Cohen
> Signed-off-by: Fe
On Wed, Nov 24, 2010 at 02:56, Hari Kanigeri wrote:
Should the subject be like this?
OMAP4: mailbox: fix rx interrupt disable
> disablign rx interrupt on omap4 is different than its pre-decessors.
Typo ->disablign
> The bit in OMAP4_MAILBOX_IRQENABLE_CLR should be set to disable the
> interrup
Hu Tao,
We hit this issue every time when we build the kernel on the board.
Are you running some stress testing program on the board?
Thanks,
-Bryan
On Wed, Nov 24, 2010 at 12:34 PM, TAO HU wrote:
> Hi, Bryan
>
> Thanks.
>
> Unfortunately, it is not easy to reproduce the problem in our HW.
> We
Hi, Bryan
Thanks.
Unfortunately, it is not easy to reproduce the problem in our HW.
We only observed 2~3 times so far.
But we do enable HIGHMEM, SMP and L2 cache in our config.
That's why I'd like to know the root cause.
On Wed, Nov 24, 2010 at 12:21 PM, Bryan Wu wrote:
> Tao Hu,
>
> Did you t
Tao Hu,
Did you try the similar solution in our Ubuntu kernel? We suspect it
related to HIGHMEM, SMP and cache control code.
And how about your test case?
Thanks a lot,
-Bryan
On Wed, Nov 24, 2010 at 11:11 AM, TAO HU wrote:
> Hi, All
>
> We got following errors on OMAP ES2.0 board.
>
> And noti
Hi, All
We got following errors on OMAP ES2.0 board.
And noticed a similar case was reported at below link
http://www.opensubscriber.com/message/kernel-t...@lists.ubuntu.com/14591440.html
Is any conclusion/fix available?
<1>[ 348.873840] Unhandled fault: imprecise external abort (0x1406) at
0x4
Kevin Hilman wrote, on 11/23/2010 06:16 PM:
[..]
Let's please just make this behave like clock& hwmod data and move on.
I suppose we could do that in the interest of world peace and global
warming ;) hopefully the v5 will the last set.
--
Regards,
Nishanth Menon
--
To unsubscribe from this
From: Yanick Saugy
The PIN which controls LCD's reset signal (VGA_nRESET/h_GPIO_96) was not
configured as a GPIO. We had to modify the OMAP MUX, and select this PIN
(CAM_XCLKA) as an output GPIO (OMAP_MUX_MODE4). (kernel 2.6.35)
Be aware of changing this PIN will probably disable the camera, bec
Hi James,
> The second error log is the stack trace when the watchdog timer calls
> SYNC_EnterCS.
Actually is not the WDT calling the function to get into the critical
section, it is the WDT being disabled when the DSP is going to OFF
state. This should fine.
> The stack trace is shown below.
>
Hi James,
On Tue, Nov 23, 2010 at 8:34 AM, James Adams wrote:
> A bit more information about why videos are not playing in a port of
> Zoom2 to gumstix:
>
> 2)
> If I use the OpenCORE unit tests I can successfully decode:
> VGA movies with software codec
> 1280*544 movie with software codec
>
"Cousson, Benoit" writes:
> On 11/23/2010 11:56 PM, Menon, Nishanth wrote:
>> Cousson, Benoit had written, on 11/23/2010 04:33 PM, the following:
>>> Hi Nishanth,
>>>
>>> On 11/23/2010 4:19 PM, Menon, Nishanth wrote:
Kevin Hilman had written, on 11/22/2010 06:09 PM, the following:
> Nish
"Rafael J. Wysocki" writes:
> On Tuesday, November 23, 2010, Alan Stern wrote:
>> On Tue, 23 Nov 2010, Rafael J. Wysocki wrote:
>>
>> > > > Moreover, I'm not sure if we need an "IRQ safe" version of _idle. Why
>> > > > do
>> > > > we need it, exactly?
>> > >
>> > > Because pm_runtime_put_sync
On 11/23/2010 11:56 PM, Menon, Nishanth wrote:
Cousson, Benoit had written, on 11/23/2010 04:33 PM, the following:
Hi Nishanth,
On 11/23/2010 4:19 PM, Menon, Nishanth wrote:
Kevin Hilman had written, on 11/22/2010 06:09 PM, the following:
Nishanth Menon writes:
Kevin Hilman wrote, on 11/2
Hi Ohad,
On Tue, 2010-11-23 at 17:38 +0200, Ohad Ben-Cohen wrote:
> From: Simon Que
>
> Add hwspinlock support for the OMAP4 Hardware Spinlock device.
>
> +
> + io_base = ioremap(res->start, resource_size(res));
> + if (!io_base) {
> + ret = -ENOMEM;
> + goto
Cousson, Benoit had written, on 11/23/2010 04:33 PM, the following:
Hi Nishanth,
On 11/23/2010 4:19 PM, Menon, Nishanth wrote:
Kevin Hilman had written, on 11/22/2010 06:09 PM, the following:
Nishanth Menon writes:
Kevin Hilman wrote, on 11/22/2010 05:19 PM:
Nishanth Menon writes:
This
On Tuesday, November 23, 2010, Alan Stern wrote:
> On Tue, 23 Nov 2010, Rafael J. Wysocki wrote:
>
> > > > Moreover, I'm not sure if we need an "IRQ safe" version of _idle. Why
> > > > do
> > > > we need it, exactly?
> > >
> > > Because pm_runtime_put_sync() calls rpm_idle(). If there were no
Hi Nishanth,
On 11/23/2010 4:19 PM, Menon, Nishanth wrote:
Kevin Hilman had written, on 11/22/2010 06:09 PM, the following:
Nishanth Menon writes:
Kevin Hilman wrote, on 11/22/2010 05:19 PM:
Nishanth Menon writes:
This patch adds OPP tables for OMAP4. New file has been added to keep
the
In the current mailbox driver, the mailbox internal pointer for
callback can be directly manipulated by the Users, so a second
User can easily corrupt the first user's callback pointer.
The initial effort to correct this issue can be referred here:
https://patchwork.kernel.org/patch/107520/
Along
Schedule the Tasklet to send only when mailbox fifo is full and there are
pending messages in kifo, else send the message directly in the Process
context. This would avoid needless scheduling of Tasklet for every message
transfer
Signed-off-by: Hari Kanigeri
---
arch/arm/plat-omap/mailbox.c |
Fix the following checkpatch warnings observed in mailbox module.
WARNING: please, no space for starting a line,
excluding comments
+ fail_alloc_rxq:$
WARNING: please, no space for starting a line,
excluding comments
+ fail_alloc_txq
From: Fernando Guzman Lugo
The variable rq_full flag is a global variable, so if there are multiple
mailbox users there will be conflicts. Now there is a full flag per
mailbox queue.
Reported-by: Ohad Ben-Cohen
Signed-off-by: Fernando Guzman Lugo
Signed-off-by: Hari Kanigeri
---
arch/arm/pla
disablign rx interrupt on omap4 is different than its pre-decessors.
The bit in OMAP4_MAILBOX_IRQENABLE_CLR should be set to disable the
interrupts instead of clearing the bit.
Defined rev field in mailbox structure to differentiate the mailbox
versions.
Signed-off-by: Hari Kanigeri
---
arch/ar
Thanks to Benoit and Felipe Balbi for their comments.
Here is the revised set taking into account comments received.
- Added more description for checkpatch warnings
- Created revision field to check for mailbox IP version to use for rx
interrupt disable functionality.
Nishanth Menon writes:
> Kevin Hilman had written, on 11/22/2010 06:09 PM, the following:
>> Nishanth Menon writes:
>>
>>> Kevin Hilman wrote, on 11/22/2010 05:19 PM:
Nishanth Menon writes:
> This patch adds OPP tables for OMAP4. New file has been added to keep
> the OMAP4 opp
Santosh Shilimkar writes:
>> -Original Message-
>> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
>> ow...@vger.kernel.org] On Behalf Of Kevin Hilman
>> Sent: Tuesday, November 23, 2010 12:46 AM
>> To: Nishanth Menon
>> Cc: linux-omap; Jean Pihet; Vishwanath Sripathy; Tony
>>
On Tue, Nov 23, 2010 at 03:01:17PM +0100, Uwe Kleine-König wrote:
> I wonder if it's not better to make these static inlines instead. Then
> no naming conflicts can occur. And maybe we'd catch some more strange
> things because p gets a proper type.
>
> I don't know how this influences gcc thoug
Hi,
While supporting one of customer I came across one interesting issue and
finding with WAITFORVSYNC ioctl -
Problem Statement -
---
With WAITFORVSYNC lots of tearing artifacts are visible on LCD output, but
WAITFORGO works fine without any issues.
Debugging/Findings -
---
On 11/20/2010 3:39 AM, Tarun Kanti DebBarma wrote:
From: Thara Gopinath
Add routines to converts dmtimers to platform devices. The device data
is obtained from hwmod database of respective platform and is registered
to device model after successful binding to driver. It also provides
provision t
From: Simon Que
Add hwspinlock support for the OMAP4 Hardware Spinlock device.
The Hardware Spinlock device on OMAP4 provides hardware assistance
for synchronization between the multiple processors in the system
(dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP).
[o...@wizery.com: adapt to generi
From: Simon Que
Build and register an hwspinlock platform device.
Although only OMAP4 supports the hardware spinlock module (for now),
it is still safe to run this initcall on all omaps, because hwmod lookup
will simply fail on hwspinlock-less platforms.
Signed-off-by: Simon Que
Signed-off-by:
Add a common, platform-independent, hwspinlock framework.
Hardware spinlock devices are needed, e.g., in order to access data
that is shared between remote processors, that otherwise have no
alternative mechanism to accomplish synchronization and mutual exclusion
operations.
Signed-off-by: Ohad B
From: Benoit Cousson
Add hwspinlock hwmod data for OMAP4 chip
Signed-off-by: Cousson, Benoit
Signed-off-by: Hari Kanigeri
Signed-off-by: Ohad Ben-Cohen
Cc: Paul Walmsley
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 63
1 files changed, 63 insertions(+), 0
OMAP4 introduces a Hardware Spinlock device, which provides hardware
assistance for synchronization and mutual exclusion between heterogeneous
processors and those not operating under a single, shared operating system
(e.g. OMAP4 has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP).
The intention o
On 11/20/2010 3:39 AM, Tarun Kanti DebBarma wrote:
Convert dmtimers static array in functions into list structure.
Please note that the static arrays will be completely removed
in subsequent patches when dmtimer is converted to platform driver.
Why do you still need to keep your own list of tim
Kevin Hilman had written, on 11/22/2010 06:09 PM, the following:
Nishanth Menon writes:
Kevin Hilman wrote, on 11/22/2010 05:19 PM:
Nishanth Menon writes:
This patch adds OPP tables for OMAP4. New file has been added to keep
the OMAP4 opp tables and the registration of these tables with th
Remove the usage of omap_gpio_init() from all omap board files
since omap_gpio_init() does nothing, after gpio is implemented
as a platform device.
Signed-off-by: Charulatha V
---
arch/arm/mach-omap1/board-ams-delta.c |1 -
arch/arm/mach-omap1/board-fsample.c|1 -
arch/arm/m
From: Benoit Cousson
Add GPIO hwmod data for OMAP4
Signed-off-by: Benoit Cousson
Signed-off-by: Charulatha V
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 341
1 files changed, 341 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx
Implement GPIO as a platform device.
GPIO APIs are used in machine_init functions. Hence it is
required to complete GPIO probe before board_init. Therefore
GPIO device register and driver register are implemented as
postcore_initcalls.
omap_gpio_init() does nothing now and this function would be
Use omap_device_build() API to do platform_device_register of
GPIO devices. For OMAP2+ chips, the device specific data defined
in the centralized hwmod database will be used.
gpio_init needs to be done before machine_init functions access
gpio APIs. Hence gpio_init is made as a postcore_initcall.
Add GPIO hwmod data for OMAP2430
Signed-off-by: Charulatha V
---
arch/arm/mach-omap2/omap_hwmod_2430_data.c | 279
1 files changed, 279 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_2430_data.c
b/arch/arm/mach-omap2/omap_hwmod_2430_data
Add GPIO hwmod data for OMAP3
Signed-off-by: Charulatha V
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 360
1 files changed, 360 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
b/arch/arm/mac
Add support for handling OMAP16xx specific gpio_init by
providing platform device data and doing device registration.
Signed-off-by: Charulatha V
---
arch/arm/mach-omap1/gpio16xx.c | 199
1 files changed, 199 insertions(+), 0 deletions(-)
create mode 10
Add GPIO hwmod data for OMAP2420
Signed-off-by: Charulatha V
---
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 229
arch/arm/plat-omap/include/plat/gpio.h |5 +
2 files changed, 234 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_24
Add support for handling OMAP7xx specific gpio_init by
providing platform device data and doing device registration.
Signed-off-by: Charulatha V
---
arch/arm/mach-omap1/gpio7xx.c | 261 +
1 files changed, 261 insertions(+), 0 deletions(-)
create mode 100
Prepare for implementing GPIO as a platform driver.
Modifies omap_gpio_init() to make use of omap_gpio_chip_init()
and omap_gpio_mod_init(). omap_gpio_mod_init() does the module init
by clearing the status register and initializing the GPIO control register.
omap_gpio_chip_init() initializes the c
Add support for handling OMAP15xx specific gpio_init by
providing platform device data and doing device registration.
Signed-off-by: Charulatha V
---
arch/arm/mach-omap1/gpio15xx.c | 98
arch/arm/plat-omap/gpio.c | 10 +---
arch/arm/plat-
Implement OMAP GPIO module in platform device model. OMAP2+ specific GPIO
module uses hwmod FW.
Tested on OMAP2430, OMAP44430, OMAP3430 SDP boards, OMAP4430 Blaze board
and zoom3 board. Verified that this patch series does not break the OMAP1
build.
Version History:
---
v7 Series:
- U
On 11/20/2010 3:39 AM, DebBarma, Tarun Kanti wrote:
(1) Add new fields and data structures to support dmtimer conversion
to platform driver.
(2) Constants to identify IP revision so that Highlander IP in OMAP 4
can be distinguished.
(3) field to identify OMAP4 abe timers.
(4) Interface function t
A bit more information about why videos are not playing in a port of
Zoom2 to gumstix:
1)
I can switch to use the software codec by simply removing the
/system/etc/01_Vendor_ti_omx.cfg file.
2)
If I use the OpenCORE unit tests I can successfully decode:
VGA movies with software codec
1280*5
Hello,
On Wed, Oct 13, 2010 at 04:22:01PM +0530, Varadarajan, Charulatha wrote:
> From: Sourav Poddar
>
> Having __v as the variable name for the definition of different macros leads
> to
> the namespace pollution. For example,
> readl(p)
> unrolls to:
> ({ u32 __v = ({ u32 __v = (( __u32)(__le
> Having __v as the variable name for the definition of different macros
> leads to
> the namespace pollution. For example,
> readl(p)
> unrolls to:
> ({ u32 __v = ({ u32 __v = (( __u32)(__le32)(( __le32) ((void)0,
> *(volatile unsigned int *)((p); __v; }); __asm__ __volatile__ ("mcr
> p15,
> ,
On Tue, 2010-11-23 at 09:26 +0200, Jarkko Nikula wrote:
> On Mon, 22 Nov 2010 17:48:24 -0700 (MST)
> Paul Walmsley wrote:
>
> > > Signed-off-by: Janusz Krzysztofik
> >
> > Thanks for fixing this. What do you think about the following patch
> > instead? It should avoid any compiler issues.
>
> -Original Message-
> From: Paul Walmsley [mailto:p...@pwsan.com]
> Sent: Tuesday, November 23, 2010 9:31 AM
> To: Kevin Hilman
> Cc: Cousson, Benoit; Basak, Partha; Varadarajan, Charulatha; linux-
> o...@vger.kernel.org
> Subject: Re: RFC: hwmod, iclks, auto-idle and autodeps
>
> Hi
>
Hi Rene,
This email contains 2 error logs. The first comes from trying to switch
to using the software decoder.
Is there something else I need to do to revert to software codecs
perhaps?
The second error log is the stack trace when the watchdog timer calls
SYNC_EnterCS.
I am sorry for troubling
Hello Mark,
On Fri, 3 Sep 2010 19:20:52 +0100
Mark Brown wrote:
> > re-add? was it there at one point and removed? Any pointers to the
> > old code?
>
> It was present in the pre-merge regulator API which you can find in
> the bowels of:
>
>git://opensource.wolfsonmicro.com/linux-2.6-audi
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Kevin Hilman
> Sent: Tuesday, November 23, 2010 12:46 AM
> To: Nishanth Menon
> Cc: linux-omap; Jean Pihet; Vishwanath Sripathy; Tony
> Subject: Re: [PATCH 00/13] OMAP3: O
Benoit,
> -Original Message-
> From: Cousson, Benoit
> Sent: Tuesday, November 23, 2010 2:11 PM
> To: DebBarma, Tarun Kanti
> Cc: linux-omap@vger.kernel.org; Gopinath, Thara
> Subject: Re: [PATCHv4 1/14] OMAP2+: dmtimer: add device names to flck
> nodes
>
> On 11/23/2010 9:36 AM, DebBarma,
On 11/23/2010 9:36 AM, DebBarma, Tarun Kanti wrote:
Benoit,
-Original Message-
From: Cousson, Benoit
Sent: Monday, November 22, 2010 11:03 PM
To: DebBarma, Tarun Kanti
Cc: linux-omap@vger.kernel.org; Gopinath, Thara
Subject: Re: [PATCHv4 1/14] OMAP2+: dmtimer: add device names to flck
no
Benoit,
> -Original Message-
> From: Cousson, Benoit
> Sent: Monday, November 22, 2010 11:03 PM
> To: DebBarma, Tarun Kanti
> Cc: linux-omap@vger.kernel.org; Gopinath, Thara
> Subject: Re: [PATCHv4 1/14] OMAP2+: dmtimer: add device names to flck
> nodes
>
> Hi Tarun,
>
> On 11/20/2010 3:39
On Mon, Nov 22, 2010 at 03:55:47PM +0100, Cousson, Benoit wrote:
So far we are using a artificial SW IP revision that reflect the
difference we'd like to highlight v1, v2.
but what's the big deal in reading that from HW itself ? The only change
will in the comparisson operator. Instead of doing
72 matches
Mail list logo
