Messages in this thread | | | Date | Fri, 09 Aug 2013 18:33:43 +0200 | From | Alexander Holler <> | Subject | Re: [rtc-linux] Re: [PATCH 2/2 RESEND] rtc: rtc-hid-sensor-time: enable HID input processing early |
| |
Am 09.08.2013 18:21, schrieb Alexander Holler: > I've now also verified if hid-sensor-hub receives an event with > sensor_hub_raw_event() in the error-path (hid_device_io_stop() called > and probe() failed), and this still *does* happen. That event (input > report) doesn't come through hid-sensor-hub to my driver, but I think > this is because of my call to sensor_hub_remove_callback() which is in > the error path too. > So I actually wonder why the input report still is reported from the > hid-subsystem to hid-sensor-hub, even after I've called > hid_device_io_stop() and probe() failed. > Maybe everything is still ok and I just got confused with the somehow > complicate interactions between the usb- and hid-subsystem, > hid-sensor-hub (which uses MFD) and rtc-hid-sensor-time.
Adding some more stuff to the confusion: Currently I think it is correct that hid-sensor-hub still receives the event, even after rtc-hid-sensor-time called hid_device_io_stop() and probe() failed. The reason the same reason, why hid-sensor-hub uses mfd, the actual hardware device might be shared by different drivers (therfor -hub).
Regards,
Alexander Holler
| |