<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/tty/serial/8250, branch linux-4.0.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.0.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.0.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2015-05-06T20:03:59Z</updated>
<entry>
<title>serial: 8250: Check UART_SCR is writable</title>
<updated>2015-05-06T20:03:59Z</updated>
<author>
<name>Peter Hurley</name>
</author>
<published>2015-03-09T18:05:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cc1064fc8f1d71f9c3429e6bdd8129629fc39784'/>
<id>urn:sha1:cc1064fc8f1d71f9c3429e6bdd8129629fc39784</id>
<content type='text'>
commit f01a0bd8921b9d6668d41fae3198970e6318f532 upstream.

Au1x00/RT2800+ doesn't implement the 8250 scratch register (and
this may be true of other h/w currently supported by the 8250 driver);
read back the canary value written to the scratch register to enable
the console h/w restart after resume from system suspend.

Fixes: 4516d50aabedb ("serial: 8250: Use canary to restart console ...")
Reported-by: Mason &lt;slash.tmp@free.fr&gt;
Signed-off-by: Peter Hurley &lt;peter@hurleysoftware.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>serial: 8250_dw: add support for AMD SOC Carrizo</title>
<updated>2015-05-06T20:03:59Z</updated>
<author>
<name>Ken Xue</name>
</author>
<published>2015-03-09T09:10:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=39b991a4765e2f7bd2faa383c66df5237117a8bb'/>
<id>urn:sha1:39b991a4765e2f7bd2faa383c66df5237117a8bb</id>
<content type='text'>
commit 5ef86b74209db33c133b5f18738dd8f3189b63a1 upstream.

Add ACPI identifier for UART on AMD SOC Carrizo.

Signed-off-by: Ken Xue &lt;Ken.Xue@amd.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>serial: 8250_dw: Fix deadlock in LCR workaround</title>
<updated>2015-03-11T15:39:52Z</updated>
<author>
<name>Peter Hurley</name>
</author>
<published>2015-03-11T13:19:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7fd6f640f2dd17dac6ddd6702c378cb0bb9cfa11'/>
<id>urn:sha1:7fd6f640f2dd17dac6ddd6702c378cb0bb9cfa11</id>
<content type='text'>
Trying to write console output from within the serial console driver
while the port-&gt;lock is held causes recursive deadlock:

  CPU 0
spin_lock_irqsave(&amp;port-&gt;lock)
printk()
  console_unlock()
    call_console_drivers()
      serial8250_console_write()
        spin_lock_irqsave(&amp;port-&gt;lock)
** DEADLOCK **

The 8250_dw i/o accessors try to write a console error message if the
LCR workaround was unsuccessful. When the port-&gt;lock is already held
(eg., when called from serial8250_set_termios()), this deadlocks.

Make the error message a FIXME until a general solution is devised.

Cc: Tim Kryger &lt;tim.kryger@gmail.com&gt;
Reported-by: Zhang Zhen &lt;zhenzhang.zhang@huawei.com&gt;
Signed-off-by: Peter Hurley &lt;peter@hurleysoftware.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>serial: 8250_dw: Fix get_mctrl behaviour</title>
<updated>2015-03-07T02:06:51Z</updated>
<author>
<name>Desmond Liu</name>
</author>
<published>2015-02-27T00:35:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dfd37668ea6d5029fb5d8a66ea5e202d0655fad7'/>
<id>urn:sha1:dfd37668ea6d5029fb5d8a66ea5e202d0655fad7</id>
<content type='text'>
Fixed behaviour of get_mctrl() serial driver function as documented in:
https://www.kernel.org/doc/Documentation/serial/driver

Added device-tree properties 'dcd-override', 'dsr-override',
'cts-override', and 'ri-override' specific to the Synopsis 8250
DesignWare UART driver. Allows one to force Data Carrier Detect,
Clear To Send, and Data Set Ready signals to permanently be reported as
active. The Ring indicator can be forced to be reported as inactive.

It is possible that if modem control signalling is enabled on a port
that doesn't have these pins (e.g. - a simple two wire Tx/Rx port), the
driver can hang indefinitely waiting for the state to change. The new
DT properties allow the driver to ignore the state of these pins on
serial ports that don't support them, as recommended in the kernel
documentation.

Reviewed-by: JD (Jiandong) Zheng &lt;jdzheng@broadcom.com&gt;
Signed-off-by: Jonathan Richardson &lt;jonathar@broadcom.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>serial:8250:8250_pci: delete unneeded quirk entries</title>
<updated>2015-03-07T02:06:51Z</updated>
<author>
<name>Wang YanQing</name>
</author>
<published>2015-03-06T17:08:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7cf91108d44dbef3d48766fd0e7f7347c2e48bda'/>
<id>urn:sha1:7cf91108d44dbef3d48766fd0e7f7347c2e48bda</id>
<content type='text'>
These quirk entries have the same effect as default
quirk entry, so we can just delete them.

Signed-off-by: Wang YanQing &lt;udknight@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>serial:8250:8250_pci: fix redundant entry report for WCH_CH352_2S</title>
<updated>2015-03-07T02:06:51Z</updated>
<author>
<name>Wang YanQing</name>
</author>
<published>2015-03-06T17:13:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6262a3692b921a82075695c5c6d10f4a6bcc5fac'/>
<id>urn:sha1:6262a3692b921a82075695c5c6d10f4a6bcc5fac</id>
<content type='text'>
Commit 8b5c913f7ee6464849570bacb6bcd9ef0eaf7dce
("serial: 8250_pci: Add WCH CH352 quirk to avoid Xscale detection")
trigger one redundant entry report message.

This patch fix it.

Reported-by: Russell King &lt;rmk@arm.linux.org.uk&gt;
Signed-off-by: Wang YanQing &lt;udknight@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Change email address for 8250_pci</title>
<updated>2015-03-07T02:06:51Z</updated>
<author>
<name>Russell King</name>
</author>
<published>2015-03-06T10:49:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f2e0ea861117bda073d1d7ffbd3120c07c0d5d34'/>
<id>urn:sha1:f2e0ea861117bda073d1d7ffbd3120c07c0d5d34</id>
<content type='text'>
I'm still receiving reports to my email address, so let's point this
at the linux-serial mailing list instead.

Cc: &lt;stable@vger.kernel.org&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>serial: 8250: Revert "tty: serial: 8250_core: read only RX if there is something in the FIFO"</title>
<updated>2015-03-07T02:06:51Z</updated>
<author>
<name>Sebastian Andrzej Siewior</name>
</author>
<published>2015-02-15T17:32:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ca8bb4aefb932e3da105f28cbfba36d57a931081'/>
<id>urn:sha1:ca8bb4aefb932e3da105f28cbfba36d57a931081</id>
<content type='text'>
This reverts commit 0aa525d11859c1a4d5b78fdc704148e2ae03ae13.

The conditional RX-FIFO read seems to cause spurious interrupts and we
see just:
|serial8250: too much work for irq29

The previous behaviour was "default" for decades and Marvell's 88f6282 SoC
might not be the only that relies on it. Therefore the Omap fix is
reverted for now.

Fixes: 0aa525d11859 ("tty: serial: 8250_core: read only RX if there is
something in the FIFO")
Reported-By: Nicolas Schichan &lt;nschichan@freebox.fr&gt;
Debuged-By: Peter Hurley &lt;peter@hurleysoftware.com&gt;
Signed-off-by: Sebastian Andrzej Siewior &lt;bigeasy@linutronix.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>serial: 8250: Fix UART_BUG_TXEN workaround</title>
<updated>2015-02-07T10:44:55Z</updated>
<author>
<name>Peter Hurley</name>
</author>
<published>2015-02-02T20:47:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c09babfab7ae8c7d79a5dce9d866fbb28b82dde4'/>
<id>urn:sha1:c09babfab7ae8c7d79a5dce9d866fbb28b82dde4</id>
<content type='text'>
UARTs which do not trigger THRE interrupt if the fifo is already
empty when the interrupt is enabled need tx primed manually. These
UARTs are identified by the UART_BUG_TXEN flag to enable the
required workaround.

However, the current workaround is broken; if the fifo is already
empty but the shifter is still transmitting, then serial8250_tx_chars()
will not be called but no further THRE interrupt will occur, and
tx will stall. The appropriate check is for fifo empty (THRE), not
transmitter empty (TEMT).

Signed-off-by: Dick Hollenbeck &lt;dick@softplc.com&gt;
[pjh: rewrote commit log]
Signed-off-by: Peter Hurley &lt;peter@hurleysoftware.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>tty/serial: serial8250_set_divisor() can be static</title>
<updated>2015-02-02T18:11:28Z</updated>
<author>
<name>kbuild test robot</name>
</author>
<published>2015-01-31T00:58:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=eb1527a8738bcfe12a42475aeef105914d63615a'/>
<id>urn:sha1:eb1527a8738bcfe12a42475aeef105914d63615a</id>
<content type='text'>
drivers/tty/serial/8250/8250_core.c:2503:6: sparse: symbol 'serial8250_set_divisor' was not declared. Should it be static?

Signed-off-by: Fengguang Wu &lt;fengguang.wu@intel.com&gt;
Cc: Peter Hurley &lt;peter@hurleysoftware.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
