Hi Dmitry, >> We are planning to further implement the followings, kindly please >> provide your suggestions. >> 1. To handle more than 1 Intel BT controller connected to platform, >> will keep list of the objects in "static const struct acpi_device_id >> intel_bt_rfkill_acpi_match[] ". And keep a list of "struct >> intel_bt_rfkill_dev" for each of the acpi object. >> 2. With this implementation from user space RF kill for the device >> object is achieved, however need to map the rfkill object with the >> corresponding "hdev" so that on error from the controller kernel can >> do the reset through this RF Kill driver. > > I am confused, why you model a generic chip reset functionality via > RFKill subsystem. As far as I understand, the issue is that you want to > be able to reset the chip when it gets confused and not actually disable > the chip/stop it from emitting RF signals. > > I believe this functionality should be contained in the driver and you > simply need to come with a way to tie the adapter instance with data in > ACPI, probably based on physical USB connection. it is impossible to do that in the driver since what the GPIO is doing is to push the USB device off the bus. So you actually see an USB disconnect and a new re-enumeration when it comes back. Meaning the driver knows nothing during that time. This is a classic soft RFKILL switch like we have seen in the early Thinkpads. Yes, this could be done all nicely with proper integration into the driver, but not with this hardware setup. They took the big hammer approach and killed the power to the device. A proper defined Reset GPIO would have been better and then we could have done this nicely within the driver. However if the device disappears, there is nothing for the driver to do. Regards Marcel
