Patch "arm64: dts: rockchip: Correct GPIO polarity on brcm BT nodes" has been added to the 6.6-stable tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This is a note to let you know that I've just added the patch titled

    arm64: dts: rockchip: Correct GPIO polarity on brcm BT nodes

to the 6.6-stable tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     arm64-dts-rockchip-correct-gpio-polarity-on-brcm-bt-.patch
and it can be found in the queue-6.6 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.



commit c753aabcdc9b17fd90b9e1c76600266faad4b82e
Author: Diederik de Haas <didi.debian@xxxxxxxxx>
Date:   Fri Oct 18 16:45:50 2024 +0200

    arm64: dts: rockchip: Correct GPIO polarity on brcm BT nodes
    
    [ Upstream commit 08846522d9a7bccf18d4f97c3f39d03c7a193970 ]
    
    Paragraph "3.4 Power up Timing Sequence" of the AzureWave-CM256SM
    datasheet mentions the following about the BT_REG_ON pin, which is
    connected to GPIO0_C4_d:
    
      When this pin is low and WL_REG_ON is high,
      the BT section is in reset.
    
    Therefor set that pin to GPIO_ACTIVE_HIGH so that it can be pulled low
    for a reset.
    If set to GPIO_ACTIVE_LOW, the following errors are observed:
    
      Bluetooth: hci0: command 0x0c03 tx timeout
      Bluetooth: hci0: BCM: Reset failed (-110)
    
    So fix the GPIO polarity by setting it to ACTIVE_HIGH.
    This also matches what other devices with the same BT device have.
    
    Fixes: 2b6a3f857550 ("arm64: dts: rockchip: Fix reset-gpios property on brcm BT nodes")
    Signed-off-by: Diederik de Haas <didi.debian@xxxxxxxxx>
    Link: https://lore.kernel.org/r/20241018145053.11928-2-didi.debian@xxxxxxxxx
    Signed-off-by: Heiko Stuebner <heiko@xxxxxxxxx>
    Signed-off-by: Sasha Levin <sashal@xxxxxxxxxx>

diff --git a/arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi b/arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi
index 27d89f48c42bd..9944c9d4ca9fe 100644
--- a/arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi
@@ -687,7 +687,7 @@ bluetooth {
 		host-wakeup-gpios = <&gpio0 RK_PC3 GPIO_ACTIVE_HIGH>;
 		pinctrl-0 = <&bt_enable_h>, <&bt_host_wake_l>, <&bt_wake_h>;
 		pinctrl-names = "default";
-		shutdown-gpios = <&gpio0 RK_PC4 GPIO_ACTIVE_LOW>;
+		shutdown-gpios = <&gpio0 RK_PC4 GPIO_ACTIVE_HIGH>;
 		vbat-supply = <&vcc_wl>;
 		vddio-supply = <&vcca_1v8_pmu>;
 	};
diff --git a/arch/arm64/boot/dts/rockchip/rk3566-radxa-cm3.dtsi b/arch/arm64/boot/dts/rockchip/rk3566-radxa-cm3.dtsi
index e9fa9bee995ae..1e36f73840dad 100644
--- a/arch/arm64/boot/dts/rockchip/rk3566-radxa-cm3.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3566-radxa-cm3.dtsi
@@ -404,7 +404,7 @@ bluetooth {
 		host-wakeup-gpios = <&gpio2 RK_PB1 GPIO_ACTIVE_HIGH>;
 		pinctrl-names = "default";
 		pinctrl-0 = <&bt_host_wake_h &bt_reg_on_h &bt_wake_host_h>;
-		shutdown-gpios = <&gpio2 RK_PC0 GPIO_ACTIVE_LOW>;
+		shutdown-gpios = <&gpio2 RK_PC0 GPIO_ACTIVE_HIGH>;
 		vbat-supply = <&vcc_3v3>;
 		vddio-supply = <&vcc_1v8>;
 	};




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux