From nobody Wed Nov 27 19:47:41 2024 Received: from out-175.mta0.migadu.com (out-175.mta0.migadu.com [91.218.175.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 15A091D6194 for ; Tue, 8 Oct 2024 11:34:24 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.175 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728387266; cv=none; b=jzoABVBkC4KLbJBI8eQZKvrAoR3FlMFFc03lAPvHs8tjiARG5hF1gXPVvwYGAbzS7909x5a5hNyW9+B/rzGjDnWUHZ9F9yd+ueMQ7XkfnyE484m/obFV6/rM2pi7duIz3oFAI7y7daxx3loiAALqoGwvnW3On2kfZuawtYlx1+o= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728387266; c=relaxed/simple; bh=/7vd3ObIjcsI2mZSyc0wBr+Lay/uyYQATpXFnYqwHO4=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=tG4gj0Jg5aJFuUQ6HuAH0A9h1X+gjaoOsAlxcj93Q13Up8gmvhRZuODXWGcHfoIWWajqcJQbrftuHoSYlCA1r1OTdStVni7ghCwUxKD/kqFyOzOUe4Dlar+/ThN11W7WegHF1Q7HM8Fj6+kPhBe1zavKK2p/qCA/ox7Yhu47TXI= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=cknow.org; spf=pass smtp.mailfrom=cknow.org; dkim=pass (2048-bit key) header.d=cknow.org header.i=@cknow.org header.b=yDy3J+/c; arc=none smtp.client-ip=91.218.175.175 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=cknow.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=cknow.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=cknow.org header.i=@cknow.org header.b="yDy3J+/c" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cknow.org; s=key1; t=1728387263; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=gZ+i+HZ0rdHDHJHDLF23OW3zaIUfIrmSTf6E1PPqT9E=; b=yDy3J+/cMtLHcUvZheYWqUpPALn6ryr/gIZaHpW/2exGa9wHvjNjMZfFjPD+FHathn5KmE kHOM1QGOpCqlS4eI6MkOByZzNRnM7lpuSy/Z/y0XLWs0jJAFaqImgxyNn4270VeM/jNkA4 4IRDBa9pLdChclFMdsVoJDpkxyI8HyVsC7FgsiseJ74+1IKJaj6iR0mmGbAyLWLMFVWzGi J9y3su7H2RjUmjDO/buJhqqQDLidgIkx6cEQ5pL+aAS+gLY4B/XlFLix7btS4UkoyVuqKI zDUhKYTNcvUPsk/orBE2DWZA/ZtGMbJZjTnWbnPrApou8TUJPZktVusT7cuPHw== From: Diederik de Haas To: Rob Herring , Krzysztof Kozlowski , Conor Dooley , Heiko Stuebner Cc: Diederik de Haas , Dragan Simic , Michael Riesch , Samuel Holland , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 1/4] arm64: dts: rockchip: Add PD to csi dphy node on rk356x Date: Tue, 8 Oct 2024 13:15:36 +0200 Message-ID: <20241008113344.23957-2-didi.debian@cknow.org> In-Reply-To: <20241008113344.23957-1-didi.debian@cknow.org> References: <20241008113344.23957-1-didi.debian@cknow.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Migadu-Flow: FLOW_OUT Content-Type: text/plain; charset="utf-8" The "rockchip-inno-csi-dphy.yaml" binding requires the power-domains property. According to RK3568 TRM Part 1 section 7.3 (page 475) the CSIHOST is placed in the PD_VI power domain. So set the csi_dphy node power-domains property accordingly. Fixes: b6c228401b25 ("arm64: dts: rockchip: add csi dphy node to rk356x") Signed-off-by: Diederik de Haas --- changes in v2: - No change arch/arm64/boot/dts/rockchip/rk356x.dtsi | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/boot/dts/rockchip/rk356x.dtsi b/arch/arm64/boot/dts= /rockchip/rk356x.dtsi index 0ee0ada6f0ab..d581170914f9 100644 --- a/arch/arm64/boot/dts/rockchip/rk356x.dtsi +++ b/arch/arm64/boot/dts/rockchip/rk356x.dtsi @@ -1790,6 +1790,7 @@ csi_dphy: phy@fe870000 { clocks =3D <&cru PCLK_MIPICSIPHY>; clock-names =3D "pclk"; #phy-cells =3D <0>; + power-domains =3D <&power RK3568_PD_VI>; resets =3D <&cru SRST_P_MIPICSIPHY>; reset-names =3D "apb"; rockchip,grf =3D <&grf>; --=20 2.45.2 From nobody Wed Nov 27 19:47:41 2024 Received: from out-180.mta0.migadu.com (out-180.mta0.migadu.com [91.218.175.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E09F41D8E1F for ; Tue, 8 Oct 2024 11:34:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.180 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728387269; cv=none; b=pW6/NF58czxjJX4s4Rd08Je/BAWUtezNZp+zMSlo8tsTitat0ZKSZ12oXRUD3jQbi7M1NXWJDC5DjwJdvfXbYy4tZtZ/J09UaQjBMunLZ3JXHRXKsY3yOIm0t/fS53/m7foDilH0Efve1R1GyBafXk9NYGN6UnOGeznW2U6BHwM= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728387269; c=relaxed/simple; bh=LlhEEJc2nRBOLpYcB4z4fC5JKOQ8ZpijXtD73XaXMlU=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=QpMfakEMKBhrj9T2JWVrsWpyXy9SZx3FenlfAChhaEPHWJaln4xrSrMKkoTKlNW7kPDZaguQ9KK07Wa1iGAdajXJd74Oq+RsS9M/fD5sh65eOrX9ZkHZaHZHCKFBDG4OORyz3JwYn1unoEJvhK4pIPGPOe7xffbHNMuduUxw+FI= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=cknow.org; spf=pass smtp.mailfrom=cknow.org; dkim=pass (2048-bit key) header.d=cknow.org header.i=@cknow.org header.b=GEDW03eJ; arc=none smtp.client-ip=91.218.175.180 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=cknow.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=cknow.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=cknow.org header.i=@cknow.org header.b="GEDW03eJ" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cknow.org; s=key1; t=1728387265; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WyJ7Z5sCax3H+U1/xrEos8F1I+KiAxNN6XMVHBXY4YM=; b=GEDW03eJ3ggGaiWlnJZzvdHe2KnXWLCVhZE2Ly0QfRU60p6HxGcEy3sEz4zYCVsVYk6pkO /R8n4MlSnb76WoQKEvLP9xwV56S8m4VS99AYVRrNVFtYlh48IosF7o8CH3MYFOociduR0M nKuiqlzoCSvj8E61OY0eWKk59BS/sDAGg+cxFDoRJR4K5WoVWAdJEDTJV3sYdEb7FinaZ9 IbCVmafzbuuz7c+ofPoOVTVtLoxeNqFBvlkg9BSTSjPTExL+BfV2XrsK0qi1Bq9X8xIkRu 0yE5ztEWRZnD1dmGEtBrO5wxd5qhs8mKU5xl39PJqqdYfC7Zumw1NU03wbLeWA== From: Diederik de Haas To: Rob Herring , Krzysztof Kozlowski , Conor Dooley , Heiko Stuebner Cc: Diederik de Haas , Dragan Simic , Michael Riesch , Samuel Holland , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 2/4] arm64: dts: rockchip: Remove hdmi's 2nd interrupt on rk3328 Date: Tue, 8 Oct 2024 13:15:37 +0200 Message-ID: <20241008113344.23957-3-didi.debian@cknow.org> In-Reply-To: <20241008113344.23957-1-didi.debian@cknow.org> References: <20241008113344.23957-1-didi.debian@cknow.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Migadu-Flow: FLOW_OUT Content-Type: text/plain; charset="utf-8" The "synopsys,dw-hdmi.yaml" binding specifies that the interrupts property of the hdmi node has 'maxItems: 1', so the hdmi node in rk3328.dtsi having 2 is incorrect. Paragraph 1.3 ("System Interrupt connection") of the RK3328 TRM v1.1 page 16 and 17 define the following hdmi related interrupts: - 67 hdmi_intr - 103 hdmi_intr_wakeup The difference of 32 is due to a different base used in the TRM. The RK3399 (which uses the same binding) has '23: hdmi_irq' and '24: hdmi_wakeup_irq' according to its TRM (page 19). The RK3568 (also same binding) has '76: hdmi_wakeup' and '77: hdmi' according to page 17 of its TRM. In both cases the non-wakeup IRQ was used, so use that too for rk3328. Helped-by: Heiko Stuebner Fixes: 725e351c265a ("arm64: dts: rockchip: add rk3328 display nodes") Signed-off-by: Diederik de Haas --- changes in v2: - Added Fixes tag arch/arm64/boot/dts/rockchip/rk3328.dtsi | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi b/arch/arm64/boot/dts= /rockchip/rk3328.dtsi index b5cbe7cab10b..0597de415fe0 100644 --- a/arch/arm64/boot/dts/rockchip/rk3328.dtsi +++ b/arch/arm64/boot/dts/rockchip/rk3328.dtsi @@ -754,8 +754,7 @@ hdmi: hdmi@ff3c0000 { compatible =3D "rockchip,rk3328-dw-hdmi"; reg =3D <0x0 0xff3c0000 0x0 0x20000>; reg-io-width =3D <4>; - interrupts =3D , - ; + interrupts =3D ; clocks =3D <&cru PCLK_HDMI>, <&cru SCLK_HDMI_SFC>, <&cru SCLK_RTC32K>; --=20 2.45.2 From nobody Wed Nov 27 19:47:41 2024 Received: from out-182.mta0.migadu.com (out-182.mta0.migadu.com [91.218.175.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 83CDA1D8DFB for ; Tue, 8 Oct 2024 11:34:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.182 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728387272; cv=none; b=fJozr0zDD1OKOs0SBV7PNgszm2a95UikpK0ulyT/rQMr5liCy57l2vZ8a5cJDhj2hsKpNnM8h6TxLqJaJUM4wF9Dglb9bEFfM/ydowKyLRRjAt2udSu08s2eRD2py3hodl4q542w5GQw7Ncx/W6mubgE+K3BWVFTwlEABrXvsUU= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728387272; c=relaxed/simple; bh=wstrmXZPnSRywIg12QvRqavJaqofiwOLcd2XZmwLHT0=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=WHu19TFLKJwYi2mtHVqhdf9hO6WiaS3Z5ARub6MXzsLyg7AjH07rmqsdQS/DfTy0yLsrvVatUlPH2+4ptF0j7SH0r9SOYOownkEYj2b5gkzqkMESFj57EC93q/NFBAyFwCL+INR/RBqKBqg/c2wLsz/6CdD1sqvXeHOzQauNDZI= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=cknow.org; spf=pass smtp.mailfrom=cknow.org; dkim=pass (2048-bit key) header.d=cknow.org header.i=@cknow.org header.b=d51xGEii; arc=none smtp.client-ip=91.218.175.182 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=cknow.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=cknow.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=cknow.org header.i=@cknow.org header.b="d51xGEii" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cknow.org; s=key1; t=1728387268; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=kNxjNd6yrVtYzBsqUHl4cB5Rc4c+PEgl84/4jE5hQ1o=; b=d51xGEiiShgKMKwdlw+LhAZoNulcDjKyuK6LJMYI/xJvPYmnbpQRMzFHh2PvpuYhdX69MM LnsHWaFdVMgp17WzooASMZ+rBqzWnRcG0wmDnWOzKz1r7DFOeMvibOztovfiWdueS2g/yi 9URd2+OkF91KjDK4ZnrXPEqVFqQQtEWPYLtXeyuKRdo1SxTUEcGuxV+cBI3BJRsbXwY85O quWZdrsd+mo+jNSqVQr8UfaG7RoXssjI6KvnoRiE2OvMS61lnHDZvbkd1DZBNrvv1lcWZj LNOB6huoVfvVirxyoCfx0ToaRpH6J1a1ybK6KLWZbu7oVJnfAUeRkdx/WPYivA== From: Diederik de Haas To: Rob Herring , Krzysztof Kozlowski , Conor Dooley , Heiko Stuebner Cc: Diederik de Haas , Dragan Simic , Michael Riesch , Samuel Holland , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 3/4] arm64: dts: rockchip: Fix wakeup prop names on PineNote BT node Date: Tue, 8 Oct 2024 13:15:38 +0200 Message-ID: <20241008113344.23957-4-didi.debian@cknow.org> In-Reply-To: <20241008113344.23957-1-didi.debian@cknow.org> References: <20241008113344.23957-1-didi.debian@cknow.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Migadu-Flow: FLOW_OUT Content-Type: text/plain; charset="utf-8" The "brcm,bluetooth.yaml" binding has 'device-wakeup-gpios' and 'host-wakeup-gpios' property names, not '*-wake-gpios'. Fix the incorrect property names. Note that the "realtek,bluetooth.yaml" binding does use the '*-wake-gpios' property names. Fixes: d449121e5e8a ("arm64: dts: rockchip: Add Pine64 PineNote board") Signed-off-by: Diederik de Haas --- changes in v2: - Dropped change already covered by Heiko's patch; updated commit message accordingly - Added Fixes tag arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi b/arch/arm64= /boot/dts/rockchip/rk3566-pinenote.dtsi index de4c082dce07..7381bb751852 100644 --- a/arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi +++ b/arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi @@ -684,8 +684,8 @@ bluetooth { compatible =3D "brcm,bcm43438-bt"; clocks =3D <&rk817 1>; clock-names =3D "lpo"; - device-wake-gpios =3D <&gpio0 RK_PC2 GPIO_ACTIVE_HIGH>; - host-wake-gpios =3D <&gpio0 RK_PC3 GPIO_ACTIVE_HIGH>; + device-wakeup-gpios =3D <&gpio0 RK_PC2 GPIO_ACTIVE_HIGH>; + host-wakeup-gpios =3D <&gpio0 RK_PC3 GPIO_ACTIVE_HIGH>; reset-gpios =3D <&gpio0 RK_PC4 GPIO_ACTIVE_LOW>; pinctrl-0 =3D <&bt_enable_h>, <&bt_host_wake_l>, <&bt_wake_h>; pinctrl-names =3D "default"; --=20 2.45.2 From nobody Wed Nov 27 19:47:41 2024 Received: from out-189.mta0.migadu.com (out-189.mta0.migadu.com [91.218.175.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7F77E1917E5 for ; Tue, 8 Oct 2024 11:34:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.189 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728387278; cv=none; b=dE/aufE+SqlbH1GnNxHNgh1BenX4fgsS8enghVtUAd10gloGtIF1MYHqMP8Vd67IvOkDxMNBmcRVoar4hFbSsHOkoSZ2YBGWYooTjvekvJ4EB/Iwe1dpnLcjrg1jL66RA5N0sM70XHq4Uo8BScGhdllguY2eXA+Jn/aqApjfwS0= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728387278; c=relaxed/simple; bh=7rPn0Zhr1Au3miPuYWq6KKAiEVX5BjKq8teXQe1T2ds=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=JbmWXaBFDzgXU6FIc3g0Gsmt/iRkMOsDn0b5h2oJYy9FJwzyCuPssEYyFmp1mTM+UMSvFDCUf6bId69xkvUlNiE3i+L3viTQJYfNnmAdr2iiWHUCqUWLJZ0u08jmf8hvrZGFWDmodnQIhVDTSA7Ca2GbSV0T8vOcojMaWOk2w0o= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=cknow.org; spf=pass smtp.mailfrom=cknow.org; dkim=pass (2048-bit key) header.d=cknow.org header.i=@cknow.org header.b=Gih9R00N; arc=none smtp.client-ip=91.218.175.189 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=cknow.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=cknow.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=cknow.org header.i=@cknow.org header.b="Gih9R00N" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cknow.org; s=key1; t=1728387273; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=dKlqz7no2Q0t056MIy0/Nk83i3CyvmCGheL9X0Hx2a4=; b=Gih9R00ND98f9TxWntc7iICTyevgHbEJHne476iMNtuYR3DmO8m1rXXY2CM9F8xB0VAaSr 5m+uFIcE2deDLKvzy63wQ4Fn54thb3LPC0nvzHjmLreIpxVidW+Zsay+r3bkOTOg6EeEQV sHpTopbwjLFUYybAis2ixpUgJmqUSW7viIKDbJ4jbld5mZ8Sj70sPDPr0+2/h+5NEZovQG 8M4D0FBvCjqRoj5gIAB1/03yIJheWUK8O/hBGCqtBkpiOshbd+zF2PYd7X5sSzR9tMjLl2 Fdh2yNdjc/zdtyfvC7Kmtt4ZnL/J76TFm9oPE9iEX1raH3/Ltpr3jXJgUxzSsA== From: Diederik de Haas To: Rob Herring , Krzysztof Kozlowski , Conor Dooley , Heiko Stuebner Cc: Diederik de Haas , Dragan Simic , Michael Riesch , Samuel Holland , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 4/4] arm64: dts: rockchip: Fix reset-gpios property on brcm BT nodes Date: Tue, 8 Oct 2024 13:15:39 +0200 Message-ID: <20241008113344.23957-5-didi.debian@cknow.org> In-Reply-To: <20241008113344.23957-1-didi.debian@cknow.org> References: <20241008113344.23957-1-didi.debian@cknow.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Migadu-Flow: FLOW_OUT Content-Type: text/plain; charset="utf-8" For most compatibles, the "brcm,bluetooth.yaml" binding doesn't allow the 'reset-gpios' property, but there is a 'shutdown-gpios' property. Page 12 of the AzureWave-CM256SM datasheet (v1.9) has the following wrt pin 34 'BT_REG_ON' (connected to GPIO0_C4_d on the PineNote): Used by PMU to power up or power down the internal regulators used by the Bluetooth section. Also, when deasserted, this pin holds the Bluetooth section in reset. This pin has an internal 200k ohm pull down resistor that is enabled by default. So it is safe to replace 'reset-gpios' with 'shutdown-gpios'. Fixes: d449121e5e8a ("arm64: dts: rockchip: Add Pine64 PineNote board") Signed-off-by: Diederik de Haas --- changes in v2: - Extended commit message to explain why replacing 'reset' with 'shutdown' is safe - Added Fixes tag arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi | 2 +- arch/arm64/boot/dts/rockchip/rk3566-radxa-cm3.dtsi | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi b/arch/arm64= /boot/dts/rockchip/rk3566-pinenote.dtsi index 7381bb751852..100a2774bbb5 100644 --- a/arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi +++ b/arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi @@ -686,9 +686,9 @@ bluetooth { clock-names =3D "lpo"; device-wakeup-gpios =3D <&gpio0 RK_PC2 GPIO_ACTIVE_HIGH>; host-wakeup-gpios =3D <&gpio0 RK_PC3 GPIO_ACTIVE_HIGH>; - reset-gpios =3D <&gpio0 RK_PC4 GPIO_ACTIVE_LOW>; pinctrl-0 =3D <&bt_enable_h>, <&bt_host_wake_l>, <&bt_wake_h>; pinctrl-names =3D "default"; + shutdown-gpios =3D <&gpio0 RK_PC4 GPIO_ACTIVE_LOW>; vbat-supply =3D <&vcc_wl>; vddio-supply =3D <&vcca_1v8_pmu>; }; diff --git a/arch/arm64/boot/dts/rockchip/rk3566-radxa-cm3.dtsi b/arch/arm6= 4/boot/dts/rockchip/rk3566-radxa-cm3.dtsi index d09e6542e236..3e0cbfff96d8 100644 --- a/arch/arm64/boot/dts/rockchip/rk3566-radxa-cm3.dtsi +++ b/arch/arm64/boot/dts/rockchip/rk3566-radxa-cm3.dtsi @@ -402,9 +402,9 @@ bluetooth { clock-names =3D "lpo"; device-wakeup-gpios =3D <&gpio2 RK_PB2 GPIO_ACTIVE_HIGH>; host-wakeup-gpios =3D <&gpio2 RK_PB1 GPIO_ACTIVE_HIGH>; - reset-gpios =3D <&gpio2 RK_PC0 GPIO_ACTIVE_LOW>; pinctrl-names =3D "default"; pinctrl-0 =3D <&bt_host_wake_h &bt_reg_on_h &bt_wake_host_h>; + shutdown-gpios =3D <&gpio2 RK_PC0 GPIO_ACTIVE_LOW>; vbat-supply =3D <&vcc_3v3>; vddio-supply =3D <&vcc_1v8>; }; --=20 2.45.2