Thread (128 messages) 128 messages, 28 authors, 2012-04-05

Re: OMAP34xx

From: Grazvydas Ignotas <hidden>
Date: 2012-02-08 10:46:19

On Wed, Feb 8, 2012 at 2:53 AM, Kevin Hilman [off-list ref] wrote:
Kevin Hilman [off-list ref] writes:
quoted
Tony Lindgren [off-list ref] writes:

[...]
quoted
quoted
Basically, it looks like the OMAP 3 UART is not delivering transmit IRQs
while in some of the deeper low power modes.

I tried reverting the rest of the patches between this one and HEAD for
omap-serial.c, but they have no effect what so ever on this bug.  As I
said in one of my emails in this thread, the above commit can't be
trivially reverted because some other stuff that the code relied upon
has vanished.

So, the above along with the other part in arch/arm/mach-omap2/cpuidle34xx.c
is the smallest 'fix' I could find if resolving the regression.
OK, thanks, that should be enough info for let Kevin take a look at this.
This one is indeed strange.  I have not seen this on the 34xx devices
I'm using (3430/n900, 3530/Overo, 3630/Zoom3).
OK, I've reproduced this on v3.3-rc2.

The reason I wasn't seeing this is because I'm using the fixes Paul has
already posted that fix this problem:

       http://marc.info/?l=linux-arm-kernel&m=132754676814391&w=2

Kevin
But it looks like these are now queued for 3.4 in tty tree?


-- 
Gražvydas
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help