Hi Loic, -----Original Message----- From: linux-bluetooth-owner@xxxxxxxxxxxxxxx [mailto:linux-bluetooth-owner@xxxxxxxxxxxxxxx] On Behalf Of Loic Poulain Sent: Wednesday, August 19, 2015 1:14 PM To: marcel@xxxxxxxxxxxx Cc: linux-bluetooth@xxxxxxxxxxxxxxx Subject: Re: [PATCH] Bluetooth: hci_intel: Add platform driver On 19/08/2015 19:11, Loic Poulain wrote: > A platform device can be used to provide some specific resources in > order to manage the controller. In this first patch we retrieve the > reset gpio which is used to power on/off the controller. Is there a patch with the DT documentation? It would be interesting to see what DT maintainers think of this approach. > > The main issue is to match the current tty with the correct pdev. > In case of ACPI, we can easily find the right tty/pdev pair because > they are both child of the same UART port. > In case of device tree, there is currently nothing to link the pdev > with its tty. So, we just match the first available pdev. That allows you to run with a single device per platform only. Meanwhile, you could have something in the DT parameters identifying the UART. You would then be able to retrieve that parameter and match it against the tty in the BT protocol. Multiple devices per platform would then be supported. Thanks, -Ilya > > If controller is powered-on from the driver, we need to wait for a > HCI boot event before being able to send any command. > > Signed-off-by: Loic Poulain <loic.poulain@xxxxxxxxx> > --- > drivers/bluetooth/hci_intel.c | 275 +++++++++++++++++++++++++++++++++++++++--- > 1 file changed, 255 insertions(+), 20 deletions(-) Apply over: Bluetooth: hci_uart: Add Intel baudrate configuration support Regards, Loic -- Intel Open Source Technology Center http://oss.intel.com/ -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
