>-----Original Message----- >From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Kevin >Hilman >Sent: Wednesday, January 06, 2010 5:27 PM >To: Steve Sakoman >Cc: Robert Nelson; linux-omap@xxxxxxxxxxxxxxx >Subject: Re: serial port input corruption with 2.6.32? > >Steve Sakoman <sakoman@xxxxxxxxx> writes: > >> On Wed, Dec 23, 2009 at 1:06 PM, Robert Nelson <robertcnelson@xxxxxxxxx> wrote: >>> On Wed, Dec 23, 2009 at 2:59 PM, Steve Sakoman <sakoman@xxxxxxxxx> 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. 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@xxxxxxxxxxxxxxx >More majordomo info at http://vger.kernel.org/majordomo-info.html ��.n��������+%������w��{.n�����{�������ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
