linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Marcel Holtmann <marcel@holtmann.org>,
	Loic Poulain <loic.poulain@gmail.com>
Cc: devicetree@vger.kernel.org,
	Johan Hedberg <johan.hedberg@gmail.com>,
	rjui@broadcom.com, linux-bluetooth@vger.kernel.org,
	robh+dt@kernel.org, linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH v4 3/4] ARM: dts: bcm2837-rpi-3-b: Add bcm43438 serial slave
Date: Wed, 23 Aug 2017 09:17:29 -0700	[thread overview]
Message-ID: <8760dep8bq.fsf@anholt.net> (raw)
In-Reply-To: <972AD2C1-FE7C-412D-AEC6-FFED22EC4B77@holtmann.org>

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

Marcel Holtmann <marcel@holtmann.org> writes:

> Hi Loic,
>
>> Add BCM43438 (bluetooth) as a slave device of uart0 (pl011/ttyAMA0).
>> This allows to automatically insert the bcm43438 to the bluetooth
>> subsystem instead of relying on userspace helpers (hciattach).
>> 
>> Overwrite chosen/stdout-path to use 8250 aux uart as console.
>> 
>> Signed-off-by: Loic Poulain <loic.poulain@gmail.com>
>> ---
>> v2: dt-bindings as separate patch
>>     rebase on upcoming pi3 dts changes
>> v3: changes in bcm serdev drivers:
>>     name refactoring and additional comments
>>     Add generic host_set_baudrate method
>>     Use agnostic device_property_read
>> v4: changes in doc and dts:
>>     Add additional params to broadcom bt dt-bindings
>>     Set the max baudrate to 2000000 instead of 921600
>>     use chosen/stdout-path instead of console=
>>     remove useless earlyprintk
>>     same changes in bcm283x.dtsi
>> 
>> arch/arm/boot/dts/bcm2837-rpi-3-b.dts | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>
> do you mind resending the 2 pending patches with Rob’s ack on it. And ensure that this goes with DT tree since I can currently not take it since net-next has not pulled in the pending DT patches.

Normally we wouldn't need a resend and I'd just apply the acks when
applying the DT patches, but I don't see them in my mail.

(Also, note that since we're already at rc6 I might not be able to apply
DT patches to -next until rc1 rolls around)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-08-23 16:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17 17:59 [PATCH v4 1/4] dt-bindings: net: bluetooth: Add broadcom-bluetooth Loic Poulain
2017-08-17 17:59 ` [PATCH v4 2/4] ARM: dts: bcm283x: Use stdout-path instead of console bootarg Loic Poulain
2017-08-22  2:30   ` Rob Herring
2017-08-17 17:59 ` [PATCH v4 3/4] ARM: dts: bcm2837-rpi-3-b: Add bcm43438 serial slave Loic Poulain
2017-08-22  2:31   ` Rob Herring
2017-08-23 14:22   ` Marcel Holtmann
2017-08-23 16:17     ` Eric Anholt [this message]
2017-08-23 16:22     ` Rob Herring
2017-08-17 17:59 ` [PATCH v4 4/4] Bluetooth: hci_bcm: Add serdev support Loic Poulain
2017-08-17 19:30   ` Marcel Holtmann
2017-08-17 19:48   ` Marcel Holtmann
2017-08-17 20:12     ` Loic Poulain
2017-08-22  2:29 ` [PATCH v4 1/4] dt-bindings: net: bluetooth: Add broadcom-bluetooth Rob Herring

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=8760dep8bq.fsf@anholt.net \
    --to=eric@anholt.net \
    --cc=devicetree@vger.kernel.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=loic.poulain@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=rjui@broadcom.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).