This patch add the relevent device tree handles to the bluetooth driver
for serial realtek devices.
Specifically it takes all devices listed in btrtk.c identifes from the
realtek web site which are serial devices (this invariably means
devices that end with and "s" in the device name).
Most of these devices are dual wifi and bluetooth, with wifi on and
sdio connection, and bluetooth on a serial uart. As these two
interfaces will need independent listings in the device tree, the
nodes here have "-bluetooth" added. The only exception is the
rtl8761atv device, which is bluetooth only - and only has a uart
interface.
Can devicetree people revive the naming scheme used here, and confirm
it is acceptable.
Marcel, if the device tree people are happy can you apply to the
bluetooth tree.
Thanks,
David.
Signed-off-by: David Summers <beagleboard@xxxxxxxxxxxxxxxxxxx>
---
drivers/bluetooth/hci_h5.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/drivers/bluetooth/hci_h5.c b/drivers/bluetooth/hci_h5.c
index 8eede1197cd2..61c9e729efc1 100644
--- a/drivers/bluetooth/hci_h5.c
+++ b/drivers/bluetooth/hci_h5.c
@@ -925,6 +925,20 @@ static struct h5_vnd rtl_vnd = {
};
#endif
+#ifdef CONFIG_OF
+static const struct of_device_id h5_of_match[] = {
+ { .compatible = "realtek,rtl8723as-bluetoooth"},
+ { .compatible = "realtek,rtl8723bs-bluetoooth"},
+ { .compatible = "realtek,rtl8723ds-bluetoooth"},
+ { .compatible = "realtek,rtl8761atv"},
+ { .compatible = "realtek,rtl8821as-bluetoooth"},
+ { .compatible = "realtek,rtl8821cs-bluetoooth"},
+ { .compatible = "realtek,rtl8822bs-bluetoooth"},
+ { }
+};
+MODULE_DEVICE_TABLE(of, h5_of_match);
+#endif
+
#ifdef CONFIG_ACPI
static const struct acpi_device_id h5_acpi_match[] = {
#ifdef CONFIG_BT_HCIUART_RTL
--
beagleboard@xxxxxxxxxxxxxxxxxxx
