<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/tty/serial/meson_uart.c, branch linux-4.11.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.11.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.11.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2017-01-19T13:38:57Z</updated>
<entry>
<title>tty: serial: meson: allow baud-rates higher than 115200</title>
<updated>2017-01-19T13:38:57Z</updated>
<author>
<name>Martin Blumenstingl</name>
</author>
<published>2017-01-15T22:32:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8c9faa556a37e62799fd22d7409386b1b8ddd4e7'/>
<id>urn:sha1:8c9faa556a37e62799fd22d7409386b1b8ddd4e7</id>
<content type='text'>
The vendor driver allows setting baud-rates higher than 115200 baud.
There is a check in the vendor driver which prevents using more than
115200 baud during startup, however it does not have such a check in
.set_termios.
Higher baud-rates are often used by the bluetooth modules embedded into
the SDIO wifi chips (Amlogic devices use brcmfmac based wifi chips quite
often, 2000000 baud seems to be a common value for the UART baud-rate in
Amlogic's "libbt").

I have tested this on a Meson GXL device with uart_A (to which the
bluetooth module is connected, where initialization times out with
115200 baud) and uart_AO (which I manually set to 2000000 baud  and then
connected with my USB UART adapter to that).

Signed-off-by: Martin Blumenstingl &lt;martin.blumenstingl@googlemail.com&gt;
Acked-by: Kevin Hilman &lt;khilman@baylibre.com&gt;
Tested-by: Andreas Färber &lt;afaerber@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>tty: serial: meson: Implement earlycon support</title>
<updated>2016-04-30T16:26:55Z</updated>
<author>
<name>Andreas Färber</name>
</author>
<published>2016-03-06T11:21:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=736d553886a72274e58ff8a0e8a2899978042b8f'/>
<id>urn:sha1:736d553886a72274e58ff8a0e8a2899978042b8f</id>
<content type='text'>
Split off the bulk of the existing meson_serial_console_write()
implementation into meson_serial_port_write() for implementing
meson_serial_early_console_write().

Use "meson" as the earlycon driver name, courtesy of Nicolas.

Signed-off-by: Nicolas Saenz Julienne &lt;nicolassaenzj@gmail.com&gt;
Acked-by: Carlo Caione &lt;carlo@endlessm.com&gt;
Signed-off-by: Andreas Färber &lt;afaerber@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>tty: serial: meson: Add support for XTAL clock input</title>
<updated>2016-02-15T01:39:36Z</updated>
<author>
<name>Andreas Färber</name>
</author>
<published>2016-02-08T12:49:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=146f3808e08faabba46ea9574133a66aa4a9468d'/>
<id>urn:sha1:146f3808e08faabba46ea9574133a66aa4a9468d</id>
<content type='text'>
Fix the baudrate calculation for 24 MHz XTAL clock found on gxbb platforms.

Signed-off-by: Andreas Färber &lt;afaerber@suse.de&gt;
Acked-by: Carlo Caione &lt;carlo@endlessm.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ARM: meson: serial: check for tx-irq enabled in irq code</title>
<updated>2015-12-14T03:59:48Z</updated>
<author>
<name>Ben Dooks</name>
</author>
<published>2015-11-18T14:41:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=39469654db20a14915a7fb33ca2ec67547011ece'/>
<id>urn:sha1:39469654db20a14915a7fb33ca2ec67547011ece</id>
<content type='text'>
Ensure that if the interrupt handler is entered then only try and do tx
work if the tx irq is enabled.

Signed-off-by: Ben Dooks &lt;ben.dooks@codethink.co.uk&gt;
Tested-by: Carlo Caione &lt;carlo@endlessm.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ARM: meson: serial: ensure tx irq on if more work to do</title>
<updated>2015-12-14T03:59:48Z</updated>
<author>
<name>Ben Dooks</name>
</author>
<published>2015-11-18T14:41:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f1dd05c82985f9c476969598fd97cc680f18e86b'/>
<id>urn:sha1:f1dd05c82985f9c476969598fd97cc680f18e86b</id>
<content type='text'>
The tx_stop() call turns the interrupt off, but the tx_start() does not
check if the interrupt is enabled. Switch it back on if there is more
work to do.

Signed-off-by: Ben Dooks &lt;ben.dooks@codethink.co.uk&gt;
Tested-by: Carlo Caione &lt;carlo@endlessm.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ARM: meson: serial: disable rx/tx irqs during console write</title>
<updated>2015-12-14T03:59:48Z</updated>
<author>
<name>Ben Dooks</name>
</author>
<published>2015-11-18T14:41:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2561f068d91bbb1bd132b439c9023120c0b28cf4'/>
<id>urn:sha1:2561f068d91bbb1bd132b439c9023120c0b28cf4</id>
<content type='text'>
As an attempt to stop issues with bad console output, ensure that both the
rx and tx interrupts are disabled during the console write to avoid any
problems with console and non-console being called together.

This should help with the SMP case as it should stop other cores being
signalled during the console write.

Signed-off-by: Ben Dooks &lt;ben.dooks@codethink.co.uk&gt;
Tested-by: Carlo Caione &lt;carlo@endlessm.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ARM: meson: serial: use meson_uart_tx_empty() to wait for empty</title>
<updated>2015-12-14T03:59:48Z</updated>
<author>
<name>Ben Dooks</name>
</author>
<published>2015-11-18T14:41:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f1f5c1400f7907a1b52be94cabe8992b480785cf'/>
<id>urn:sha1:f1f5c1400f7907a1b52be94cabe8992b480785cf</id>
<content type='text'>
Use the meson_uart_tx_empty() instead of a direct read of the status
register. This is easier to read and will ensure the UART's transmit
state machine is idle when trying to update the baud rate.

Signed-off-by: Ben Dooks &lt;ben.dooks@codethink.co.uk&gt;
Tested-by: Carlo Caione &lt;carlo@endlessm.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ARM: meson: serial: only disable tx irq on stop</title>
<updated>2015-12-14T03:59:48Z</updated>
<author>
<name>Ben Dooks</name>
</author>
<published>2015-11-18T14:41:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=855ddcab352c15b8c4d0bd93759f821250c601fb'/>
<id>urn:sha1:855ddcab352c15b8c4d0bd93759f821250c601fb</id>
<content type='text'>
Since disabling the transmit state machine still allows characters to
be transmitted when written to the UART write FIFO, simply disable the
transmit interrupt when the UART port is stopped.

This has not shown an improvement with the console issues when running
systemd, but seems like it should be done.

Signed-off-by: Ben Dooks &lt;ben.dooks@codethink.co.uk&gt;
Reported-by: Edward Cragg &lt;ed.cragg@codethink.co.uk&gt;
Tested-by: Carlo Caione &lt;carlo@endlessm.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ARM: meson: serial: ensure console port uart enabled</title>
<updated>2015-12-14T03:59:48Z</updated>
<author>
<name>Ben Dooks</name>
</author>
<published>2015-11-18T14:41:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=41788f054920d591c2d44838b73457e9d33ebd2c'/>
<id>urn:sha1:41788f054920d591c2d44838b73457e9d33ebd2c</id>
<content type='text'>
Ensure the UART's transmitter is enabled when meson_console_putchar is
called. If not, then the console output is corrupt (the hardware seems
to try and send /something/ even if the TX is disabled).

This fixes corrupt console output on events such as trying to reboot the
system since the console tx may be called after drivers shutdown method has
been called.

Signed-off-by: Ben Dooks &lt;ben.dooks@codethink.co.uk&gt;
Reported-by: Edward Cragg &lt;edward.cragg@codethink.co.uk&gt;
Tested-by: Carlo Caione &lt;carlo@endlessm.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ARM: meson: serial: tx_empty fails to check for transmitter busy</title>
<updated>2015-12-14T03:59:48Z</updated>
<author>
<name>Ben Dooks</name>
</author>
<published>2015-11-18T14:41:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=88679739012cda64b1a45ee9dea16d04380dba71'/>
<id>urn:sha1:88679739012cda64b1a45ee9dea16d04380dba71</id>
<content type='text'>
The tx_empty() uart_op should only return empty if both the transmit fifo
and the transmit state-machine are both idle. Add a test for the hardware's
XMIT_BUSY flag.

Note, this is possibly related to an issue where the port is being shutdown
with paritally transmitted characters in it.

Signed-off-by: Ben Dooks &lt;ben.dooks@codethink.co.uk&gt;
Reported-by: Edward Cragg &lt;edward.cragg@codethink.co.uk&gt;
Tested-by: Carlo Caione &lt;carlo@endlessm.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
