Lines Matching refs:device
65 /* Generic Bluetooth USB device */
68 /* Generic Bluetooth AMP device */
328 /* Asus WL-BTD202 device */
500 /* Dell OptiPlex 3060 (QCA ROME device 0cf3:e007) */
507 /* Dell XPS 9360 (QCA ROME device 0cf3:e300) */
514 /* Dell Inspiron 5565 (QCA ROME device 0cf3:e009) */
614 * is going to yank the device off the USB and then replug. So doing
616 * (standard USB disconnect), and the new device is detected cleanly
639 bt_dev_err(hdev, "No gpio to reset Realtek device, ignoring");
643 /* Toggle the hard reset line. The Realtek device is going to
646 * device is detected cleanly and bound to the driver again like
654 bt_dev_err(hdev, "Reset Realtek device via gpio");
668 bt_dev_err(hdev, "Multiple cmd timeouts seen. Resetting usb device.");
669 /* This is not an unbalanced PM reference since the device will reset */
899 * -ENODEV: device got disconnected
989 * -ENODEV: device got disconnected
1085 * -ENODEV: device got disconnected
1234 * -ENODEV: device got disconnected
1361 /* Disable device remote wakeup when host is suspended
1363 * SET_FEATURE (DEVICE_REMOTE_WAKEUP) can save more power in device.
1866 * squatting of this poor old Bluetooth 1.1 device. Even sold as such.
1925 * early Bluetooth 1.1 device from CSR.
2028 * device. Some vendor commands expects more than one events, for
2132 /* fw_patch_num indicates the version of patch the device currently
2133 * have. If there is no patch data in the device, it is always 0x00.
2134 * So, if it is other than 0x00, no need to patch the device again.
2137 bt_dev_info(hdev, "Intel device is already patched. "
2145 * If no patch file is found, allow the device to operate without
2277 /* When the device is in bootloader mode, then it can send
2330 * the device sends a vendor specific event
2337 * device sends out a vendor specific event
2484 /* The firmware variant determines if the device is in bootloader
2490 * the check for valid Bluetooth device address is needed. This
2491 * determines if the device will be added as configured or
2503 /* If the device is not in bootloader mode, then the only possible
2504 * choice is to return an error and abort the device initialization.
2529 /* If the OTP has no valid Bluetooth device address, then there will
2533 bt_dev_info(hdev, "No device address configured");
2537 /* With this Intel bootloader only the hardware variant and device
2571 bt_dev_info(hdev, "Found device firmware: %s", fwname);
2595 /* Before switching the device into operational mode and with that
2604 * of this device.
2654 /* Read the Intel version information to determine if the device
2690 /* The bootloader will not indicate when the device is ready. This
2697 bt_dev_info(hdev, "Waiting for device to boot");
2728 /* Once the device is running in operational mode, it needs to
2729 * apply the device configuration (DDC) parameters.
2731 * The device can work without DDC parameters, so even if it
2766 * The device will function correctly without these events enabled
2802 bt_dev_err(hdev, "turning off Intel device LED failed");
2958 * between the two consecutive control URBs to relax the target device
2960 * the device successfully.
2969 * -ENODEV: device got disconnected
3311 bt_dev_err(hdev, "Failed to get device id (%d)", err);
3346 /* Setup a firmware which the device definitely requires */
3414 /* Disable the device */
3434 /* Configure an out-of-band gpio as wake-up pin, if specified in device tree */
3439 struct device *dev = &data->udev->dev;
3491 bt_dev_err(hdev, "changing Marvell device address failed (%ld)",
3946 struct device *dev = &data->udev->dev;