From: "Heiko Stübner" <heiko@sntech.de>
To: Marcel Holtmann <marcel@holtmann.org>,
Douglas Anderson <dianders@chromium.org>
Cc: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
BlueZ <linux-bluetooth@vger.kernel.org>,
linux-rockchip@lists.infradead.org,
devicetree <devicetree@vger.kernel.org>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/1] ARM: dts: rockchip: Add brcm bluetooth for rk3288-veyron
Date: Mon, 09 Dec 2019 01:03:00 +0100 [thread overview]
Message-ID: <1788857.Va9C3Z3akr@diego> (raw)
In-Reply-To: <61639BAF-5AA0-4264-906F-E24E2A30088D@holtmann.org>
Am Montag, 9. Dezember 2019, 00:48:31 CET schrieb Marcel Holtmann:
> > This enables the Broadcom uart bluetooth driver on uart0 and gives it
> > ownership of its gpios. In order to use this, you must enable the
> > following kconfig options:
> > - CONFIG_BT_HCIUART_BCM
> > - CONFIG_SERIAL_DEV
> >
> > This is applicable to rk3288-veyron series boards that use the bcm43540
> > wifi+bt chips.
> >
> > As part of this change, also refactor the pinctrl across the various
> > boards. All the boards using broadcom bluetooth shouldn't touch the
> > bt_dev_wake pin.
>
> so have these changes being merged?
not yet
Doug wanted to give a Reviewed-by, once the underlying bluetooth
changes got merged - not sure what the status is though.
Heiko
next prev parent reply other threads:[~2019-12-09 0:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 22:39 [PATCH v2 0/1] ARM: dts: rockchip: Add brcm bluetooth for rk3288-veyron Abhishek Pandit-Subedi
2019-11-27 22:39 ` [PATCH v2 1/1] " Abhishek Pandit-Subedi
2019-12-08 23:48 ` Marcel Holtmann
2019-12-09 0:03 ` Heiko Stübner [this message]
2019-12-09 23:56 ` Doug Anderson
2019-12-10 0:32 ` Matthias Kaehlcke
2019-12-10 7:44 ` Marcel Holtmann
2019-12-10 22:32 ` Heiko Stuebner
2019-12-16 19:29 ` Abhishek Pandit-Subedi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1788857.Va9C3Z3akr@diego \
--to=heiko@sntech.de \
--cc=abhishekpandit@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=marcel@holtmann.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).