Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp7232076yba; Thu, 2 May 2019 06:35:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqz8CjKDaqwuyAn9D5hazVdEwenQxHXBXxM+DpFmU43L/SjG3fK4lI9A7WWaM3OORRXeBh+7 X-Received: by 2002:a62:5707:: with SMTP id l7mr4322170pfb.205.1556804124468; Thu, 02 May 2019 06:35:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556804124; cv=none; d=google.com; s=arc-20160816; b=wipxwq//C8e1Nyks1PoMlCxdy8J04oXX6N7DbJ+cGsTfvL6DSPtDho7d/7Tv3pobKb 3voYWda60g50YVSZrichQcSK/vb2p5bkCN8UYNzMA6IBuoZRi40svUZOucu/+/+PxgDP quRk/kE78wLHtKlitZRsXSCszaXzPnXGepLZHxbhc3tIH5DOPk8186RXmUzRfAz9tya+ 8M3j2OvQSos+FSK/60GyXaU3gciedFAQJuGIZNnIBxkHp3uXCv5qe63YUXSEZQ6SrxEY jnl0n0GCCzIqrUriex6qDDkHE+eiG9511gcNAIQi2I6mkcwByiOLTBlnCzD0guuvIwVy BjSw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from; bh=TbiL2qx5o+RHdahiwftkHusB+axDXcTZslLqwWY89/0=; b=YawUX5DUpcQjAT7ISzlBkH88ar4VTIuYlEsEAM7sh3i6BKf1U3X7BLtzD5oUK0qGHC nHX/Pug0gbF47Q52y6j1ygHWD45Z81xEu4Xb5RH2/lGCMSeXCnwBDpQWLZtlVDDKoW8+ HC1enZ8sAwIxDgx2p7VVvC6GQSW6GqlIKIhr1g2B8rilvvDBcDAyxyISQjg7C/6WRyxp eWi4ftbBatK9RL2nXkD8bSri5CV+B9ZWjk1C3+PWO7Pd0aJ3TLILezq7EX+wIL6bhs/N ovW8oD3ZZVlfYTFQMFYUPXzU2bI/RT1KdQDFbEnkNbv8NsKTdiaiZ0MgNX8b0x9MmFQv n8QQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g132si40483036pfc.260.2019.05.02.06.35.07; Thu, 02 May 2019 06:35:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726482AbfEBNeN (ORCPT + 99 others); Thu, 2 May 2019 09:34:13 -0400 Received: from mail2.sp2max.com.br ([138.185.4.9]:45894 "EHLO mail2.sp2max.com.br" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726399AbfEBNeJ (ORCPT ); Thu, 2 May 2019 09:34:09 -0400 Received: from pgsop.sopnet.com.ar (unknown [179.40.38.12]) (Authenticated sender: pablo@fliagreco.com.ar) by mail2.sp2max.com.br (Postfix) with ESMTPA id 0C86B7B3003; Thu, 2 May 2019 10:34:04 -0300 (-03) From: Pablo Greco To: linux-sunxi@googlegroups.com Cc: Pablo Greco , Rob Herring , Mark Rutland , Maxime Ripard , Chen-Yu Tsai , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH v6 5/5] ARM: dts: sun8i: v40: bananapi-m2-berry: Add Bluetooth device node Date: Thu, 2 May 2019 10:33:49 -0300 Message-Id: <1556804030-25291-6-git-send-email-pgreco@centosproject.org> X-Mailer: git-send-email 1.8.3.1 In-Reply-To: <1556804030-25291-1-git-send-email-pgreco@centosproject.org> References: <1556804030-25291-1-git-send-email-pgreco@centosproject.org> X-SP2Max-MailScanner-Information: Please contact the ISP for more information X-SP2Max-MailScanner-ID: 0C86B7B3003.A6140 X-SP2Max-MailScanner: Sem Virus encontrado X-SP2Max-MailScanner-SpamCheck: nao spam, SpamAssassin (not cached, escore=-2.9, requerido 6, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90) X-SP2Max-MailScanner-From: pgreco@centosproject.org X-Spam-Status: No Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The AP6212 is based on the Broadcom BCM43430 or BCM43438. The WiFi side identifies as BCM43430, while the Bluetooth side identifies as BCM43438. The Bluetooth side is connected to UART3 in a 4 wire configuration. Same as the WiFi side, due to being the same chip and package, DLDO1 and DLDO2 regulator outputs from the PMIC provide overall power via VBAT and I/O power via VDDIO. The CLK_OUT_A clock output from the SoC provides the LPO low power clock at 32.768 kHz. This patch enables Bluetooth on this board, and also adds the missing LPO clock on the WiFi side. There is also a PCM connection for Bluetooth, but this is not covered here. The LPO clock is fed from CLK_OUT_A, which needs to be muxed on pin PI12. This can be represented in multiple ways. This patch puts the pinctrl property in the pin controller node. This is due to limitations in Linux, where pinmux settings, even the same one, can not be shared by multiple devices. Thus we cannot put it in both the WiFi and Bluetooth device nodes. Putting it the CCU node is another option, but Linux's CCU driver does not handle pinctrl. Also the pin controller is guaranteed to be initialized after the CCU, when clocks are available. And any other devices that use muxed pins are guaranteed to be initialized after the pin controller. Thus having the CLK_OUT_A pinmux reference be in the pin controller node is a good choice without having to deal with implementation issues. Signed-off-by: Pablo Greco --- arch/arm/boot/dts/sun8i-v40-bananapi-m2-berry.dts | 38 +++++++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/arch/arm/boot/dts/sun8i-v40-bananapi-m2-berry.dts b/arch/arm/boot/dts/sun8i-v40-bananapi-m2-berry.dts index 461683c..15c22b0 100644 --- a/arch/arm/boot/dts/sun8i-v40-bananapi-m2-berry.dts +++ b/arch/arm/boot/dts/sun8i-v40-bananapi-m2-berry.dts @@ -96,6 +96,8 @@ wifi_pwrseq: wifi_pwrseq { compatible = "mmc-pwrseq-simple"; reset-gpios = <&pio 6 10 GPIO_ACTIVE_LOW>; /* PG10 WIFI_EN */ + clocks = <&ccu CLK_OUTA>; + clock-names = "ext_clock"; }; }; @@ -172,6 +174,8 @@ }; &pio { + pinctrl-names = "default"; + pinctrl-0 = <&clk_out_a_pin>; vcc-pa-supply = <®_aldo2>; vcc-pc-supply = <®_dcdc1>; vcc-pd-supply = <®_dcdc1>; @@ -233,12 +237,27 @@ regulator-name = "vcc-wifi-io"; }; +/* + * Our WiFi chip needs both DLDO2 and DLDO3 to be powered at the same + * time, with the two being in sync, to be able to meet maximum power + * consumption during transmits. Since this is not really supported + * right now, just use the two as always on, and we will fix it later. + */ + ®_dldo2 { + regulator-always-on; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-name = "vcc-wifi"; }; +®_dldo3 { + regulator-always-on; + regulator-min-microvolt = <3300000>; + regulator-max-microvolt = <3300000>; + regulator-name = "vcc-wifi-2"; +}; + ®_dldo4 { regulator-min-microvolt = <2500000>; regulator-max-microvolt = <2500000>; @@ -261,6 +280,25 @@ status = "okay"; }; +&uart3 { + pinctrl-names = "default"; + pinctrl-0 = <&uart3_pg_pins>, <&uart3_rts_cts_pg_pins>; + uart-has-rtscts; + status = "okay"; + + bluetooth { + compatible = "brcm,bcm43438-bt"; + clocks = <&ccu CLK_OUTA>; + clock-names = "lpo"; + vbat-supply = <®_dldo2>; + vddio-supply = <®_dldo1>; + device-wakeup-gpios = <&pio 6 11 GPIO_ACTIVE_HIGH>; /* PG11 */ + /* TODO host wake line connected to PMIC GPIO pins */ + shutdown-gpios = <&pio 7 12 GPIO_ACTIVE_HIGH>; /* PH12 */ + max-speed = <1500000>; + }; +}; + &usbphy { usb1_vbus-supply = <®_vcc5v0>; status = "okay"; -- 1.8.3.1