Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp125314imb; Thu, 28 Feb 2019 18:15:44 -0800 (PST) X-Google-Smtp-Source: APXvYqzFJOuMMr5FIBLNbqWwZ8CU0UuNiRcEkRQpuVU/EVa1IAIh0nfv2rqIYtWOPUCylB9I3uaV X-Received: by 2002:a63:6a08:: with SMTP id f8mr2422641pgc.165.1551406544065; Thu, 28 Feb 2019 18:15:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551406544; cv=none; d=google.com; s=arc-20160816; b=G/3ypizcocYrwniNEdPCrZ/pzfIH13P+3eKjmVCxXpZumZwq4zz49gku/ilZ3NEm1o +gRjo+5jDcmXtbvSaGxS+EKV9ibdy47cYpWjVBxmjJNAEapvGtISTdrYATrzvwx/NaSr MFl/GpHIBW7S6ye65/DcFG6NxO3fx/uA62DXZTVlCHDNtPmmOzXir77SCQfNDJis9r8F iIupvcQRxFc6Z1JhNSNj2VWFoF+IcO02MQtZQNC0JhitUy+hD+dJLTdpRRoB71bp/jZB sfVNuwDFOsbx7FWAIGLTls2AyXYrB1l9pgsBLGPcXq8x/Cpuy2THN8IDwhnehzmhmnu6 nj2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from; bh=7QQ2Q5JKlkvGNa7xvDr3rYufaJnbBLIWdS8TEYk7Hog=; b=aDJnHPBjJ249WcJb6wAJUBfssZAEIvwEvg8oHOCLG1yl2rTZynODc9lMuJsvfVqseg MwQTvL+ZA40XjNk8mN9OZgJh9/UyuJmk+/epP1b8dYuRPBJuhUAdebFyeaqXlJTuFgXY /T51ldd9oKteZldLe81z/CblgqoE/rM5KoeRTlQt+6/6lgm3kYWARn26fwIGy1wfs7BH sz6lEf9zlurTfQQcrOflDYySlo2HQlprYkGWUKiMuQPofxOzajn70eDYHJasEPR+suGo FUlcHXmizvG/DRDHKUyazws1B0O71mmbFmsZLlbERDt2iOqVMTTr3E+YxaU5AHdKWjg2 SNkA== 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 i3si18636389plt.120.2019.02.28.18.15.28; Thu, 28 Feb 2019 18:15:44 -0800 (PST) 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 S1730742AbfCACOZ (ORCPT + 99 others); Thu, 28 Feb 2019 21:14:25 -0500 Received: from mailgw02.mediatek.com ([210.61.82.184]:41670 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1725896AbfCACOY (ORCPT ); Thu, 28 Feb 2019 21:14:24 -0500 X-UUID: 0318acd61d9b4d9296986d1fdbb00a07-20190301 X-UUID: 0318acd61d9b4d9296986d1fdbb00a07-20190301 Received: from mtkmrs01.mediatek.inc [(172.21.131.159)] by mailgw02.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 97358672; Fri, 01 Mar 2019 10:14:18 +0800 Received: from mtkcas08.mediatek.inc (172.21.101.126) by mtkmbs01n2.mediatek.inc (172.21.101.79) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 1 Mar 2019 10:14:10 +0800 Received: from mtkswgap22.mediatek.inc (172.21.77.33) by mtkcas08.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Fri, 1 Mar 2019 10:14:10 +0800 From: To: , , , CC: , , , , , Sean Wang Subject: [PATCH v2 1/2] dt-bindings: net: bluetooth: add support for MediaTek MT7663U and MT7668U UART devices Date: Fri, 1 Mar 2019 10:14:07 +0800 Message-ID: <937e729bab743a5e1c0f74db789064de2d078241.1551405664.git.sean.wang@mediatek.com> X-Mailer: git-send-email 1.7.9.5 In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain X-TM-SNTS-SMTP: E4A479C784B4D73BCF107209ED08A0004351E035A710CF03884C6DB4DB123B1D2000:8 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Sean Wang Update binding document with adding support of MT7663U and MT7668U UART devices to mediatek-bluetooth. Reviewed-by: Rob Herring Signed-off-by: Sean Wang --- .../bindings/net/mediatek-bluetooth.txt | 64 +++++++++++++++++++ 1 file changed, 64 insertions(+) diff --git a/Documentation/devicetree/bindings/net/mediatek-bluetooth.txt b/Documentation/devicetree/bindings/net/mediatek-bluetooth.txt index 14ceb2a5b4e8..41a7dcc80f5b 100644 --- a/Documentation/devicetree/bindings/net/mediatek-bluetooth.txt +++ b/Documentation/devicetree/bindings/net/mediatek-bluetooth.txt @@ -33,3 +33,67 @@ Example: clock-names = "ref"; }; }; + +MediaTek UART based Bluetooth Devices +================================== + +This device is a serial attached device to UART device and thus it must be a +child node of the serial node with UART. + +Please refer to the following documents for generic properties: + + Documentation/devicetree/bindings/serial/slave-device.txt + +Required properties: + +- compatible: Must be + "mediatek,mt7663u-bluetooth": for MT7663U device + "mediatek,mt7668u-bluetooth": for MT7668U device +- vcc-supply: Main voltage regulator +- pinctrl-names: Should be "default", "runtime" +- pinctrl-0: Should contain UART RXD low when the device is powered up to + enter proper bootstrap mode. +- pinctrl-1: Should contain UART mode pin ctrl + +Optional properties: + +- reset-gpios: GPIO used to reset the device whose initial state keeps low, + if the GPIO is missing, then board-level design should be + guaranteed. +- current-speed: Current baud rate of the device whose defaults to 921600 + +Example: + + uart1_pins_boot: uart1-default { + pins-dat { + pinmux = ; + output-low; + }; + }; + + uart1_pins_runtime: uart1-runtime { + pins-dat { + pinmux = , + ; + }; + }; + + uart1: serial@11003000 { + compatible = "mediatek,mt7623-uart", + "mediatek,mt6577-uart"; + reg = <0 0x11003000 0 0x400>; + interrupts = ; + clocks = <&pericfg CLK_PERI_UART1_SEL>, + <&pericfg CLK_PERI_UART1>; + clock-names = "baud", "bus"; + + bluetooth { + compatible = "mediatek,mt7663u-bluetooth"; + vcc-supply = <®_5v>; + reset-gpios = <&pio 24 GPIO_ACTIVE_LOW>; + pinctrl-names = "default", "runtime"; + pinctrl-0 = <&uart1_pins_boot>; + pinctrl-1 = <&uart1_pins_runtime>; + current-speed = <921600>; + }; + }; -- 2.18.0