From: sashiko-bot@kernel.org
To: "Paul Cercueil" <paul@crapouillou.net>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH] ARM: dts: samsung: exynos4210-i9100: Fix Bluetooth node
Date: Fri, 28 Aug 2026 18:54:39 +0000 [thread overview]
Message-ID: <20260828185439.F33681F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260828184331.655804-1-paul@crapouillou.net>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Baud rate mismatch between Bluetooth controller and host UART due to driver clamping.
--
commit cb253c8ef9aaafc70357be54516beee25ad6e5a6
Author: Paul Cercueil <paul@crapouillou.net>
ARM: dts: samsung: exynos4210-i9100: Fix Bluetooth node
This commit adds the uart-has-rtscts property to the bluetooth node and
configures the max-speed property to 4000000 (4 Mbps) to fix choppy audio
issues on the Galaxy S2.
> diff --git a/arch/arm/boot/dts/samsung/exynos4210-i9100.dts b/arch/arm/boot/dts/samsung/exynos4210-i9100.dts
> --- a/arch/arm/boot/dts/samsung/exynos4210-i9100.dts
> +++ b/arch/arm/boot/dts/samsung/exynos4210-i9100.dts
> @@ -875,11 +875,14 @@ &serial_0 {
> status = "okay";
>
> pinctrl-names = "default";
> + uart-has-rtscts;
> pinctrl-0 = <&bt_en>, <&bt_res>, <&uart0_data>, <&uart0_fctl>;
>
> bluetooth {
> compatible = "brcm,bcm4330-bt";
>
> + max-speed = <4000000>;
[Severity: High]
Does this configuration cause a baud rate mismatch between the Bluetooth
controller and the host UART?
When bcm_setup() configures the Broadcom controller to 4,000,000 bps, it then
calls host_set_baudrate() to configure the host Exynos UART to match.
However, the request propagates to the Exynos UART driver in
drivers/tty/serial/samsung_tty.c, which enforces a hardcoded maximum baud rate
of 3,000,000 via s3c24xx_serial_set_termios():
baud = uart_get_baud_rate(port, termios, old, 0, 3000000);
Because 4,000,000 exceeds this limit, uart_get_baud_rate() falls back to max - 1,
returning 2,999,999.
This creates a baud rate mismatch that introduces framing errors and breaks
subsequent HCI communication.
> +
> shutdown-gpios = <&gpl0 4 GPIO_ACTIVE_HIGH>;
> reset-gpios = <&gpl1 0 GPIO_ACTIVE_LOW>;
> device-wakeup-gpios = <&gpx3 1 GPIO_ACTIVE_HIGH>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260828184331.655804-1-paul@crapouillou.net?part=1
prev parent reply other threads:[~2026-08-28 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 18:43 [PATCH] ARM: dts: samsung: exynos4210-i9100: Fix Bluetooth node Paul Cercueil
2026-08-28 18:54 ` sashiko-bot [this message]
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=20260828185439.F33681F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox