From: dcbw@redhat.com (Dan Williams)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/4] bluetooth: hci_uart: add LL protocol serdev driver support
Date: Fri, 07 Apr 2017 15:09:18 -0500 [thread overview]
Message-ID: <1491595758.2136.28.camel@redhat.com> (raw)
In-Reply-To: <CAL_Jsq+aM+xxbu=3v8_w9Ce+=t_pXmVWuisnckA8_8LOS-ftVA@mail.gmail.com>
On Fri, 2017-04-07 at 13:48 -0500, Rob Herring wrote:
> On Fri, Apr 7, 2017 at 12:09 PM, Dan Williams <dcbw@redhat.com>
> wrote:
> > On Fri, 2017-04-07 at 09:35 -0500, Rob Herring wrote:
> > > Turns out that the LL protocol and the TI-ST are the same thing
> > > AFAICT.
> > > The TI-ST adds firmware loading, GPIO control, and shared access
> > > for
> > > NFC, FM radio, etc. For now, we're only implementing what is
> > > needed
> > > for
> > > BT. This mirrors other drivers like BCM and Intel, but uses the
> > > new
> > > serdev bus.
> > >
> > > The firmware loading is greatly simplified by using existing
> > > infrastructure to send commands. It may be a bit slower than the
> > > original code using synchronous functions, but the real
> > > bottleneck is
> > > likely doing firmware load at 115.2kbps.
> >
> > Is there no way to put the TI-specific stuff into a TI UART module
> > rather than building it into the generic one?
>
> In case it's not clear, all of HCI_LL is the TI specific part, not
> just what I'm adding. So you are talking about putting each UART BT
> protocol into a separate module. I'd assume that is doable, but seems
> orthogonal to this patch set. I'd also assume there was some reason
> that was not done already.
Ok, thanks for the explanation. Wasn't clear at all from the file
paths in the source tree; it looked generic.
Dan
next prev parent reply other threads:[~2017-04-07 20:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 18:30 [PATCH 0/4] TI Bluetooth serdev support Rob Herring
2017-04-05 18:30 ` [PATCH 1/4] dt-bindings: net: Add TI WiLink shared transport binding Rob Herring
2017-04-05 18:30 ` [PATCH 2/4] bluetooth: hci_uart: remove unused hci_uart_init_tty Rob Herring
2017-04-05 18:30 ` [PATCH 3/4] bluetooth: hci_uart: add LL protocol serdev driver support Rob Herring
2017-04-07 14:35 ` [PATCH v2 " Rob Herring
2017-04-07 17:09 ` Dan Williams
2017-04-07 18:48 ` Rob Herring
2017-04-07 20:09 ` Dan Williams [this message]
2017-04-12 20:20 ` Marcel Holtmann
2017-04-05 18:30 ` [PATCH 4/4] arm64: dts: hikey: add WL1835 Bluetooth device node Rob Herring
2017-04-30 15:14 ` [PATCH 0/4] TI Bluetooth serdev support Adam Ford
2017-04-30 16:04 ` Sebastian Reichel
2017-05-05 14:51 ` Adam Ford
2017-05-08 19:07 ` Sebastian Reichel
2017-05-08 21:12 ` Rob Herring
2017-05-09 4:48 ` Baruch Siach
2017-05-09 14:14 ` Rob Herring
2017-10-27 10:55 ` Adam Ford
2017-10-28 11:33 ` Adam Ford
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=1491595758.2136.28.camel@redhat.com \
--to=dcbw@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).