From: sashiko-bot@kernel.org
To: "Olivier Louvignes" <olivier@mgcrea.io>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH 2/2] serial: 8250_ingenic: Start the X1600 UART from 16 clocks a bit
Date: Sat, 24 Oct 2026 05:21:16 +0000 [thread overview]
Message-ID: <sashiko-outbox-183553@kernel.org> (raw)
In-Reply-To: <20261024051515.55639-2-olivier@mgcrea.io>
> The X1600 UART samples each bit with UMR clocks, adjusted per bit by
> UACR, while the divisor the 8250 core computes assumes 16. The driver
> never sets them, so the UART keeps what ran before it: on a HiBy R1 the
> vendor kernel leaves UART0's UMR at 8, which by the register's meaning
> doubles every rate set here (the line rate itself was not measured). The
> Bluetooth chip on that UART then never answers: "command 0xfc18 tx
> timeout" from hci_bcm.
>
> Add an X1600 entry that writes UMR = 16 and UACR = 0 at probe. The
> offsets come from Rockbox's X1600 register headers and match the UMR
> read on the R1. The X1000, whose compatible the X1600's falls back to,
> may have the same registers, but I could not check one, so it is left
> alone.
>
> Tested on a HiBy R1: UMR reads 16 and UACR 0 after probe, and the
> BCM43430A1 on UART0 comes up at 1.5 Mbaud and streams A2DP audio.
>
> Signed-off-by: Olivier Louvignes <olivier@mgcrea.io>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261024051515.55639-1-olivier@mgcrea.io?part=2
next prev parent reply other threads:[~2026-10-24 5:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 5:15 [PATCH 1/2] dt-bindings: serial: ingenic: Add the X1600 Olivier Louvignes
2026-10-24 5:15 ` [PATCH 2/2] serial: 8250_ingenic: Start the X1600 UART from 16 clocks a bit Olivier Louvignes
2026-10-24 5:21 ` sashiko-bot [this message]
2026-10-24 17:23 ` H. Nikolaus Schaller
2026-10-24 5:19 ` [PATCH 1/2] dt-bindings: serial: ingenic: Add the X1600 sashiko-bot
2026-10-26 11:03 ` Krzysztof Kozlowski
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-183553@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=olivier@mgcrea.io \
--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.