Hi!
>>
>> However, if I uncomment the line containing:
>>
>> err = bcm_setup_sleep(hu);
>>
>> The driver dies, with timeouts, thus:
>>
>> Bluetooth: hci0: BCM: chip id 94
>> Bluetooth: hci0: BCM43430A1 (001.002.009) build 0000
>> Bluetooth: hci0: BCM: failed to write clock (-56)
>> Bluetooth: hci0: BCM (001.002.009) build 0182
>> Bluetooth: hci0 command 0x0c56 tx timeout
>> Bluetooth: hci0 command 0x0c7a tx timeout
>> Bluetooth: hci0 command 0x0c6d tx timeout
>> Bluetooth: hci0 command 0x2008 tx timeout
>> Bluetooth: hci0 command 0x2009 tx timeout
>
> bcm_setup_sleep enable low power mode, so I think problem is
> that the wakeup gpio is not correctly drove.
> -> Are you sure that you don't toggle the power gpio instead of the
> wakeup one.
Possibly not - AFAIK, I only have one GPIO on this board, so I *assume*
its the power one. I'll see if I can find out if wakeup/irq are connected.
*HOWEVER* the code checks for success of bcm_request_irq() when deciding
to execute bcm_setup_sleep(). This makes sense to me, as I'd expect the
hardware to want to interrupt the host when it wakes up.
> -> Without host-wakeup gpio, you are not able to get controller events.
>
>> static struct platform_driver bcm_driver = {
>> .probe = bcm_probe,
>> .remove = bcm_remove,
>> .driver = {
>> .name = "hci_bcm",
>> .acpi_match_table = ACPI_PTR(bcm_acpi_match),
>> + .of_match_table = bcm_of_match,
>> .pm = &bcm_pm_ops,
>> },
>> };
>> 13
>>
>
> I think you should look at the serial device driver solution
> (e.g nokia.c), This is the preferable way now.
damnit! thats very similar to my first idea on the matter, but I
couldn't see how it was supposed to work.
Whats the right path forward here? both the drivers you listed have some
merit - the hci_bcm driver, I have working, and it seems to support
loading different firmwares well.
hci_nokia.c seems very similar, but only supports 2 firmwares, AFAICT.
-Ian
--
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
