Lines Matching defs:report
99 * bluetooth. The message lengths are defined by the hid vendor specific report
100 * descriptor for the HIDPP_SHORT report type (total message lenth 7 bytes) and
101 * the HIDPP_LONG report type (total message length 20 bytes)
103 * The RAP protocol uses both report types, whereas the FAP only uses HIDPP_LONG
349 /* Send as long report if short reports are not supported. */
408 struct hidpp_report *report)
411 (report->fap.feature_index == hidpp->wireless_feature_index)) ||
412 ((report->report_id == REPORT_ID_HIDPP_SHORT) &&
413 (report->rap.sub_id == 0x41));
711 struct hidpp_report *report = (struct hidpp_report *)data;
715 if (report->report_id != REPORT_ID_HIDPP_SHORT)
718 switch (report->rap.sub_id) {
721 level = hidpp10_battery_status_map_level(report->rawbytes[1]);
722 status = hidpp10_battery_status_map_status(report->rawbytes[2]);
725 capacity = report->rap.params[0];
727 status = hidpp10_battery_mileage_map_status(report->rawbytes[3]);
1099 * The spec says this should be < 31 but some devices report 30
1254 struct hidpp_report *report = (struct hidpp_report *)data;
1258 if (report->fap.feature_index != hidpp->battery.feature_index ||
1259 report->fap.funcindex_clientid != EVENT_BATTERY_LEVEL_STATUS_BROADCAST)
1262 status = hidpp20_batterylevel_map_status_capacity(report->fap.params,
1401 struct hidpp_report *report = (struct hidpp_report *)data;
1404 if (report->fap.feature_index != hidpp->battery.voltage_feature_index ||
1405 report->fap.funcindex_clientid != EVENT_BATTERY_VOLTAGE_STATUS_BROADCAST)
1408 status = hidpp20_battery_map_status_voltage(report->fap.params, &voltage,
1644 struct hidpp_report *report = (struct hidpp_report *)data;
1648 function = report->fap.funcindex_clientid;
1651 if (report->fap.feature_index != hidpp->battery.solar_feature_index ||
1657 capacity = report->fap.params[0];
1661 lux = (report->fap.params[1] << 8) | report->fap.params[2];
2550 struct hidpp_report *report = (struct hidpp_report *)data;
2559 hid_err(hdev, "Received HID report of bad size (%d)",
2577 if ((report->fap.feature_index != wd->mt_feature_index) ||
2578 (report->fap.funcindex_clientid != EVENT_TOUCHPAD_RAW_XY))
2686 /* how buttons are mapped in the report */
2724 hid_err(hdev, "error in report\n");
2731 * m560 mouse report for middle, forward and backward button
2759 hid_err(hdev, "error in report\n");
2766 * Logitech M560 mouse report
3087 * Buttons are either delivered through the regular mouse report *or*
3088 * through the extra buttons report. At least for button 6 how it is
3096 /* Some mice report events on button 9+, use BTN_MISC */
3120 /* HID++1.0 kbds which only report 0x10xx consumer usages through sub-id 0x03 */
3123 /* Find the consumer-page input report desc and change Maximums to 0x107f */
3172 * Build a normal consumer report (3) out of the data, this detour
3173 * is necessary to get some keyboards to report their 0x10xx usages.
3314 struct hidpp_report *report = (struct hidpp_report *)data;
3326 if (hidpp_match_answer(question, report) ||
3327 hidpp_match_error(question, report)) {
3328 *answer = *report;
3341 if (unlikely(hidpp_report_is_connect_event(hidpp, report))) {
3343 !(report->rap.params[0] & (1 << 6)));
3388 static int hidpp_raw_event(struct hid_device *hdev, struct hid_report *report,
3401 hid_err(hdev, "received hid++ report of bad size (%d)",
3409 hid_err(hdev, "received hid++ report of bad size (%d)",
3417 hid_err(hdev, "received hid++ report of bad size (%d)",
3425 /* If no report is available for further processing, skip calling
3742 struct hid_report *report;
3745 report = re->report_id_hash[id];
3746 if (!report)
3749 return report->field[0]->report_count + 1;
3790 hid_warn(hdev, "not enough values in hidpp report %d\n", id);
3798 struct hid_report *report;
3801 report = list_first_entry_or_null(report_list, struct hid_report, list);
3802 return report && report->application == application;