Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Lukas Timmermann" <linux@timmermann.space>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v2] ARM: dts: exynos: Add bluetooth support to manta
Date: Sun, 14 Jun 2026 20:32:01 +0000	[thread overview]
Message-ID: <20260614203202.6432A1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260614-manta-bluetooth-v2-1-52de06cabf9d@timmermann.space>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Missing `max-speed` property in the Bluetooth node significantly restricts UART bandwidth.
--

commit 661518d39bb3c0a9a3884e1d914c3ff2bc70cf74
Author: Lukas Timmermann <linux@timmermann.space>

ARM: dts: exynos: Add bluetooth support to manta

This commit enables the bcm4330-bt device for manta boards on serial0.
It also adds the necessary pin definitions and interrupt handling for wakeup.

> diff --git a/arch/arm/boot/dts/samsung/exynos5250-manta.dts b/arch/arm/boot/dts/samsung/exynos5250-manta.dts
> index 24a27b342227b..76d3657eb22f0 100644
> --- a/arch/arm/boot/dts/samsung/exynos5250-manta.dts
> +++ b/arch/arm/boot/dts/samsung/exynos5250-manta.dts

[ ... ]

> @@ -536,7 +557,25 @@ &sd1_cmd {
>  
>  /* Bluetooth */
>  &serial_0 {
> -	status = "disabled";
> +	pinctrl-0 = <&uart0_data &uart0_fctl>;
> +	pinctrl-names = "default";
> +
> +	bluetooth {
> +		compatible = "brcm,bcm4330-bt";
> +
> +		pinctrl-0 = <&bt_reg_on &bt_wake &bt_host_wakeup>;

[Severity: Medium]
Should this node include a max-speed property to negotiate a high-speed
UART connection?

Without max-speed, the brcm,bcm4330-bt driver in drivers/bluetooth/hci_bcm.c
leaves the oper_speed at 0 and skips negotiating a higher baud rate. This
forces the UART to operate at its default 115200 bps. 

Operating at 115200 bps restricts the bandwidth to around 11.5 KB/s, which
can cause high-bandwidth Bluetooth profiles like A2DP to stutter or fail.
Other Exynos boards typically set max-speed (e.g., max-speed = <3000000>)
to prevent this bottleneck.

> +		pinctrl-names = "default";
> +
> +		shutdown-gpios = <&gph0 0 GPIO_ACTIVE_HIGH>;
> +		device-wakeup-gpios = <&gph1 3 GPIO_ACTIVE_HIGH>;

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260614-manta-bluetooth-v2-1-52de06cabf9d@timmermann.space?part=1

      reply	other threads:[~2026-06-14 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-14 20:16 [PATCH v2] ARM: dts: exynos: Add bluetooth support to manta Lukas Timmermann
2026-06-14 20:32 ` 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=20260614203202.6432A1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux@timmermann.space \
    --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