Re: serial port input corruption with 2.6.32?

[Kevin Hilman <khilman@deeprootsystems.com>]

"Pandita, Vikram" <vikram.pandita@ti.com> writes:

>>Steve Sakoman <sakoman@gmail.com> writes:
>>
>>> On Wed, Dec 23, 2009 at 1:06 PM, Robert Nelson <robertcnelson@gmail.com> wrote:
>>>> On Wed, Dec 23, 2009 at 2:59 PM, Steve Sakoman <sakoman@gmail.com> wrote:
>>>>> I'm seeing some strange behavior with my console serial port with 2.6.32.
>>>>>
> <snip>
>>This will also have obvious and serious PM implications for non
>>serial-console devices connected to UARTs (IrDA, bluetooth, modems,
>>etc.)
>
> OMAP uarts for BT etc use h/w flow control, which is another way of
> waking up omap before sending any chars and hence don’t loose data.

Good point.  However, I haven't personally tested (or heard) that it
actually works as would be expected.  Can you confirm working BT over
a UART with idle/unclocking enabled?

Kevin


> Console uses no flow control as you know.
>
>>
>>I've heard some ideas of muxing the UART into GPIO mode when idle and
>>having a bitbanging to get the first char so it is not lost, but
>>haven't seen any patches to do it.
>>
>>While it doesn't really solve your problem, I hope it at least helps
>>understand the reason for it.
>
> You could write a book on uart pm :)
>
>>
>>Kevin
>>
>>
>>--
>>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
--
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