From: Gray Huang <gray.huang@wesion.com>
To: Heiko Stuebner <heiko@sntech.de>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
nick@khadas.com
Subject: [PATCH 6/6] arm64: dts: rockchip: Add Bluetooth support for Khadas Edge 2L
Date: Wed, 29 Apr 2026 14:51:42 +0800 [thread overview]
Message-ID: <50276dda-0610-4146-9224-e49f869685ac@wesion.com> (raw)
In-Reply-To: <3716011.atdPhlSkOF@phil>
On 4/27/26 20:27, Heiko Stuebner wrote:
> Am Mittwoch, 25. März 2026, 06:46:14 Mitteleuropäische Sommerzeit schrieb Gray Huang:
>> Enable Bluetooth support for the Ampak AP6275P module on the
>> Khadas Edge 2L. This involves enabling the UART5 interface for
>> HCI communication and defining the required regulators and
>> power-sequence pins.
>>
>> Signed-off-by: Gray Huang <gray.huang@wesion.com>
>> ---
>> .../dts/rockchip/rk3576-khadas-edge-2l.dts | 35 +++++++++++++++++++
>> 1 file changed, 35 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3576-khadas-edge-2l.dts b/arch/arm64/boot/dts/rockchip/rk3576-khadas-edge-2l.dts
>> index 8ecd00f6645d..345dc4c981c1 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3576-khadas-edge-2l.dts
>> +++ b/arch/arm64/boot/dts/rockchip/rk3576-khadas-edge-2l.dts
>> @@ -560,6 +560,20 @@ usb_host_pwren: usb-host-pwren {
>> };
>> };
>>
>> + bluetooth {
>> + bt_reg_on: bt-reg-on {
>> + rockchip,pins = <4 RK_PB2 RK_FUNC_GPIO &pcfg_pull_up>;
>> + };
>> +
>> + bt_wake_host: bt-wake-host {
>> + rockchip,pins = <0 RK_PB1 RK_FUNC_GPIO &pcfg_pull_down>;
>> + };
>> +
>> + host_wake_bt: host-wake-bt {
>> + rockchip,pins = <0 RK_PA5 RK_FUNC_GPIO &pcfg_pull_up>;
>> + };
>> + };
> same sorting problem with bluetooth between usb-foo and wifi-foo.
>
>> +
>> wifi {
>> wifi_reg_on: wifi-reg-on {
>> rockchip,pins = <4 RK_PA2 RK_FUNC_GPIO &pcfg_pull_up>;
> Heiko
Has been sorted alphabetically in patch of v2.
Gray
next prev parent reply other threads:[~2026-04-29 6:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 5:46 [PATCH 0/6] arm64: dts: rockchip: Add peripheral support for Khadas Edge 2L Gray Huang
2026-03-25 5:46 ` [PATCH 1/6] arm64: dts: rockchip: Add PMIC " Gray Huang
2026-03-25 5:46 ` [PATCH 2/6] arm64: dts: rockchip: Add AP6275P wireless " Gray Huang
2026-04-27 12:25 ` Heiko Stuebner
2026-03-25 5:46 ` [PATCH 3/6] arm64: dts: rockchip: Enable GPU " Gray Huang
2026-03-25 5:46 ` [PATCH 4/6] arm64: dts: rockchip: Add HDMI and VOP support " Gray Huang
2026-03-25 5:46 ` [PATCH 5/6] arm64: dts: rockchip: Enable USB " Gray Huang
2026-04-27 12:27 ` Heiko Stuebner
2026-04-29 6:49 ` Gray Huang
2026-03-25 5:46 ` [PATCH 6/6] arm64: dts: rockchip: Add Bluetooth support " Gray Huang
2026-04-27 12:27 ` Heiko Stuebner
2026-04-29 6:51 ` Gray Huang [this message]
2026-04-27 12:23 ` (subset) [PATCH 0/6] arm64: dts: rockchip: Add peripheral " Heiko Stuebner
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=50276dda-0610-4146-9224-e49f869685ac@wesion.com \
--to=gray.huang@wesion.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=nick@khadas.com \
--cc=robh@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