Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AA3D2C4360F for ; Wed, 20 Feb 2019 03:00:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7E76421738 for ; Wed, 20 Feb 2019 03:00:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730011AbfBTDAF (ORCPT ); Tue, 19 Feb 2019 22:00:05 -0500 Received: from mail-ed1-f67.google.com ([209.85.208.67]:42304 "EHLO mail-ed1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725616AbfBTDAF (ORCPT ); Tue, 19 Feb 2019 22:00:05 -0500 Received: by mail-ed1-f67.google.com with SMTP id j89so9211571edb.9; Tue, 19 Feb 2019 19:00:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kx6Mv5hmjbEtG9ehmh0BjC1fToEGSWVIZ3eqHBq3bns=; b=FwFMklJMOMNi6t4uQNRCZaYqln8bsvNcBlvVhuD736oFPRevmtSq4G2LM1ybl1zyxq invsVoQDpjn7a49M/LX3qZ5NEGad6cshdFtWiwpkD6MynfaTixZqL7FDQtsODnKgCfBD EE8D9y/KaZV67AOzs4z4psRNiwXXUmriX2qC16DJPrgtRykX5iouOe3JxxkOxmifUqa4 XGR4g7AOj1/lX/3x3jWyj7CziBqfSn+MTETVg6TNi+pm45nCW5PYbXmVgCzm99Oykekc pQU9Qnd+IstXbLqTjCgz3FNnYzG7v3lSqNP61kli18sHrQfmT663aCu0CqcpWPY5h/Cd lgIg== X-Gm-Message-State: AHQUAuZQMyF1izw24L+hToNSfVdHxiJemc1ADp6yLQBZxyMRnoTB2Fnb 7Ay4Nh/q6xGoWNZkIvBWB4iJQp4h2LA= X-Google-Smtp-Source: AHgI3IauzMr1bfTrnDseHNMfYdl0TEi6uCCfKJuQWCiCzFibkCtBDAqzOTPO++o9YaMcvCqkK8QtYA== X-Received: by 2002:a17:906:e9cc:: with SMTP id kb12mr722578ejb.81.1550631602269; Tue, 19 Feb 2019 19:00:02 -0800 (PST) Received: from mail-wm1-f45.google.com (mail-wm1-f45.google.com. [209.85.128.45]) by smtp.gmail.com with ESMTPSA id b11sm5332975eds.68.2019.02.19.18.59.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Feb 2019 19:00:00 -0800 (PST) Received: by mail-wm1-f45.google.com with SMTP id h22so3629942wmb.0; Tue, 19 Feb 2019 18:59:59 -0800 (PST) X-Received: by 2002:a1c:4c08:: with SMTP id z8mr4337333wmf.99.1550631599174; Tue, 19 Feb 2019 18:59:59 -0800 (PST) MIME-Version: 1.0 References: <20190118170232.16142-1-anarsoul@gmail.com> <20190118170232.16142-4-anarsoul@gmail.com> <20190218211035.GA28145@bogus> <1245842044.588056.1550527701604@email.ionos.de> <6a26ff97-0b9c-cfdd-9428-74580694220a@davidjohnsummers.uk> In-Reply-To: <6a26ff97-0b9c-cfdd-9428-74580694220a@davidjohnsummers.uk> From: Chen-Yu Tsai Date: Wed, 20 Feb 2019 10:59:49 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 3/8] dt-bindings: net: bluetooth: Add rtl8723bs-bluetooth To: David Summers Cc: Rob Herring , Vasily Khoruzhick , Stefan Wahren , Mark Rutland , devicetree , Johan Hedberg , Maxime Ripard , netdev , Marcel Holtmann , "open list:BLUETOOTH DRIVERS" , "David S. Miller" , arm-linux Content-Type: text/plain; charset="UTF-8" Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org On Wed, Feb 20, 2019 at 5:09 AM David Summers wrote: > > On 19/02/2019 14:17, Rob Herring wrote: > > On Mon, Feb 18, 2019 at 4:28 PM Vasily Khoruzhick wrote: > >> On Mon, Feb 18, 2019 at 2:08 PM Stefan Wahren wrote: > >>> Hi Vasily, > >> Hi Stefan, > >> > >>>> Vasily Khoruzhick hat am 18. Februar 2019 um 22:24 geschrieben: > >>>> > >>>> > >>>> On Mon, Feb 18, 2019 at 1:10 PM Rob Herring wrote: > >>>>> On Fri, Jan 18, 2019 at 09:02:27AM -0800, Vasily Khoruzhick wrote: > >>>>>> Add binding document for bluetooth part of RTL8723BS/RTL8723CS > >>>>>> > >>>>>> Signed-off-by: Vasily Khoruzhick > >>>>>> --- > >>>>>> .../bindings/net/rtl8723bs-bluetooth.txt | 35 +++++++++++++++++++ > >>>>>> 1 file changed, 35 insertions(+) > >>>>>> create mode 100644 Documentation/devicetree/bindings/net/rtl8723bs-bluetooth.txt > >>>>>> > >>>>>> diff --git a/Documentation/devicetree/bindings/net/rtl8723bs-bluetooth.txt b/Documentation/devicetree/bindings/net/rtl8723bs-bluetooth.txt > >>>>>> new file mode 100644 > >>>>>> index 000000000000..8357f242ae4c > >>>>>> --- /dev/null > >>>>>> +++ b/Documentation/devicetree/bindings/net/rtl8723bs-bluetooth.txt > >>>>>> @@ -0,0 +1,35 @@ > >>>>>> +RTL8723BS/RTL8723CS Bluetooth > >>>>>> +--------------------- > >>>>>> + > >>>>>> +RTL8723CS/RTL8723CS is WiFi + BT chip. WiFi part is connected over SDIO, while > >>>>>> +BT is connected over serial. It speaks H5 protocol with few extra commands > >>>>>> +to upload firmware and change module speed. > >>>>>> + > >>>>>> +Required properties: > >>>>>> + > >>>>>> + - compatible: should be one of the following: > >>>>>> + * "realtek,rtl8723bs-bt" > >>>>>> + * "realtek,rtl8723cs-bt" > >>>>>> +Optional properties: > >>>>>> + > >>>>>> + - device-wake-gpios: GPIO specifier, used to wakeup the BT module (active high) > >>>>>> + - enable-gpios: GPIO specifier, used to enable the BT module (active high) > >>>>>> + - host-wake-gpios: GPIO specifier, used to wakeup the host processor (active high) > >>>>>> + - firmware-postfix: firmware postfix to be used for firmware config > >>> sorry, i didn't noticed your great series before. David and i working at the same stuff but for the Asus Tinker Board. > >>> > >>> I created a similiar yet untested patch version for hci_h5 [1]. Maybe it's useful. > >> Looks good to me, but you may need to add firmware-postfix. > >> > >>> Just a comment about the binding. It's really necessary to add the reset-gpio? Can't we use the enable-gpio with inverse polarity for this? > >> Yes, we can use enable-gpio instead of reset-gpio on pine64 and pinebook. > > Then why do we have both? Reset and enable are distinct. The inverse > > of enable-gpios is typically powerdown-gpios, not reset-gpios. > > > > Rob > > Both data sheets that I know: > > http://cit.odessa.ua/media/pdf/Intel-Compute-Stick/FN-Link_F23BDSM25-W1.pdf > http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf > > BT_RST_N BT Reset IN / BT_DIS# General Purpose I/O Pin > > So from the datasheet there is only one pin. And from its name it sounds > like reset. Yes there's only one pin. Would be nice if we could use "enable" though. That is what ACPI uses. > This said though the datasheets of these Realtek devices are a bit thin .... These datasheets are for the integrated modules (the chip plus passive components). I don't think the datasheet for the chip itself is public. ChenYu