From: sashiko-bot@kernel.org
To: "James Hilliard" <james.hilliard1@gmail.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH v8 06/11] serial: 8250_dw: derive RX trigger thresholds from the FIFO depth
Date: Thu, 05 Nov 2026 21:19:11 +0000 [thread overview]
Message-ID: <sashiko-outbox-200216@kernel.org> (raw)
In-Reply-To: <20261105-submit-h616-uart-fifo-v1-v8-6-14024d2b184b@gmail.com>
> DW_apb_uart uses receive thresholds of one byte, one quarter full,
> one half full and two bytes below full. The generic 16550A table describes
> these encodings only for a 16-byte FIFO. For example, the half-full setting
> on a 64-byte DW FIFO is reported as eight bytes instead of 32, and a sysfs
> request for 32 bytes selects the 62-byte encoding.
>
> Build a per-port threshold table from the discovered FIFO depth in dwlib
> and install receive-trigger callbacks for CPR-described FIFOs, including
> LPSS ports. Keep the setup helper available to integrations which obtain
> the depth without probing the optional DW registers. Validate that each
> threshold is positive and representable before constructing the table.
>
> Serialize FCR updates with termios and the port lock, acquire a runtime PM
> reference before accessing the device, and propagate resume errors without
> changing the shadow or hardware. Update only the trigger field so changing
> the threshold preserves the FIFO contents.
>
> The FCR mapping is documented in the DW_apb_uart databook, section 6,
> FIFO Control Register. The existing default FCR encoding is unchanged.
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261105-submit-h616-uart-fifo-v1-v8-0-14024d2b184b@gmail.com?part=6
next prev parent reply other threads:[~2026-11-05 21:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 20:52 [PATCH v8 00/11] serial: 8250_dw: share RX trigger setup and describe Allwinner UARTs James Hilliard
2026-11-05 20:52 ` [PATCH v8 01/11] serial: 8250_dw: allow port setup to report errors James Hilliard
2026-11-05 20:58 ` sashiko-bot
2026-11-09 23:05 ` Andy Shevchenko
2026-11-09 23:06 ` Andy Shevchenko
2026-11-05 20:52 ` [PATCH v8 02/11] serial: 8250_dw: select port setup through platform data James Hilliard
2026-11-05 21:01 ` sashiko-bot
2026-11-05 20:52 ` [PATCH v8 03/11] serial: 8250: widen RX trigger byte counts to 16 bits James Hilliard
2026-11-05 21:03 ` sashiko-bot
2026-11-05 20:52 ` [PATCH v8 04/11] serial: 8250: share the RX trigger conversion helper James Hilliard
2026-11-05 21:08 ` sashiko-bot
2026-11-05 20:52 ` [PATCH v8 05/11] serial: 8250: expose RX trigger controls for custom callbacks James Hilliard
2026-11-05 21:11 ` sashiko-bot
2026-11-05 20:52 ` [PATCH v8 06/11] serial: 8250_dw: derive RX trigger thresholds from the FIFO depth James Hilliard
2026-11-05 21:19 ` sashiko-bot [this message]
2026-11-09 23:10 ` Andy Shevchenko
2026-11-05 20:52 ` [PATCH v8 07/11] dt-bindings: serial: snps-dw-apb-uart: add Allwinner H616 James Hilliard
2026-11-05 21:20 ` sashiko-bot
2026-11-05 20:52 ` [PATCH v8 08/11] serial: 8250_dw: configure the Allwinner H616 UART James Hilliard
2026-11-05 21:27 ` sashiko-bot
2026-11-05 20:52 ` [PATCH v8 09/11] dt-bindings: serial: snps-dw-apb-uart: add Allwinner A523 James Hilliard
2026-11-05 21:31 ` sashiko-bot
2026-11-05 20:52 ` [PATCH v8 10/11] serial: 8250_dw: discover Allwinner A523 FIFO depths through FCC James Hilliard
2026-11-05 21:34 ` sashiko-bot
2026-11-05 20:52 ` [PATCH v8 11/11] serial: 8250_dw: configure RX trigger thresholds for Octeon James Hilliard
2026-11-05 21:38 ` sashiko-bot
2026-11-10 9:54 ` [PATCH v8 00/11] serial: 8250_dw: share RX trigger setup and describe Allwinner UARTs Kryštof Černý
2026-11-10 10:45 ` Andy Shevchenko
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=sashiko-outbox-200216@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=james.hilliard1@gmail.com \
--cc=linux-serial@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.