<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/tty, branch v3.0.56</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/tty?h=v3.0.56</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/tty?h=v3.0.56'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2012-10-07T15:27:26Z</updated>
<entry>
<title>n_gsm: memory leak in uplink error path</title>
<updated>2012-10-07T15:27:26Z</updated>
<author>
<name>Russ Gorby</name>
<email>russ.gorby@intel.com</email>
</author>
<published>2012-08-13T12:45:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e54195a3bb9d5025d96b0e3d3bb8de07a506d4f5'/>
<id>urn:sha1:e54195a3bb9d5025d96b0e3d3bb8de07a506d4f5</id>
<content type='text'>
commit 88ed2a60610974443335c924d7cb8e5dcf9dbdc1 upstream.

Uplink (TX) network data will go through gsm_dlci_data_output_framed
there is a bug where if memory allocation fails, the skb which
has already been pulled off the list will be lost.

In addition TX skbs were being processed in LIFO order

Fixed the memory leak, and changed to FIFO order processing

Signed-off-by: Russ Gorby &lt;russ.gorby@intel.com&gt;
Tested-by: Kappel, LaurentX &lt;laurentx.kappel@intel.com&gt;
Signed-off-by: Alan Cox &lt;alan@linux.intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>n_gsm: added interlocking for gsm_data_lock for certain code paths</title>
<updated>2012-10-07T15:27:25Z</updated>
<author>
<name>Russ Gorby</name>
<email>russ.gorby@intel.com</email>
</author>
<published>2012-08-13T12:44:40Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9ce5f868f54045589dd0f90e6b502efb1becd88d'/>
<id>urn:sha1:9ce5f868f54045589dd0f90e6b502efb1becd88d</id>
<content type='text'>
commit 5e44708f75b0f8712da715d6babb0c21089b2317 upstream.

There were some locking holes in the management of the MUX's
message queue for 2 code paths:
1) gsmld_write_wakeup
2) receipt of CMD_FCON flow-control message
In both cases gsm_data_kick is called w/o locking so it can collide
with other other instances of gsm_data_kick (pulling messages tx_tail)
or potentially other instances of __gsm_data_queu (adding messages to tx_head)

Changed to take the tx_lock in these 2 cases

Signed-off-by: Russ Gorby &lt;russ.gorby@intel.com&gt;
Tested-by: Yin, Fengwei &lt;fengwei.yin@intel.com&gt;
Signed-off-by: Alan Cox &lt;alan@linux.intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>serial: set correct baud_base for EXSYS EX-41092 Dual 16950</title>
<updated>2012-10-07T15:27:25Z</updated>
<author>
<name>Flavio Leitner</name>
<email>fbl@redhat.com</email>
</author>
<published>2012-09-22T00:04:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d482e8f2f8afc2f6fd0a1e450b0516c9ae7fef82'/>
<id>urn:sha1:d482e8f2f8afc2f6fd0a1e450b0516c9ae7fef82</id>
<content type='text'>
commit 26e8220adb0aec43b7acafa0f1431760eee28522 upstream.

Apparently the same card model has two IDs, so this patch
complements the commit 39aced68d664291db3324d0fcf0985ab5626aac2
adding the missing one.

Signed-off-by: Flavio Leitner &lt;fbl@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>serial: pl011: handle corruption at high clock speeds</title>
<updated>2012-10-07T15:27:25Z</updated>
<author>
<name>Linus Walleij</name>
<email>linus.walleij@linaro.org</email>
</author>
<published>2012-09-26T15:21:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f580d511e9fd963d75464de030c3b8de5715ee09'/>
<id>urn:sha1:f580d511e9fd963d75464de030c3b8de5715ee09</id>
<content type='text'>
commit c5dd553b9fd069892c9e2de734f4f604e280fa7a upstream.

This works around a few glitches in the ST version of the PL011
serial driver when using very high baud rates, as we do in the
Ux500: 3, 3.25, 4 and 4.05 Mbps.

Problem Observed/rootcause:

When using high baud-rates, and the baudrate*8 is getting close to
the provided clock frequency (so a division factor close to 1), when
using bursts of characters (so they are abutted), then it seems as if
there is not enough time to detect the beginning of the start-bit which
is a timing reference for the entire character, and thus the sampling
moment of character bits is moving towards the end of each bit, instead
of the middle.

Fix:
Increase slightly the RX baud rate of the UART above the theoretical
baudrate by 5%. This will definitely give more margin time to the
UART_RX to correctly sample the data at the middle of the bit period.

Also fix the ages old copy-paste error in the very stressed comment,
it's referencing the registers used in the PL010 driver rather than
the PL011 ones.

Signed-off-by: Guillaume Jaunet &lt;guillaume.jaunet@stericsson.com&gt;
Signed-off-by: Christophe Arnal &lt;christophe.arnal@stericsson.com&gt;
Signed-off-by: Matthias Locher &lt;matthias.locher@stericsson.com&gt;
Signed-off-by: Rajanikanth HV &lt;rajanikanth.hv@stericsson.com&gt;
Cc: Bibek Basu &lt;bibek.basu@stericsson.com&gt;
Cc: Par-Gunnar Hjalmdahl &lt;par-gunnar.hjalmdahl@stericsson.com&gt;
Signed-off-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Remove BUG_ON from n_tty_read()</title>
<updated>2012-10-07T15:27:24Z</updated>
<author>
<name>Stanislav Kozina</name>
<email>skozina@redhat.com</email>
</author>
<published>2012-08-16T11:01:47Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0950902e1cf419d6fa060ed5f59e7cecd2400028'/>
<id>urn:sha1:0950902e1cf419d6fa060ed5f59e7cecd2400028</id>
<content type='text'>
commit e9490e93c1978b6669f3e993caa3189be13ce459 upstream.

Change the BUG_ON to WARN_ON and return in case of tty-&gt;read_buf==NULL. We want to track a
couple of long standing reports of this but at the same time we can avoid killing the box.

Signed-off-by: Stanislav Kozina &lt;skozina@redhat.com&gt;
Signed-off-by: Alan Cox &lt;alan@linux.intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>pch_uart: Fix parity setting issue</title>
<updated>2012-10-02T16:47:53Z</updated>
<author>
<name>Tomoya MORINAGA</name>
<email>tomoya.rohm@gmail.com</email>
</author>
<published>2012-07-06T08:19:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b960ba52595157ae215c4e899e9da99fbc81959a'/>
<id>urn:sha1:b960ba52595157ae215c4e899e9da99fbc81959a</id>
<content type='text'>
commit 38bd2a1ac736901d1cf4971c78ef952ba92ef78b upstream.

Parity Setting value is reverse.
E.G. In case of setting ODD parity, EVEN value is set.
This patch inverts "if" condition.

Signed-off-by: Tomoya MORINAGA &lt;tomoya.rohm@gmail.com&gt;
Acked-by: Alan Cox &lt;alan@linux.intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>pch_uart: Fix rx error interrupt setting issue</title>
<updated>2012-10-02T16:47:53Z</updated>
<author>
<name>Tomoya MORINAGA</name>
<email>tomoya.rohm@gmail.com</email>
</author>
<published>2012-07-06T08:19:42Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4b14f6f47a76380216419e70a3d569eed730a47b'/>
<id>urn:sha1:4b14f6f47a76380216419e70a3d569eed730a47b</id>
<content type='text'>
commit 9539dfb7ac1c84522fe1f79bb7dac2990f3de44a upstream.

Rx Error interrupt(E.G. parity error) is not enabled.
So, when parity error occurs, error interrupt is not occurred.
As a result, the received data is not dropped.

This patch adds enable/disable rx error interrupt code.

Signed-off-by: Tomoya MORINAGA &lt;tomoya.rohm@gmail.com&gt;
Acked-by: Alan Cox &lt;alan@linux.intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>pch_uart: Fix missing break for 16 byte fifo</title>
<updated>2012-10-02T16:47:53Z</updated>
<author>
<name>Alan Cox</name>
<email>alan@linux.intel.com</email>
</author>
<published>2012-07-02T17:51:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=00b35456c281ca28739b83e6493ae5e981c68bf5'/>
<id>urn:sha1:00b35456c281ca28739b83e6493ae5e981c68bf5</id>
<content type='text'>
commit 9bc03743fff0770dc5a5324ba92e67cc377f16ca upstream.

Otherwise we fall back to the wrong value.

Reported-by: &lt;dcb314@hotmail.com&gt;
Resolves-bug: https://bugzilla.kernel.org/show_bug.cgi?id=44091
Signed-off-by: Alan Cox &lt;alan@linux.intel.com&gt;
Signed-off-by: Tomoya MORINAGA &lt;tomoya.rohm@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>tty: Allow uart_register/unregister/register</title>
<updated>2012-06-01T07:12:56Z</updated>
<author>
<name>Alan Cox</name>
<email>alan@linux.intel.com</email>
</author>
<published>2012-05-14T13:51:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3c867337cdb88f7b31f9fcf07003e97d408fcd26'/>
<id>urn:sha1:3c867337cdb88f7b31f9fcf07003e97d408fcd26</id>
<content type='text'>
commit 1e66cded334e6cea596c72f6f650eec351b1e959 upstream.

This is legitimate but because we don't clear the drv-&gt;state pointer in the
unregister code causes a bogus BUG().

Resolves-bug: https://bugzilla.kernel.org/show_bug.cgi?id=42880
Signed-off-by: Alan Cox &lt;alan@linux.intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Add missing call to uart_update_timeout()</title>
<updated>2012-06-01T07:12:56Z</updated>
<author>
<name>Lothar Waßmann</name>
<email>LW@KARO-electronics.de</email>
</author>
<published>2012-05-03T09:37:12Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e9fecd74e41f2a9ff04071675be20a5db97723ac'/>
<id>urn:sha1:e9fecd74e41f2a9ff04071675be20a5db97723ac</id>
<content type='text'>
commit 8b979f7c6bf13a57e7b6002f1175312a44773960 upstream.

This patch fixes a problem reported here:
http://article.gmane.org/gmane.linux.ports.arm.kernel/155242/match=auart

Signed-off-by: Lothar Waßmann &lt;LW@KARO-electronics.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
</feed>
