Return-Path: MIME-Version: 1.0 In-Reply-To: <1491584978.2136.21.camel@redhat.com> References: <20170407143516.9945-1-robh@kernel.org> <1491584978.2136.21.camel@redhat.com> From: Rob Herring Date: Fri, 7 Apr 2017 13:48:52 -0500 Message-ID: Subject: Re: [PATCH v2 3/4] bluetooth: hci_uart: add LL protocol serdev driver support To: Dan Williams Cc: Marcel Holtmann , "open list:BLUETOOTH DRIVERS" , "linux-arm-kernel@lists.infradead.org" , Gustavo Padovan , Johan Hedberg , Mark Rutland , Wei Xu , Eyal Reizer , Satish Patel , netdev , "devicetree@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 List-ID: On Fri, Apr 7, 2017 at 12:09 PM, Dan Williams 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. Rob