From: Gabriel Somlo <gsomlo@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-serial@vger.kernel.org, gregkh@linuxfoundation.org,
jirislaby@kernel.org, kgugala@antmicro.com,
mholenko@antmicro.com, joel@jms.id.au,
david.abdurachmanov@gmail.com, florent@enjoy-digital.fr,
geert@linux-m68k.org, ilpo.jarvinen@linux.intel.com
Subject: [PATCH v6 09/14] serial: liteuart: clean up rx loop variables
Date: Wed, 23 Nov 2022 08:04:55 -0500 [thread overview]
Message-ID: <20221123130500.1030189-10-gsomlo@gmail.com> (raw)
In-Reply-To: <20221123130500.1030189-1-gsomlo@gmail.com>
The `status` variable will always be `1` when passed into the call
to `uart_insert_char()`, so it can be eliminated altogether.
Use `u8` as the type for `ch`, as it matches the return type of
the `litex_read8()` call which produces its value.
Signed-off-by: Gabriel Somlo <gsomlo@gmail.com>
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
---
Changes from v5:
- removing `status` variable altogether
- using `u8` for `ch`, matching the type of the call producing it
rather than that of the calls that consume its value
drivers/tty/serial/liteuart.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/tty/serial/liteuart.c b/drivers/tty/serial/liteuart.c
index 81aa7c1da73c..62bfd2ed9051 100644
--- a/drivers/tty/serial/liteuart.c
+++ b/drivers/tty/serial/liteuart.c
@@ -73,10 +73,9 @@ static void liteuart_timer(struct timer_list *t)
struct liteuart_port *uart = from_timer(uart, t, timer);
struct uart_port *port = &uart->port;
unsigned char __iomem *membase = port->membase;
- int ch;
- unsigned long status;
+ u8 ch;
- while ((status = !litex_read8(membase + OFF_RXEMPTY)) == 1) {
+ while (!litex_read8(membase + OFF_RXEMPTY)) {
ch = litex_read8(membase + OFF_RXTX);
port->icount.rx++;
@@ -85,7 +84,7 @@ static void liteuart_timer(struct timer_list *t)
/* no overflow bits in status */
if (!(uart_handle_sysrq_char(port, ch)))
- uart_insert_char(port, status, 0, ch, TTY_NORMAL);
+ uart_insert_char(port, 1, 0, ch, TTY_NORMAL);
}
tty_flip_buffer_push(&port->state->port);
--
2.38.1
next prev parent reply other threads:[~2022-11-23 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 13:04 [PATCH v6 00/14] serial: liteuart: add IRQ support Gabriel Somlo
2022-11-23 13:04 ` [PATCH v6 01/14] serial: liteuart: use KBUILD_MODNAME as driver name Gabriel Somlo
2022-11-23 13:04 ` [PATCH v6 02/14] serial: liteuart: use bit number macros Gabriel Somlo
2022-11-23 13:04 ` [PATCH v6 03/14] serial: liteuart: remove unused uart_ops stubs Gabriel Somlo
2022-11-23 13:04 ` [PATCH v6 04/14] serial: liteuart: don't set unused port fields Gabriel Somlo
2022-11-23 13:04 ` [PATCH v6 05/14] serial: liteuart: minor style fix in liteuart_init() Gabriel Somlo
2022-11-23 13:04 ` [PATCH v6 06/14] serial: liteuart: move tty_flip_buffer_push() out of rx loop Gabriel Somlo
2022-11-23 13:04 ` [PATCH v6 07/14] serial: liteuart: rx loop should only ack rx events Gabriel Somlo
2022-11-23 13:04 ` [PATCH v6 08/14] serial: liteuart: simplify passing of uart_insert_char() flag Gabriel Somlo
2022-11-23 13:04 ` Gabriel Somlo [this message]
2022-11-23 13:04 ` [PATCH v6 10/14] serial: liteuart: separate rx loop from poll timer Gabriel Somlo
2022-11-23 13:04 ` [PATCH v6 11/14] serial: liteuart: move function definitions Gabriel Somlo
2022-11-23 13:04 ` [PATCH v6 12/14] serial: liteuart: add IRQ support for the RX path Gabriel Somlo
2022-11-23 13:04 ` [PATCH v6 13/14] serial: liteuart: add IRQ support for the TX path Gabriel Somlo
2022-11-23 13:05 ` [PATCH v6 14/14] serial: liteuart: move polling putchar() function Gabriel Somlo
2022-11-24 7:02 ` [PATCH v6 00/14] serial: liteuart: add IRQ support Jiri Slaby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221123130500.1030189-10-gsomlo@gmail.com \
--to=gsomlo@gmail.com \
--cc=david.abdurachmanov@gmail.com \
--cc=florent@enjoy-digital.fr \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=joel@jms.id.au \
--cc=kgugala@antmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mholenko@antmicro.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®