From: Ryan <ryanphilips19@googlemail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>
Subject: Re: btbcm issue
Date: Tue, 9 Aug 2016 18:12:52 +0530 [thread overview]
Message-ID: <CANMsd03gwuttLRzDdXf1sEmUHJ=jJvGNtLt3yD2dFsLtD2ajEw@mail.gmail.com> (raw)
In-Reply-To: <D33F5F42-68EC-4DCA-B4DB-E2A9F482629E@holtmann.org>
Hi Marcel,
Is this what you are referring to?
http://www.spinics.net/lists/linux-bluetooth/msg61742.html
In this patchset, bcm tried to create new functionality/files for uart and =
bcm.
If not, can you point me to the right set of patches?
Regards,
ryan
On Tue, Aug 9, 2016 at 1:07 PM, Marcel Holtmann <marcel@holtmann.org> wrote=
:
> Hi Ryan,
>
>> I wanted to check whats the best way of going about adding
>> suspend-resume support for bcm bt chip
>>
>> Should one have a separate driver
>> (https://android.googlesource.com/kernel/bcm/+/3d6d35972004824a9111f1392=
6bed2a4a495b668/drivers/misc/bcm-bt-lpm.c)
>>
>> or should i use the existing hci_bcm.c driver & add dt support or use
>> a platform device to pass the gpiod_desc for wakeup/sleep?
>
> no separate driver please. As soon as btattach links the UART and we enab=
le the device, everything should be done in background by the driver. The B=
roadcom LPM driver is just a hack for Android since they still haven't swit=
ched to using HCI User Channel for Android (like Intel for example).
>
> In general DT and ACPI are the same. They describe the hardware and there=
are methods to read these descriptions from them and then use them. The on=
ly problem with DT was that Broadcom never got the definition acked by the =
DT maintainer. Otherwise all the functionality should be already in hci_bcm=
.c right now.
>
> Regards
>
> Marcel
>
prev parent reply other threads:[~2016-08-09 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 7:39 btbcm issue Ryan
2016-07-21 8:00 ` Marcel Holtmann
[not found] ` <CANMsd01O4s=g-B3i+Z-w4LY52CzfOKhGPhfHxD29sVn0JR245A@mail.gmail.com>
2016-08-09 7:37 ` Marcel Holtmann
2016-08-09 12:42 ` Ryan [this message]
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='CANMsd03gwuttLRzDdXf1sEmUHJ=jJvGNtLt3yD2dFsLtD2ajEw@mail.gmail.com' \
--to=ryanphilips19@googlemail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).