From mboxrd@z Thu Jan 1 00:00:00 1970 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=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no 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 77F57C3A5A4 for ; Fri, 30 Aug 2019 13:20:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 484AB2186A for ; Fri, 30 Aug 2019 13:20:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1567171244; bh=SK7MIU26ekdFufN9wFcNBBpMKeHmFfdUbjP+h2nZYvI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=ll3la+E0sSRDniyGzum1/5LBYTtacA4cK0mAxt3SAbUGpgyNQJAip3GmL4IiE8a2L 18FewWz2GVLaXu8o9L/EEd3zr3JW/3KfmqdnnwSu86hqIpiGNkzHH+/FM/G2UJ9LBA m9B7sUPszezwaR71YnG4DXaCkRg0lhusfqvT368o= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727792AbfH3NUi (ORCPT ); Fri, 30 Aug 2019 09:20:38 -0400 Received: from mail.kernel.org ([198.145.29.99]:32950 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727135AbfH3NUi (ORCPT ); Fri, 30 Aug 2019 09:20:38 -0400 Received: from localhost (lfbn-1-17395-211.w86-250.abo.wanadoo.fr [86.250.200.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9E0A72186A; Fri, 30 Aug 2019 13:20:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1567171237; bh=SK7MIU26ekdFufN9wFcNBBpMKeHmFfdUbjP+h2nZYvI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=kwwbxERsPTczwEsIdSPds2TKEG8g1kxDybF1PiA0Z0k+fDM25ivomVokZGGEPDksp V5RitlF0EmcbfhMrs9eRJRJvkJNLgEqIMUh1urS042x+/5RNzhWrXyLQOLdO8LwvzU U8zyEwOecd8CSGBUqh2E+L94YyODq2KLxmWw6Pco= Date: Fri, 30 Aug 2019 15:20:34 +0200 From: Maxime Ripard To: Marcel Holtmann Cc: megous@megous.com, Chen-Yu Tsai , Rob Herring , Johan Hedberg , Mark Rutland , "David S. Miller" , netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-bluetooth@vger.kernel.org Subject: Re: [RESEND PATCH 0/5] Add bluetooth support for Orange Pi 3 Message-ID: <20190830132034.u65arlv7umh64lx6@flea> References: <20190823103139.17687-1-megous@megous.com> <5524D5E9-FA82-4244-A91F-78CF1C3FB3FB@holtmann.org> <20190830092104.odipmbflounqpffo@flea> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org On Fri, Aug 30, 2019 at 02:43:48PM +0200, Marcel Holtmann wrote: > >>> (Resend to add missing lists, sorry for the noise.) > >>> > >>> This series implements bluetooth support for Xunlong Orange Pi 3 board. > >>> > >>> The board uses AP6256 WiFi/BT 5.0 chip. > >>> > >>> Summary of changes: > >>> > >>> - add more delay to let initialize the chip > >>> - let the kernel detect firmware file path > >>> - add new compatible and update dt-bindings > >>> - update Orange Pi 3 / H6 DTS > >>> > >>> Please take a look. > >>> > >>> thank you and regards, > >>> Ondrej Jirman > >>> > >>> Ondrej Jirman (5): > >>> dt-bindings: net: Add compatible for BCM4345C5 bluetooth device > >>> bluetooth: bcm: Add support for loading firmware for BCM4345C5 > >>> bluetooth: hci_bcm: Give more time to come out of reset > >>> arm64: dts: allwinner: h6: Add pin configs for uart1 > >>> arm64: dts: allwinner: orange-pi-3: Enable UART1 / Bluetooth > >>> > >>> .../bindings/net/broadcom-bluetooth.txt | 1 + > >>> .../dts/allwinner/sun50i-h6-orangepi-3.dts | 19 +++++++++++++++++++ > >>> arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi | 10 ++++++++++ > >>> drivers/bluetooth/btbcm.c | 3 +++ > >>> drivers/bluetooth/hci_bcm.c | 3 ++- > >>> 5 files changed, 35 insertions(+), 1 deletion(-) > >> > >> all 5 patches have been applied to bluetooth-next tree. > > > > The DTS patches (last 2) should go through the arm-soc tree, can you > > drop them? > > why is that? We have included DTS changes for Bluetooth devices > directly all the time. What is different with this hardware? I guess some maintainers are more relaxed with it than we are then, but for the why, well, it's the usual reasons, the most immediate one being that it reduces to a minimum the conflicts between trees. The other being that it's not really usual to merge patches supposed to be handled by another maintainer without (at least) his consent. I'm pretty sure you would have asked the same request if I would have merged the bluetooth patches through my tree without notice. Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com