The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Crescent Hsieh <crescentcy.hsieh@moxa.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	FangpingFP.Cheng@moxa.com, Epson.Chiang@moxa.com,
	EddieSY.Lin@moxa.com, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH v5 08/14] serial: 8250_mxpcie: speed up TX using memory-mapped FIFO window
Date: Mon, 3 Aug 2026 06:46:51 +0200	[thread overview]
Message-ID: <7a4900a7-bd31-46ee-81ee-d597899a34de@kernel.org> (raw)
In-Reply-To: <CAHp75VdL71oE-E85fOLbz36bhs3EKg1iL_vtNP+TQzek5PNqnQ@mail.gmail.com>

On 02. 08. 26, 11:10, Andy Shevchenko wrote:
> On Fri, Jul 31, 2026 at 10:49 AM Crescent Hsieh
> <crescentcy.hsieh@moxa.com> wrote:
>>
>> The MUEx50 UART provides a memory-mapped TX FIFO data window along with
>> a TX FIFO level counter.
>>
>> Fill the TX FIFO in bulk via the MMIO FIFO window based on available
>> FIFO space, using uart_port_tx_limited() for the common serial-core TX
>> handling.
> 
> ...
> 
>> +static void mxpcie8250_tx_chars(struct uart_8250_port *up)
>> +{
>> +       struct uart_port *port = &up->port;
>> +       unsigned int offset = 0;
>> +       unsigned char c;
>> +
>> +       uart_port_tx_limited(port, c, port->fifosize - serial_in(up, MOXA_PUART_TX_FIFO_CNT),
>> +                            true,
>> +                            serial_out(up, MOXA_PUART_TX_FIFO_MEM + offset++, c),
>> +                            ({}));
>> +}
> 
> At least three randomly chosen drivers use the empty tx_done, perhaps
> it's time to have a helper that embeds this ugly piece in it and hides
> from the driver?

I haven't tried, can we make the helper a variadic macro?

-- 
js
suse labs

  reply	other threads:[~2026-08-03  4:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31  7:48 [PATCH v5 00/14] serial: 8250: add Moxa MUEx50 PCIe board support Crescent Hsieh
2026-07-31  7:48 ` [PATCH v5 01/14] serial: 8250: split Moxa PCIe serial board support out of 8250_pci Crescent Hsieh
2026-08-02  8:35   ` Andy Shevchenko
2026-07-31  7:48 ` [PATCH v5 02/14] serial: 8250: add Moxa MUEx50 UART port type Crescent Hsieh
2026-07-31  7:48 ` [PATCH v5 03/14] serial: 8250_mxpcie: enable enhanced mode and program FIFO trigger levels Crescent Hsieh
2026-07-31  7:48 ` [PATCH v5 04/14] serial: 8250_mxpcie: enable automatic RTS/CTS flow control Crescent Hsieh
2026-08-02  8:58   ` Andy Shevchenko
2026-07-31  7:48 ` [PATCH v5 05/14] serial: 8250_mxpcie: offload XON/XOFF flow control to MUEx50 hardware Crescent Hsieh
2026-08-02  9:00   ` Andy Shevchenko
2026-07-31  7:48 ` [PATCH v5 06/14] serial: 8250_mxpcie: add custom handle_irq callback Crescent Hsieh
2026-07-31  7:48 ` [PATCH v5 07/14] serial: 8250_mxpcie: speed up RX using memory-mapped FIFO window Crescent Hsieh
2026-08-02  9:03   ` Andy Shevchenko
2026-07-31  7:48 ` [PATCH v5 08/14] serial: 8250_mxpcie: speed up TX " Crescent Hsieh
2026-08-02  9:10   ` Andy Shevchenko
2026-08-03  4:46     ` Jiri Slaby [this message]
2026-08-03  7:26       ` Andy Shevchenko
2026-08-03  7:28         ` Andy Shevchenko
2026-07-31  7:48 ` [PATCH v5 09/14] serial: 8250_mxpcie: support serial interface mode switching Crescent Hsieh
2026-07-31  7:48 ` [PATCH v5 10/14] serial: 8250: allow low-level drivers to override break control Crescent Hsieh
2026-07-31  7:48 ` [PATCH v5 11/14] serial: 8250_mxpcie: add break support for RS485 using MUEx50 features Crescent Hsieh
2026-07-31  7:48 ` [PATCH v5 12/14] serial: 8250: allow UART drivers to override rx_trig_bytes handling Crescent Hsieh
2026-08-02  9:20   ` Andy Shevchenko
2026-08-04  3:52     ` Crescent Hsieh
2026-07-31  7:48 ` [PATCH v5 13/14] serial: 8250_mxpcie: introduce per-port private data structure Crescent Hsieh
2026-07-31  7:48 ` [PATCH v5 14/14] serial: 8250_mxpcie: implement rx_trig_bytes callbacks via MUEx50 RTL Crescent Hsieh
2026-08-03 14:52 ` [PATCH v5 00/14] serial: 8250: add Moxa MUEx50 PCIe board support Greg Kroah-Hartman

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=7a4900a7-bd31-46ee-81ee-d597899a34de@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=EddieSY.Lin@moxa.com \
    --cc=Epson.Chiang@moxa.com \
    --cc=FangpingFP.Cheng@moxa.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=crescentcy.hsieh@moxa.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    /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