All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier L'Heureux <olivier.lheureux@mind.be>
To: Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org,
	Olivier L'Heureux <olivier.lheureux@mind.be>
Subject: [PATCH 1/7] ARM: dts: stm32: Add Bluetooth (usart2) feature on stm32mp157x
Date: Tue,  5 Sep 2023 00:11:52 +0200	[thread overview]
Message-ID: <20230904221158.35425-2-olivier.lheureux@mind.be> (raw)
In-Reply-To: <20230904221158.35425-1-olivier.lheureux@mind.be>

From: Christophe Roullier <christophe.roullier@st.com>

Add BT (usart2) config on stm32mp157x.

Signed-off-by: Christophe Roullier <christophe.roullier@st.com>
Change-Id: I41cc7d60900e05d8bd4e3281abe170ef3fbbaee8
Reviewed-on: https://gerrit.st.com/c/mpu/oe/st/linux-stm32/+/237115
Reviewed-by: CITOOLS <MDG-smet-aci-reviews@list.st.com>
Reviewed-by: Eric FOURMONT <eric.fourmont-ext@st.com>
Tested-by: Eric FOURMONT <eric.fourmont-ext@st.com>

Cherry-picked for v5.13: dropped part of patch for absent
"stm32mp157f-dk2.dts".
---
 arch/arm/boot/dts/st/stm32mp157c-dk2.dts | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/st/stm32mp157c-dk2.dts b/arch/arm/boot/dts/st/stm32mp157c-dk2.dts
index 4bef2300ed7c..680391433992 100644
--- a/arch/arm/boot/dts/st/stm32mp157c-dk2.dts
+++ b/arch/arm/boot/dts/st/stm32mp157c-dk2.dts
@@ -102,5 +102,14 @@ &usart2 {
 	pinctrl-0 = <&usart2_pins_c>;
 	pinctrl-1 = <&usart2_sleep_pins_c>;
 	pinctrl-2 = <&usart2_idle_pins_c>;
-	status = "disabled";
+	uart-has-rtscts;
+	status = "okay";
+
+	bluetooth {
+		shutdown-gpios = <&gpioz 6 GPIO_ACTIVE_HIGH>;
+		compatible = "brcm,bcm43438-bt";
+		max-speed = <3000000>;
+		vbat-supply = <&v3v3>;
+		vddio-supply = <&v3v3>;
+	};
 };
-- 
2.39.2


  reply	other threads:[~2023-09-04 22:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04 22:11 [PATCH RFC 0/7] Fix a memory leak in Bluetooth L2CAP Olivier L'Heureux
2023-09-04 22:11 ` Olivier L'Heureux [this message]
2023-09-04 22:38   ` bluez.test.bot
2023-09-04 22:11 ` [PATCH 2/7] Bluetooth: add many traces for allocation/free/refcounting Olivier L'Heureux
2023-09-04 22:11 ` [PATCH 3/7] Bluetooth: L2CAP: use refcount on struct l2cap_chan->conn Olivier L'Heureux
2023-09-04 22:11 ` [PATCH 4/7] Bluetooth: L2CAP: free the leaking struct l2cap_conn Olivier L'Heureux
2023-09-04 22:11 ` [PATCH 5/7] Bluetooth: introduce hci_conn_free() for better structure Olivier L'Heureux
2023-09-04 22:11 ` [PATCH 6/7] Bluetooth: L2CAP: inc refcount if reuse struct l2cap_conn Olivier L'Heureux
2023-09-04 22:11 ` [PATCH 7/7] Bluetooth: unlink objects to avoid use-after-free Olivier L'Heureux
2023-09-05 20:42 ` [PATCH RFC 0/7] Fix a memory leak in Bluetooth L2CAP Luiz Augusto von Dentz
2023-09-12 19:19   ` Luiz Augusto von Dentz
2023-09-13 22:25   ` Olivier L'Heureux
2023-09-14 21:17     ` Luiz Augusto von Dentz
2023-11-07  8:46       ` Marleen Vos
2023-11-07 15:10         ` Luiz Augusto von Dentz
     [not found]           ` <CAJav_R4Dp1rddk67vNDPvwS4208pk7-aORXM0KiwXPaOkXmGkw@mail.gmail.com>
2023-11-13 14:58             ` Luiz Augusto von Dentz
2023-11-13 15:01               ` Marleen Vos

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=20230904221158.35425-2-olivier.lheureux@mind.be \
    --to=olivier.lheureux@mind.be \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.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 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.