/Linux-v5.4/Documentation/hid/ |
D | hid-transport.rst | 86 channels, but they can also provide acknowledgement reports, automatic 100 reports. No management commands or data acknowledgements are sent on this 111 Outgoing reports are usually sent on the ctrl channel via synchronous 114 Communication between devices and HID core is mostly done via HID reports. A 117 - INPUT Report: Input reports provide data from device to host. This 122 - OUTPUT Report: Output reports change device states. They are sent from host 124 reports are never sent from device to host, but a host can retrieve their 126 Hosts may choose to send output reports either continuously or only on 128 - FEATURE Report: Feature reports are used for specific static device features 131 Feature reports are never sent without requests. A host must explicitly set [all …]
|
D | hidraw.rst | 6 Interface Devices (HIDs). It differs from hiddev in that reports sent and 12 reports manually. This is often the case when making userspace drivers for 17 descriptors. Because hiddev parses reports which are sent and received 44 devices, the reports read using read() are the reports sent from the device 50 On a device which uses numbered reports, the first byte of the returned data 52 byte. For devices which do not use numbered reports, the report data 63 number. If the device does not use numbered reports, the first byte should 114 specification, feature reports are always sent using the control endpoint. 116 which do not use numbered reports, set the first byte to 0. The report data 126 reports, set the first byte to 0. The report will be returned starting at
|
D | hid-alps.rst | 31 14 wMaxOutputLength 0000 No Output Reports 45 ReportID-1 (Input Reports) (HIDUsage-Mouse) for TP&SP 46 ReportID-2 (Input Reports) (HIDUsage-keyboard) for TP 47 ReportID-3 (Input Reports) (Vendor Usage: Max 10 finger data) for TP 48 ReportID-4 (Input Reports) (Vendor Usage: ON bit data) for GP 49 ReportID-5 (Feature Reports) Feature Reports 50 ReportID-6 (Input Reports) (Vendor Usage: StickPointer data) for SP 51 ReportID-7 (Feature Reports) Flash update (Bootloader)
|
/Linux-v5.4/Documentation/ABI/testing/ |
D | sysfs-class-power | 7 Reports the name of the device manufacturer. 16 Reports the name of the device model. 25 Reports the serial number of the device. 91 Reports an average IBAT current reading for the battery, over a 102 Reports the maximum IBAT current allowed into the battery. 111 Reports an instant, single IBAT current reading for the battery. 176 Reports the charging current value which is used to determine 186 Reports the health of the battery or battery side of charger 198 Reports the charging current applied during pre-charging phase 208 Reports whether a battery is present or not in the system. [all …]
|
D | sysfs-pps | 21 The /sys/class/pps/ppsX/assert file reports the assert events 33 The /sys/class/pps/ppsX/clear file reports the clear events 45 The /sys/class/pps/ppsX/mode file reports the functioning 55 The /sys/class/pps/ppsX/echo file reports if the X-th does 62 The /sys/class/pps/ppsX/name file reports the name of the 69 The /sys/class/pps/ppsX/path file reports the path name of
|
D | sysfs-class-remoteproc | 6 Reports the name of the firmware currently loaded to the 17 Reports the state of the remote processor, which will be one of: 58 Reports the name of the remote processor. This can be used by
|
/Linux-v5.4/drivers/hid/ |
D | hid-uclogic-rdesc.h | 106 /* Report ID for v1 pen reports */ 109 /* Fixed report descriptor template for (tweaked) v1 pen reports */ 113 /* Report ID for v2 pen reports */ 116 /* Fixed report descriptor template for (tweaked) v2 pen reports */ 120 /* Fixed report descriptor for (tweaked) v1 buttonpad reports */ 124 /* Report ID for tweaked v1 buttonpad reports */ 127 /* Fixed report descriptor for (tweaked) v2 buttonpad reports */ 131 /* Report ID for tweaked v2 buttonpad reports */ 146 /* Report ID of Ugee G5 frame control reports */
|
D | hid-uclogic-params.h | 24 /* Normal reports: zero - out of proximity, one - in proximity */ 26 /* Inverted reports: zero - in proximity, one - out of proximity */ 28 /* No reports */ 55 /* Report ID, if reports should be tweaked, zero if not */ 60 * True, if reports include fragmented high resolution coords, with 87 * Report ID, if reports should be tweaked, zero if not. 112 * reports unchanged and lets the generic HID driver handle everything.
|
D | hid-gfrm.c | 63 * Convert GFRM100 Search key reports into Consumer.0221 (Key.Search) in gfrm_raw_event() 64 * reports. Ignore audio data. in gfrm_raw_event() 111 * key reports. Thus, we need to add it manually here, so that in gfrm_probe() 112 * those reports reach gfrm_raw_event() from hid_input_report(). in gfrm_probe()
|
/Linux-v5.4/drivers/hid/usbhid/ |
D | hid-pidff.c | 25 /* Report usage table used to put reports into an array */ 147 struct hid_report *reports[sizeof(pidff_reports)]; member 254 hid_hw_request(pidff->hid, pidff->reports[PID_SET_ENVELOPE], in pidff_set_envelope_report() 281 hid_hw_request(pidff->hid, pidff->reports[PID_SET_CONSTANT], in pidff_set_constant_force_report() 316 hid_hw_request(pidff->hid, pidff->reports[PID_SET_EFFECT], in pidff_set_effect_report() 348 hid_hw_request(pidff->hid, pidff->reports[PID_SET_PERIODIC], in pidff_set_periodic_report() 366 * Send condition effect reports to the device 390 hid_hw_request(pidff->hid, pidff->reports[PID_SET_CONDITION], in pidff_set_condition_report() 431 hid_hw_request(pidff->hid, pidff->reports[PID_SET_RAMP], in pidff_set_ramp_force_report() 456 hid_hw_request(pidff->hid, pidff->reports[PID_CREATE_NEW_EFFECT], in pidff_request_effect_upload() [all …]
|
/Linux-v5.4/Documentation/media/uapi/rc/ |
D | lirc-set-rec-timeout-reports.rst | 19 LIRC_SET_REC_TIMEOUT_REPORTS - enable or disable timeout reports for IR receive 35 reports. 43 Enable or disable timeout reports for IR receive. By default, timeout reports
|
D | lirc-set-wideband-receiver.rst | 53 carrier reports. In that case it will be disabled as soon as you disable 54 carrier reports. Trying to disable wide band receiver while carrier 55 reports are active will do nothing.
|
/Linux-v5.4/drivers/usb/serial/ |
D | keyspan_usa90msg.h | 156 u8 msr, // reports the actual MSR register 157 cts, // reports CTS pin 158 dcd, // reports DCD pin 159 dsr, // reports DSR pin 160 ri, // reports RI pin 162 rxBreak, // reports break state
|
D | keyspan_usa26msg.h | 209 hskia_cts, // USA26: reports HSKIA pin 210 // USA17: reports CTS pin 211 gpia_dcd, // USA26: reports GPIA pin 212 // USA17: reports DCD pin 213 dsr, // USA17: reports DSR pin 214 ri, // USA17: reports RI pin
|
/Linux-v5.4/drivers/gpu/drm/i915/ |
D | i915_perf.c | 75 * the constraints on HW configuration require reports to be filtered before it 114 * The OA unit writes reports of counters into a circular buffer, without 134 * feature and forwarded OA reports to userspace via perf's 'raw' sample 138 * them. For Mesa it's also convenient to be forwarded raw, periodic reports 139 * for combining with the side-band raw reports it captures using 169 * attach GPU timestamps to our OA samples. We were shoehorning OA reports 235 * Although this can be observed explicitly while copying reports to userspace 236 * by checking for a zeroed report-id field in tail reports, we want to account 242 * time for the corresponding reports to become visible to the CPU. 265 * non-periodic reports (such as on context switch) or the OA unit may be [all …]
|
/Linux-v5.4/Documentation/media/uapi/v4l/ |
D | pixfmt-compressed.rst | 47 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM`` 99 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM`` 108 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM`` 188 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM`` 198 :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
|
/Linux-v5.4/Documentation/hwmon/ |
D | ltc2978.rst | 238 temperatures, and temp5 reports the chip temperature. 240 temperature measurement is supported and reports 244 temp3 reports the chip temperature. 245 - On LTC3883, temp1 reports an external temperature, 246 and temp2 reports the chip temperature.
|
/Linux-v5.4/Documentation/ia64/ |
D | aliasing.rst | 162 If the EFI memory map reports that the entire granule supports 188 The EFI memory map reports the following attributes: 208 If the EFI memory map reports that the entire range supports the 213 If EFI reports the range as partly WB and partly UC (as on sx[12]000 217 If EFI reports some of the range but not all (as on Intel firmware 224 The EFI memory map reports the following attributes::
|
/Linux-v5.4/Documentation/misc-devices/ |
D | ics932s401.rst | 24 clock, and a reference clock. The driver reports selected and actual 25 frequency. If spread spectrum mode is enabled, the driver also reports by what
|
/Linux-v5.4/Documentation/networking/ |
D | devlink-health.txt | 8 The main idea is to unify and centralize driver health reports in the 16 For each registered health reporter a driver can issue error/health reports 17 asynchronously. All health reports handling is done by devlink.
|
D | nfc.txt | 82 * NFC_EVENT_DEVICE_ADDED - reports an NFC device addition 83 * NFC_EVENT_DEVICE_REMOVED - reports an NFC device removal 84 * NFC_EVENT_TARGETS_FOUND - reports START_POLL results when 1 or more targets
|
/Linux-v5.4/Documentation/admin-guide/ |
D | ufs.rst | 64 Bug Reports 68 to dushistov@mail.ru (do not send partition tables bug reports).
|
/Linux-v5.4/drivers/input/tablet/ |
D | gtco.c | 109 struct urb *urbinfo; /* urb for incoming reports */ 111 unsigned char * buffer; /* databuffer for reports */ 193 * - We know what the IRQ reports are supposed to look like. 196 * out the mins and maxs of the fields in the IRQ reports. The IRQ 197 * reports for 400/401 change slightly if the max X is bigger than 64K. 553 * the usb system so we start getting reports 621 * URB callback routine. Called when we get IRQ reports from the 625 * on the input device based on the USB reports. 665 * Conveniently, the reports have more information, the higher in gtco_urb_callback() 701 /* All reports have X and Y coords in the same place */ in gtco_urb_callback() [all …]
|
/Linux-v5.4/drivers/block/ |
D | ps3vram.c | 78 void __iomem *reports; member 108 static u32 __iomem *ps3vram_get_notifier(void __iomem *reports, int notifier) in ps3vram_get_notifier() argument 110 return reports + DMA_NOTIFIER_OFFSET_BASE + in ps3vram_get_notifier() 117 u32 __iomem *notify = ps3vram_get_notifier(priv->reports, NOTIFIER); in ps3vram_notifier_reset() 128 u32 __iomem *notify = ps3vram_get_notifier(priv->reports, NOTIFIER); in ps3vram_notifier_wait() 709 priv->reports = ioremap(reports_lpar, reports_size); in ps3vram_probe() 710 if (!priv->reports) { in ps3vram_probe() 711 dev_err(&dev->core, "ioremap REPORTS failed\n"); in ps3vram_probe() 782 iounmap(priv->reports); in ps3vram_probe() 812 iounmap(priv->reports); in ps3vram_remove()
|
/Linux-v5.4/Documentation/scsi/ |
D | NinjaSCSI.txt | 19 If you installed pcmcia-cs already, pcmcia reports your card as UNKNOWN 118 Please send me some reports(bug reports etc..) of this software.
|