Home
last modified time | relevance | path

Searched hist:"6 b3f75f7" (Results 1 – 3 of 3) sorted by relevance

/openbmc/linux/drivers/hid/intel-ish-hid/ishtp/
H A Dbus.h6b3f75f7 Mon Mar 18 14:14:19 CDT 2019 Hong Liu <hong.liu@intel.com> HID: intel-ish-hid: Add match callback to ishtp bus type

Currently we depend on the guid check in ishtp_cl_driver.probe to match
the device and driver. However Linux device core first calls the match()
callback to decide the matching of driver and device, and then does some
preparation before calling the driver probe function. If we return error
in the driver probe, it needs to tear down all the preparation work and
retry with next driver.

Adding the match callback can avoid the unnecessary entry into unmatched
driver probe function for ishtp clients reported by FW.

Signed-off-by: Hong Liu <hong.liu@intel.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
6b3f75f7 Mon Mar 18 14:14:19 CDT 2019 Hong Liu <hong.liu@intel.com> HID: intel-ish-hid: Add match callback to ishtp bus type

Currently we depend on the guid check in ishtp_cl_driver.probe to match
the device and driver. However Linux device core first calls the match()
callback to decide the matching of driver and device, and then does some
preparation before calling the driver probe function. If we return error
in the driver probe, it needs to tear down all the preparation work and
retry with next driver.

Adding the match callback can avoid the unnecessary entry into unmatched
driver probe function for ishtp clients reported by FW.

Signed-off-by: Hong Liu <hong.liu@intel.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
H A Dbus.c6b3f75f7 Mon Mar 18 14:14:19 CDT 2019 Hong Liu <hong.liu@intel.com> HID: intel-ish-hid: Add match callback to ishtp bus type

Currently we depend on the guid check in ishtp_cl_driver.probe to match
the device and driver. However Linux device core first calls the match()
callback to decide the matching of driver and device, and then does some
preparation before calling the driver probe function. If we return error
in the driver probe, it needs to tear down all the preparation work and
retry with next driver.

Adding the match callback can avoid the unnecessary entry into unmatched
driver probe function for ishtp clients reported by FW.

Signed-off-by: Hong Liu <hong.liu@intel.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
6b3f75f7 Mon Mar 18 14:14:19 CDT 2019 Hong Liu <hong.liu@intel.com> HID: intel-ish-hid: Add match callback to ishtp bus type

Currently we depend on the guid check in ishtp_cl_driver.probe to match
the device and driver. However Linux device core first calls the match()
callback to decide the matching of driver and device, and then does some
preparation before calling the driver probe function. If we return error
in the driver probe, it needs to tear down all the preparation work and
retry with next driver.

Adding the match callback can avoid the unnecessary entry into unmatched
driver probe function for ishtp clients reported by FW.

Signed-off-by: Hong Liu <hong.liu@intel.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
/openbmc/linux/drivers/hid/intel-ish-hid/
H A Dishtp-hid-client.c6b3f75f7 Mon Mar 18 14:14:19 CDT 2019 Hong Liu <hong.liu@intel.com> HID: intel-ish-hid: Add match callback to ishtp bus type

Currently we depend on the guid check in ishtp_cl_driver.probe to match
the device and driver. However Linux device core first calls the match()
callback to decide the matching of driver and device, and then does some
preparation before calling the driver probe function. If we return error
in the driver probe, it needs to tear down all the preparation work and
retry with next driver.

Adding the match callback can avoid the unnecessary entry into unmatched
driver probe function for ishtp clients reported by FW.

Signed-off-by: Hong Liu <hong.liu@intel.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
6b3f75f7 Mon Mar 18 14:14:19 CDT 2019 Hong Liu <hong.liu@intel.com> HID: intel-ish-hid: Add match callback to ishtp bus type

Currently we depend on the guid check in ishtp_cl_driver.probe to match
the device and driver. However Linux device core first calls the match()
callback to decide the matching of driver and device, and then does some
preparation before calling the driver probe function. If we return error
in the driver probe, it needs to tear down all the preparation work and
retry with next driver.

Adding the match callback can avoid the unnecessary entry into unmatched
driver probe function for ishtp clients reported by FW.

Signed-off-by: Hong Liu <hong.liu@intel.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>