Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3993593imj; Tue, 19 Feb 2019 13:14:12 -0800 (PST) X-Google-Smtp-Source: AHgI3IZsMGosCK3cTg5BONoHTb6Qw5wTDq+yiFs5RUcJsyPQNwj4bT+NOZ2amkcI3t8pWfs/zTvo X-Received: by 2002:a63:f844:: with SMTP id v4mr25506919pgj.82.1550610852087; Tue, 19 Feb 2019 13:14:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550610852; cv=none; d=google.com; s=arc-20160816; b=wdc7ANjdrOKlkdLTsJtJVTIJudPICFSDnAuTuzRBIvXaLzlJo8f+QZlFUZ+40XQFj6 aqb/srImSTvpzWWgTYLLS0DQL/vlJkHPwMVAPXbr2bGypOouGYGkwcjYE8uiVAAFQsEr pgFaSUgkp0tWIjU3sO3ZU9KNOSfM/D/C1GNmPYblBsd9gTsEoh7ikEeSWtaf6y3TUPH2 HcBGpiCvdKwE5yMK4/LXPtlSSgDNDBI7pEou/Lbv+ymRoSLrOzxRt06RCHRtbwzwttTS ivlGQ31lRuwBlWraki16oxJUm5M9FRzHJZbdLQAL/xBEWqbLamTDozur+sxqcfxIfMgB JkEg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :references:in-reply-to:date:cc:to:from:subject:message-id; bh=fX2wW8Y3kmoOChZE6gw2iq5VFoVbC3+CZQPqMmmA+ew=; b=Z80u43w9FGOYYzbBkdCSm0VWxTmz8RtV9iUT6bHbaJTvazSNpjh4syjm3A2I8gaUkJ urDUrHewYURpniC6mM8BI6WPXAqraZwkCL3/VyT2VbCU8uxUk8pV/lsksgu3xgTZMDll QIlIgfTg8McV/Vm8eOo7C9zZCDWnw54AC5Fkw8zlfJLa3VrJ5bV4XvoLMBw+FLttnIzr JfajDRCOOJvaCD5uS3fs9Vwxoi3m23VBTS2q+FRFp6VWAQ1PSu/1TxMySu0qRW6mG5z+ W5gANODWghrQLlowg7U+O4cM6Lgeb2NK4ppwscK4DpCvQVsKIusWiUbenztvSM4L9BJ+ 4q5g== 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 x1si12362774plr.439.2019.02.19.13.13.56; Tue, 19 Feb 2019 13:14:12 -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 S1727206AbfBSVNf (ORCPT + 99 others); Tue, 19 Feb 2019 16:13:35 -0500 Received: from mailgw02.mediatek.com ([210.61.82.184]:28115 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1725829AbfBSVNf (ORCPT ); Tue, 19 Feb 2019 16:13:35 -0500 X-UUID: c147d20144254d9da419c9643ce8f7e5-20190220 X-UUID: c147d20144254d9da419c9643ce8f7e5-20190220 Received: from mtkcas06.mediatek.inc [(172.21.101.30)] by mailgw02.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 1704607133; Wed, 20 Feb 2019 05:13:24 +0800 Received: from mtkcas07.mediatek.inc (172.21.101.84) by mtkmbs03n2.mediatek.inc (172.21.101.182) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 20 Feb 2019 05:13:22 +0800 Received: from [172.21.77.33] (172.21.77.33) by mtkcas07.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Wed, 20 Feb 2019 05:13:22 +0800 Message-ID: <1550610802.8245.1.camel@mtkswgap22> Subject: Re: [PATCH 0/6]Bluetooth: mediatek: add support for MediaTek MT7663U and MT7668U UART devices From: Sean Wang To: Marcel Holtmann CC: , , Johan Hedberg , , , , , Date: Wed, 20 Feb 2019 05:13:22 +0800 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-TM-SNTS-SMTP: 98A3CAF5D64E85FAF0BAE40E263515CF4456794E36B4038D6C812BCE94E377172000:8 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Marcel, I will follow it up. Thank for your help! Sean On Mon, 2019-02-18 at 14:10 +0100, Marcel Holtmann wrote: > Hi Sean, > > > This adds the support of enabling MT7668U and MT7663U UART based Bluetooth > > function running on the top of btmtkuart driver. > > > > We are through several patches to reach the goal and also wish applied > > the same flow in MediaTek btusb [1] for the transport independence. > > Once [1] and the series is being merged and then in next step I will > > consider to add a btmtk.c to hold these independent operations among > > various transport reused by MediaTek UART, USB and SDIO-based Bluetooth. > > > > Firstly, > > in patch 1/6 to update the dt-binding document for the kind of devices. > > in patch 2/6, 3/6 to fix the common error issues in the current code. > > in Patch 4/6, 5/6 to add the general flow which MT7622 and even MT7663U and > > MT7668U USB devices also utilize. > > > > Finally, in patch 6/6 to add the specific setups for MediaTek UART-based > > Bluetooth and enable MT7663U and MT7668U device. > > > > [1] http://lists.infradead.org/pipermail/linux-mediatek/2019-January/017074.html > > > > Sean Wang (6): > > dt-bindings: net: bluetooth: add support for MediaTek MT7663U and > > MT7668U UART devices > > Bluetooth: mediatek: trivial typo fix > > Bluetooth: mediatek: fix up an error path to restore bdev->tx_state > > Bluetooth: mediatek: pass a pointer to mtk_hci_wmt_sync > > Bluetooth: mediatek: update the common setup between MT7622 and other > > devices > > Bluetooth: mediatek: add support for MediaTek MT7663U and MT7668U UART > > devices > > > > .../bindings/net/mediatek-bluetooth.txt | 64 +++ > > drivers/bluetooth/btmtkuart.c | 538 ++++++++++++++++-- > > 2 files changed, 569 insertions(+), 33 deletions(-) > > please re-send 1/6 and 6/6 when the DT changes are ACKed by Rob. > > Regards > > Marcel >