From: Vyacheslav Bocharov <adeep@lexina.in>
To: Neil Armstrong <narmstrong@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH v2 1/4] arm64: meson: add dts bluetooth node for JetHub H1
Date: Sat, 26 Mar 2022 10:51:07 +0300 [thread overview]
Message-ID: <20220326075110.1462301-2-adeep@lexina.in> (raw)
In-Reply-To: <20220326075110.1462301-1-adeep@lexina.in>
Add bluetooth node for RTL8822CS uart to JetHub H1 dts file.
Signed-off-by: Vyacheslav Bocharov <adeep@lexina.in>
---
.../boot/dts/amlogic/meson-gxl-s905w-jethome-jethub-j80.dts | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxl-s905w-jethome-jethub-j80.dts b/arch/arm64/boot/dts/amlogic/meson-gxl-s905w-jethome-jethub-j80.dts
index 6eafb908695f..fcb304c5a40f 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxl-s905w-jethome-jethub-j80.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-gxl-s905w-jethome-jethub-j80.dts
@@ -213,6 +213,12 @@ &uart_A {
pinctrl-0 = <&uart_a_pins>, <&uart_a_cts_rts_pins>;
pinctrl-names = "default";
uart-has-rtscts;
+
+ bluetooth {
+ compatible = "realtek,rtl8822cs-bt";
+ enable-gpios = <&gpio GPIOX_17 GPIO_ACTIVE_HIGH>;
+ host-wake-gpios = <&gpio GPIOX_18 GPIO_ACTIVE_HIGH>;
+ };
};
&uart_C {
--
2.30.2
next prev parent reply other threads:[~2022-03-26 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 7:51 [PATCH v2 0/4] arm64: meson: update dts for JetHub devices Vyacheslav Bocharov
2022-03-26 7:51 ` Vyacheslav Bocharov [this message]
2022-03-26 7:51 ` [PATCH v2 2/4] arm64: meson: dts: update serial alias in dts for JetHub D1 Vyacheslav Bocharov
2022-03-26 7:51 ` [PATCH v2 3/4] arm64: meson: update SDIO voltage " Vyacheslav Bocharov
2022-03-26 7:51 ` [PATCH v2 4/4] arm64: meson: update WiFi SDIO " Vyacheslav Bocharov
2022-04-04 7:55 ` [PATCH v2 0/4] arm64: meson: update dts for JetHub devices Neil Armstrong
2022-04-04 8:01 ` Neil Armstrong
2022-04-04 10:39 ` Vyacheslav
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=20220326075110.1462301-2-adeep@lexina.in \
--to=adeep@lexina.in \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
/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;
as well as URLs for NNTP newsgroup(s).