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=-3.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT 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 6E847C432C3 for ; Wed, 27 Nov 2019 22:39:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 449122176D for ; Wed, 27 Nov 2019 22:39:26 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="SFs22QNC" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727217AbfK0WjU (ORCPT ); Wed, 27 Nov 2019 17:39:20 -0500 Received: from mail-pf1-f195.google.com ([209.85.210.195]:41814 "EHLO mail-pf1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726947AbfK0WjU (ORCPT ); Wed, 27 Nov 2019 17:39:20 -0500 Received: by mail-pf1-f195.google.com with SMTP id s18so3348449pfd.8 for ; Wed, 27 Nov 2019 14:39:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=EHVbHRnSyLZIvpQSJdKBuo3vPPZlfvB1a4T9xCgdTuw=; b=SFs22QNC5hMmqvZPW40mcmcBBPmEpdsOtYsMagwY9mLUglW4JRbrQ2P/YfKX6icomt NLkRrpV4fVV4DqFWxY2+o1sPGR5wSnEhGfUZ7IaeX0l4QG1cLky+X1vAO9Oe3Z1+jozY 3Fc0j+mCHcHt0e2uOj7TE4FtHTgCkuVdKYlXI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=EHVbHRnSyLZIvpQSJdKBuo3vPPZlfvB1a4T9xCgdTuw=; b=HYXbUFdccVd/DGCC6JiHcJlnTyGFTTcF8hyWReP9wnaXSpR8PdEk90OSCuv0D1Awob Kfg8vL5MJbHbg30FtwHiyxNKiMBNJOwzk4xDxhHNiPY8xgr791YQGyE7d9CyEIZ/4Xt4 wWS0aOwpKTDQ5P2g0CWh3V7EFyD559plVyElN7wyLvhjaW+ex0YDhnGEKZua7UL3HW1U YkXh/PiYPpzbfkyREholv7xa6GmqEBmluMq0IwXMKqxYyNDriFBMHT4FxDdZYlua3ZFP QbjMOgxUn4P+96Zjz22m2GD+ruobffRvw2RYZ2tRPsnjOlu4KTpE1XOEhi/C3M0IcOBB 6+2A== X-Gm-Message-State: APjAAAUvGERibnn5zN3eyRJYPfe+bNzt5Mxw7MCw7IVEiWllW/0pyu+S +IV1akBdwC0OGjTQrit2CWKZ6Q== X-Google-Smtp-Source: APXvYqzJpOpejjYn146jmpkBi176AhZDdn7NcHNIXMFDPoF5M4picmxeNcIUsNSjUqkWCk7fHfCosw== X-Received: by 2002:a63:1e47:: with SMTP id p7mr230935pgm.339.1574894358017; Wed, 27 Nov 2019 14:39:18 -0800 (PST) Received: from apsdesk.mtv.corp.google.com ([2620:15c:202:1:e09a:8d06:a338:aafb]) by smtp.gmail.com with ESMTPSA id d6sm17699992pfn.32.2019.11.27.14.39.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Nov 2019 14:39:17 -0800 (PST) From: Abhishek Pandit-Subedi To: Heiko Stuebner , dianders@chromium.org Cc: linux-bluetooth@vger.kernel.org, linux-rockchip@lists.infradead.org, Abhishek Pandit-Subedi , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Rob Herring , Mark Rutland , linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 0/1] ARM: dts: rockchip: Add brcm bluetooth for rk3288-veyron Date: Wed, 27 Nov 2019 14:39:08 -0800 Message-Id: <20191127223909.253873-1-abhishekpandit@chromium.org> X-Mailer: git-send-email 2.24.0.432.g9d3f5f5b63-goog MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Hi Heiko, The necessary patches for this change have been merged into bluetooth-next. Please pick this up at your convenience. This patch enables using the Broadcom HCI UART driver with the BCM43540 Wi-Fi + Bluetooth chip. This chip is used on a RK3288 based board (Veyron) and these changes have been tested on the Minnie variant of the board (i.e. rk3288-veyron-minnie.dts). The changes are applicable to the minnie, mickey, speedy and brain variants (all of which use the Broadcom chips). The bt-activity node was removed for all Veyron boards and shouldn't affect the boards using Marvell chips since they aren't using this out-of-band wakeup gpio. A previous portion of this series adding the compatible string to the hci_bcm driver has already been merged into bluetooth-next: https://lore.kernel.org/r/4680AA6A-599F-4D5E-9A96-0655569BAE94@holtmann.org Another patch series to fix up the baudrate settings and configure the PCM parameters has meen merged on bluetooth-next: https://lore.kernel.org/linux-bluetooth/20191127071105.GA32820@akivisil-mobl1.ger.corp.intel.com/T/#t Thanks Abhishek Changes in v2: - Changed sco routing params to brcm,bt-pcm-int-params Abhishek Pandit-Subedi (1): ARM: dts: rockchip: Add brcm bluetooth for rk3288-veyron arch/arm/boot/dts/rk3288-veyron-brain.dts | 9 +++ .../dts/rk3288-veyron-broadcom-bluetooth.dtsi | 22 +++++++ .../boot/dts/rk3288-veyron-chromebook.dtsi | 21 ------- arch/arm/boot/dts/rk3288-veyron-fievel.dts | 2 - arch/arm/boot/dts/rk3288-veyron-jaq.dts | 22 +++++++ arch/arm/boot/dts/rk3288-veyron-jerry.dts | 22 +++++++ arch/arm/boot/dts/rk3288-veyron-mickey.dts | 9 +++ arch/arm/boot/dts/rk3288-veyron-minnie.dts | 21 +++++++ arch/arm/boot/dts/rk3288-veyron-pinky.dts | 22 +++++++ arch/arm/boot/dts/rk3288-veyron-speedy.dts | 21 +++++++ arch/arm/boot/dts/rk3288-veyron.dtsi | 59 +++---------------- 11 files changed, 155 insertions(+), 75 deletions(-) create mode 100644 arch/arm/boot/dts/rk3288-veyron-broadcom-bluetooth.dtsi -- 2.24.0.432.g9d3f5f5b63-goog