From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Rengarajan S <rengarajan.s@microchip.com>
Cc: kumaravel.thiagarajan@microchip.com,
tharunkumar.pasumarthi@microchip.com,
gregkh@linuxfoundation.org, jirislaby@kernel.org,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
unglinuxdriver@microchip.com
Subject: Re: [PATCH v1 tty] 8250: microchip: pci1xxxx: Refactor TX Burst code to use pre-existing APIs
Date: Thu, 22 Feb 2024 18:01:34 +0200 (EET) [thread overview]
Message-ID: <37490c91-a48f-e0a1-ec92-2307c08260e2@linux.intel.com> (raw)
In-Reply-To: <20240222134944.1131952-1-rengarajan.s@microchip.com>
On Thu, 22 Feb 2024, Rengarajan S wrote:
> Updated the TX Burst implementation by changing the circular buffer
> processing with the pre-existing APIs in kernel. Also updated conditional
> statements and alignment issues for better readability.
>
> Signed-off-by: Rengarajan S <rengarajan.s@microchip.com>
> ---
> @@ -434,16 +435,7 @@ static void pci1xxxx_tx_burst(struct uart_port *port, u32 uart_status)
>
> xmit = &port->state->xmit;
>
> - if (port->x_char) {
> - writeb(port->x_char, port->membase + UART_TX);
> - port->icount.tx++;
> - port->x_char = 0;
> - return;
> - }
> -
> - if ((uart_tx_stopped(port)) || (uart_circ_empty(xmit))) {
> - port->ops->stop_tx(port);
> - } else {
> + if (!(port->x_char)) {
> data_empty_count = (pci1xxxx_read_burst_status(port) &
> UART_BST_STAT_TX_COUNT_MASK) >> 8;
> do {
> @@ -453,15 +445,22 @@ static void pci1xxxx_tx_burst(struct uart_port *port, u32 uart_status)
> &data_empty_count,
> &valid_byte_count);
>
> - port->icount.tx++;
> if (uart_circ_empty(xmit))
> break;
> } while (data_empty_count && valid_byte_count);
> + } else {
> + writeb(port->x_char, port->membase + UART_TX);
> + port->icount.tx++;
> + port->x_char = 0;
> + return;
Why you made this reorganization for x_char handling?? It seems
entirely wrong thing to do, x_char should have precendence over
sending normal chars.
This patch would have been some much simpler to review if it would have
not attempted to n things in one go, please try to split into sensible
changes.
--
i.
next prev parent reply other threads:[~2024-02-22 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 13:49 [PATCH v1 tty] 8250: microchip: pci1xxxx: Refactor TX Burst code to use pre-existing APIs Rengarajan S
2024-02-22 16:01 ` Ilpo Järvinen [this message]
2024-02-23 9:22 ` Rengarajan.S
2024-02-23 6:08 ` Jiri Slaby
2024-02-23 9:21 ` Rengarajan.S
2024-02-23 9:26 ` Jiri Slaby
2024-02-23 9:36 ` Rengarajan.S
2024-03-04 4:37 ` Rengarajan.S
2024-03-04 6:19 ` Jiri Slaby
2024-03-05 4:15 ` Rengarajan.S
2024-03-05 7:19 ` Jiri Slaby
2024-03-06 6:55 ` Rengarajan.S
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=37490c91-a48f-e0a1-ec92-2307c08260e2@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kumaravel.thiagarajan@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rengarajan.s@microchip.com \
--cc=tharunkumar.pasumarthi@microchip.com \
--cc=unglinuxdriver@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.