From: Crescent Hsieh <crescentcy.hsieh@moxa.com>
To: Johan Hovold <johan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 4/4] usb: serial: mxuport: add sysfs control for UART FIFO
Date: Tue, 12 May 2026 19:28:19 +0800 [thread overview]
Message-ID: <agMO03V9xppAtWjf@moxa-ThinkCentre-M90t> (raw)
In-Reply-To: <afy2yeDTHiVFkPmy@hovoldconsulting.com>
On Thu, May 07, 2026 at 05:59:05PM +0200, Johan Hovold wrote:
> On Tue, Mar 24, 2026 at 11:50:41AM +0800, Crescent Hsieh wrote:
> > Add a per-port sysfs attribute, uart_fifo, to allow userspace to enable
> > or disable the UART FIFO at runtime.
>
> Why would you want to do that?
>
> We should try to avoid driver specific sysfs knobs.
The motivation is to allow userspace to choose between lower latency and
higher throughput at runtime. Some latency-sensitive request/response
deployments become unreliable if the UART FIFO is enabled due to the
added buffering delay.
I understand the concern about driver-specific sysfs knobs. UART FIFO
enable/disable seems more like a common UART capability than a
device-unique behaviour.
If a driver-specific sysfs attribute is not the right approach here, do
you have a suggestion for a better interface?
---
Sincerely,
Crescent Hsieh
next prev parent reply other threads:[~2026-05-12 11:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260324035041.352190-1-crescentcy.hsieh@moxa.com>
[not found] ` <20260324035041.352190-2-crescentcy.hsieh@moxa.com>
2026-05-07 14:13 ` [PATCH v1 1/4] usb: serial: mxuport: add support for more MXU50U UART devices Johan Hovold
[not found] ` <20260324035041.352190-3-crescentcy.hsieh@moxa.com>
2026-05-07 14:40 ` [PATCH v1 2/4] usb: serial: mxuport: handle SEND_NEXT tx flow control Johan Hovold
[not found] ` <20260324035041.352190-4-crescentcy.hsieh@moxa.com>
2026-05-07 15:56 ` [PATCH v1 3/4] usb: serial: mxuport: support serial interface mode configuration Johan Hovold
[not found] ` <20260324035041.352190-5-crescentcy.hsieh@moxa.com>
2026-05-07 15:59 ` [PATCH v1 4/4] usb: serial: mxuport: add sysfs control for UART FIFO Johan Hovold
2026-05-12 11:28 ` Crescent Hsieh [this message]
2026-05-13 8:20 ` Johan Hovold
2026-05-13 8:48 ` 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=agMO03V9xppAtWjf@moxa-ThinkCentre-M90t \
--to=crescentcy.hsieh@moxa.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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