Hi Loic, >>> Thanks a lot for working on that, I've made a similar attempt a few >>> weeks ago but didn't manage to get it to work. >>> >>> The way it's hooked in our boards is a bit more complex though, even >>> if it could be because we're using a different part. >>> >>> In order to get it running we need: >>> - two clocks, called in the broadcom datasheets lpo and tcxo. >>> - three GPIOs, device wakeup, host wakeup and a shutdown GPIO (which >>> might be the BT_ON you were discussing about) >>> - two regulators called vbat and reg-en for us (I guess they're >>> meant to power the chip, and its registers >> >>> Do you know if you're also using those? Or could it be that it's just >>> hardwired to some non-gatable crystal / regulator on the RPI? > > Not on Pi3, but the three gpios and the clock are pretty common for > Broadcom bt controller (cf v4 of dt-bindings patch). once we get the GPIO expander driver upstream, I think we also need this for RPI 3 and Zero W. Right now we can just not do anything about this. However we can start looking at the PCM setup and see how that one is wired up and see if we can feed that into ALSA or wherever they terminate that. > This is already partially supported in the hci_bcm driver. > Today this driver registers a platform_driver(legacy/ACPI) and a > serdev_device_driver (new/DT). > > The platform driver retrieves the gpios and mainly uses them in pm ops. > Once the ACPI for serdev will be supported, this plat driver should be > removed. > > The serdev driver does no support this yet because I used the RPi3 > as dev platform. But this is something we want to have as well. Making ACPI serdev aware and turning BTH0 into serdev nodes is really the next step. That would allow us to simplify the drivers and remove duplicate code. Do you still have access to ACPI based tablets with Broadcom chips? It would be great if you can take a stab at this. Regards Marcel -- 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
