Lines Matching refs:device
10 #include <linux/device.h>
575 * a single USB-device / receiver.
589 /* Try to find an already-probed interface from the same device */
697 hid_err(djrcv_dev->hidpp, "%s: can't destroy a NULL device\n",
717 /* We are the only one ever adding a device, no need to lock */
719 /* The device is already known. No need to reallocate it. */
720 dbg_hid("%s: device is already known\n", __func__);
852 dbg_hid("%s: device list is empty\n", __func__);
860 * This means that the original "device paired" notification corresponding
862 * 1) hid-core discards all packets coming from a device during probe().
921 * only 1 paired device with a device_type of REPORT_TYPE_KEYBOARD. For the
924 * device with a device_type of REPORT_TYPE_MOUSE as we normally would).
1001 hid_warn(hdev, "%s: unexpected device-index %d", __func__,
1024 hid_info(hdev, "Non Logitech device connected on slot %d\n",
1078 /* custom receiver device (eg. powerplay) */
1085 "unusable device of type %s (0x%02x) connected on slot %d",
1092 hid_info(hdev, "device of type %s (0x%02x) connected on slot %d",
1335 * receiver, so do not overwrite the device index.
1543 * 3) Data is an actual input event from a paired DJ device in which
1544 * case we forward it to the correct hid device (via hid_input_report()
1556 hid_err(hdev, "%s: invalid device index:%d\n",
1564 /* received an event for an unknown device, bail out */
1603 /* special case were the device wants to know its unifying
1615 * data to the corresponding child dj device and return 0 to hid-core
1616 * so he data also goes to the hidraw device of the receiver. This
1628 hid_err(hdev, "%s: invalid device index:%d\n", __func__,
1639 * remove the old device if the user has paired a *different* device.
1828 /* Starts the usb device and connects to upper interfaces hiddev and