Re: OMAP34xx

Grazvydas Ignotas
2012-02-08T17:23:35Z

On Wed, Feb 8, 2012 at 7:06 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Wed, Feb 08, 2012 at 09:01:24AM -0800, Kevin Hilman wrote:
>> Grazvydas Ignotas <notasas@gmail.com> writes:
>>
>> > On Wed, Feb 8, 2012 at 2:53 AM, Kevin Hilman <khilman@ti.com> wrote:
>> >> Kevin Hilman <khilman@ti.com> writes:
>> >>
>> >>> 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?
>>
>> I believe they were targettted for 3.3-rc.
>>
>> Paul, Greg, can you confirm?
>
> I have no idea what you are refering to here, please be much more
> specific.  You can look at the linux-next tree to answer your question
> yourself as well...

It's about these patches in gregkh/tty.git tty-next:
6bbcbf2 tty: serial: omap-serial: wakeup latency constraint is in
microseconds, not milliseconds
edbe5db tty: serial: OMAP: block idle while the UART is transferring
data in PIO mode
5816269 tty: serial: OMAP: use a 1-byte RX FIFO threshold in PIO mode

It would look to me like they are queued for 3.4 but Kevin says there
were intended for 3.3-rc.

--
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