Home
last modified time | relevance | path

Searched refs:Event (Results 1 – 94 of 94) sorted by relevance

/linux-4.1.27/Documentation/input/
Dcma3000_d0x.txt63 Event type 0 (Sync)
64 Event type 3 (Absolute)
65 Event code 0 (X)
70 Event code 1 (Y)
75 Event code 2 (Z)
80 Event code 40 (Misc)
84 Event type 4 (Misc)
Dinput.txt46 1.2 Event handlers
154 3.2 Event handlers
156 Event handlers distribute the events from the devices to userland and
262 5. Event interface
Devent-codes.txt20 Event types:
22 Event types are groupings of codes under a logical input construct. Each
66 Event codes:
68 Event codes define the precise type of event.
Dmulti-touch-protocol.txt55 important. Event filtering and finger tracking is left to user space [3].
159 Event Usage
222 Event Semantics
339 Event Computation
Drotary-encoder.txt27 Event a b c d a b c d a b c d
Djoystick-api.txt22 2. Event Reading
Datarikbd.txt104 5.1 Joystick Event Reporting
/linux-4.1.27/drivers/input/tablet/
DKconfig21 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
34 "Mouse support" (CONFIG_INPUT_MOUSEDEV) and/or "Event interface
46 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
70 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
/linux-4.1.27/tools/perf/tests/
Dattr.py25 class Event(dict): class
93 for t in Event.terms:
102 for t in Event.terms:
167 e = Event(section, parser_items, base_items)
/linux-4.1.27/Documentation/devicetree/bindings/x86/
Dtimer.txt4 * High Precision Event Timer (HPET)
/linux-4.1.27/Documentation/timers/
Dhpet.txt1 High Precision Event Timer Driver for Linux
3 The High Precision Event Timer (HPET) hardware follows a specification
D00-INDEX6 - High Precision Event Timer Driver for Linux
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-firmware-acpi152 invalid: it's either a GPE or a Fixed Event that
155 disable: the GPE/Fixed Event is valid but disabled.
157 enable: the GPE/Fixed Event is valid and enabled.
172 Note that only writting to VALID GPE/Fixed Event is allowed,
174 Fixed Event with event handler installed.
Dsysfs-firmware-dmi83 --- Type 15 - System Event Log ---
94 SMBIOS / DMI specification under "System Event Log (Type 15)":
Dsysfs-bus-iio-light-lm3533-als6 Event generated when channel passes one of the four thresholds
Dsysfs-bus-event_source-devices-events64 This is referred to as "event parameterization". Event
Dsysfs-bus-iio547 Event generated when channel passes a threshold in the specified
600 Event generated when channel passes a threshold on the rate of
953 Event generated when channel passes a threshold on the absolute
/linux-4.1.27/Documentation/trace/
Dtracepoint-analysis.txt55 3.1 System-Wide Event Enabling
64 3.2 System-Wide Event Enabling with SystemTap
89 3.3 System-Wide Event Enabling with PCL
110 3.4 Local Event Enabling
116 3.5 Local Event Enablement with PCL
134 4. Event Filtering
141 5. Analysing Event Variances with PCL
Dkprobetrace.txt1 Kprobe-based Event Tracing
30 EVENT : Event name. If omitted, the event name is generated
66 Per-Probe Event Filtering
87 Event Profiling
Devents.txt1 Event Tracing
18 2. Using Event Tracing
101 4. Event formats
152 5. Event filtering
291 6. Event triggers
301 section 5 (Event filtering) associated with it - the command will only
312 Event triggers are implemented on top of "soft" mode, which means that
343 The filter syntax is the same as that described in the 'Event
Duprobetracer.txt1 Uprobe-tracer: Uprobe-based Event Tracing
27 EVENT : Event name. If omitted, the event name is generated based
61 Event Profiling
/linux-4.1.27/Documentation/video4linux/cx2341x/
Dfw-decoder-api.txt239 Event: 0=Audio mode change between mono, (joint) stereo and dual channel.
240 Event: 3=Decoder started
241 Event: 4=Unknown: goes off 10-15 times per second while decoding.
242 Event: 5=Some sync event: goes off once per frame.
Dfw-calling.txt64 Event notifications are sent from the firmware to the host. The host tells the
Dfw-encoder-api.txt582 Event (0=refresh encoder input)
/linux-4.1.27/drivers/isdn/hardware/eicon/
Dkst_ifc.h44 dword Event; member
77 dword Event; member
Ddebug.c1523 diva_mnt_internal_dprintf(pC->hDbg->id, DLI_STAT, "MDM Event = %lu", modem->Event); in diva_maint_state_change_notify()
1542 if (modem->Event == 3) { in diva_maint_state_change_notify()
1546 if ((modem->Event == 3) && (pC->hDbg->dbgMask & DIVA_MGT_DBG_MDM_STATISTICS)) { in diva_maint_state_change_notify()
1568 diva_mnt_internal_dprintf(pC->hDbg->id, DLI_STAT, "FAX Event = %lu", fax->Event); in diva_maint_state_change_notify()
1579 if (fax->Event == 3) { in diva_maint_state_change_notify()
1583 if ((fax->Event == 3) && (pC->hDbg->dbgMask & DIVA_MGT_DBG_FAX_STATISTICS)) { in diva_maint_state_change_notify()
Dmaintidi.c1347 pLib->parse_table[pLib->cur_parse_entry++].variable = &pFax->Event; in diva_create_fax_parse_table()
1411 pLib->parse_table[pLib->cur_parse_entry++].variable = &pModem->Event; in diva_create_modem_parse_table()
/linux-4.1.27/tools/perf/Documentation/
Dperf-list.txt67 Figure 13-7 Performance Event-Select Register (PerfEvtSeln)).
78 Event Umask Event Mask
Dperf-top.txt26 Event period to sample.
215 Event to display when multiple counters are active.
Dperf-record.txt64 Event filter.
93 Event period to sample.
Dperf-report.txt83 - weight: Event specific weight, e.g. memory latency or transaction
/linux-4.1.27/drivers/devfreq/event/
DKconfig2 bool "DEVFREQ-Event device Support"
/linux-4.1.27/drivers/staging/iio/
DKconfig33 bool "Event generation support"
/linux-4.1.27/drivers/input/
DKconfig143 tristate "Event interface"
152 tristate "Event debugging"
166 tristate "Input Power Event -> APM Bridge" if EXPERT
/linux-4.1.27/Documentation/powerpc/
D00-INDEX25 - Description of the API for using the PMU with Event Based Branches.
Dpmu-ebb.txt1 PMU Event Based Branches
4 Event Based Branches (EBBs) are a feature which allows the hardware to
/linux-4.1.27/Documentation/networking/
Dxfrm_sync.txt64 XFRM_AE_CR=16, /* Event cause is replay update */
65 XFRM_AE_CE=32, /* Event cause is timer expiry */
66 XFRM_AE_CU=64, /* Event cause is policy update */
De100.txt82 Event Log Message Level: The driver uses the message level flag to log events
/linux-4.1.27/arch/powerpc/platforms/pseries/
DKconfig66 bool "IO Event Interrupt support"
70 Select this option, if you want to enable support for IO Event
/linux-4.1.27/drivers/pci/pcie/
DKconfig10 Power Management Event support and Virtual Channel support to run
/linux-4.1.27/drivers/block/
DDAC960.c1460 Controller->V2.Event = slice_dma_loaf(DmaPages, in DAC960_V2_EnableMemoryMailboxInterface()
4385 DAC960_V2_Event_T *Event) in DAC960_V2_ReportEvent() argument
4388 (DAC960_SCSI_RequestSense_T *) &Event->RequestSenseData; in DAC960_V2_ReportEvent()
4513 if (Event->EventCode == 0x1C && in DAC960_V2_ReportEvent()
4517 Event->EventCode = ((RequestSense->AdditionalSenseCode - 0x80) << 8) | in DAC960_V2_ReportEvent()
4522 if (EventCode == Event->EventCode || EventCode == 0) break; in DAC960_V2_ReportEvent()
4530 Controller, Event->EventCode); in DAC960_V2_ReportEvent()
4537 Event->Channel, Event->TargetID, EventMessage); in DAC960_V2_ReportEvent()
4541 Event->LogicalUnit, Controller->ControllerNumber, in DAC960_V2_ReportEvent()
4542 Event->LogicalUnit, EventMessage); in DAC960_V2_ReportEvent()
[all …]
DDAC960.h2468 DAC960_V2_Event_T *Event; member
/linux-4.1.27/drivers/media/pci/ngene/
Dngene-core.c77 struct EVENT_BUFFER Event = in event_tasklet() local
82 if ((Event.UARTStatus & 0x01) && (dev->TxEventNotify)) in event_tasklet()
83 dev->TxEventNotify(dev, Event.TimeStamp); in event_tasklet()
84 if ((Event.UARTStatus & 0x02) && (dev->RxEventNotify)) in event_tasklet()
85 dev->RxEventNotify(dev, Event.TimeStamp, in event_tasklet()
86 Event.RXCharacter); in event_tasklet()
/linux-4.1.27/Documentation/devicetree/bindings/net/can/
Dm_can.txt40 Tx Event FIFO 0-32 elements / 0-64 words
/linux-4.1.27/Documentation/scsi/
Darcmsr_spec.txt228 ** GUI_POLL_EVENT : Poll If Event Log Changed
231 ** GUI_GET_EVENT : Read Event
234 ** byte 3 : Event Page (0:1st page/1/2/3:last page)
382 ** GUI_CLEAR_EVENT : Clear System Event
Dscsi_fc_transport.txt254 State Event New State
/linux-4.1.27/drivers/staging/iio/Documentation/
Doverview.txt23 * Event chrdevs. These are similar to input in that they provide a
/linux-4.1.27/drivers/scsi/mpt3sas/
Dmpt3sas_trigger_diag.c83 mpi_reply->Event = cpu_to_le16(MPI3_EVENT_DIAGNOSTIC_TRIGGER_FIRED); in _mpt3sas_raise_sigio()
Dmpt3sas_base.c562 event = le16_to_cpu(mpi_reply->Event); in _base_display_event_data()
801 ack_request->Event = mpi_reply->Event; in _base_async_event()
Dmpt3sas_ctl.c359 event = le16_to_cpu(mpi_reply->Event); in mpt3sas_ctl_add_to_event_log()
Dmpt3sas_scsih.c4019 event_reply->Event = in _scsih_smart_predicted_fault()
7183 event = le16_to_cpu(mpi_reply->Event); in mpt3sas_scsih_event_callback()
/linux-4.1.27/drivers/message/fusion/lsi/
Dmpi_ioc.h448 U32 Event; /* 14h */ member
464 U32 Event; /* 0Ch */ member
Dmpi_history.txt141 * 09-28-01 01.02.03 Modified Event Data for Integrated RAID.
167 * 01-15-05 01.05.05 Added event data for SAS SES Event.
199 * Broadcast Event Data (replacing _RESERVED2).
200 * For Discovery Error Event Data DiscoveryStatus field,
211 * Change Event data to indicate completion of internally
/linux-4.1.27/Documentation/
DIPMI.txt672 * Event Dir | Event Type: 0x6f (Assertion, sensor-specific event info)
673 * Event Data 1: 0xa1 (Runtime stop in OEM bytes 2 and 3)
674 * Event data 2: second byte of panic string
675 * Event data 3: third byte of panic string
Dkernel-docs.txt289 * Title: "I/O Event Handling Under Linux"
293 Description: From the Introduction: "I/O Event handling is about
Ddevices.txt2894 3 = /dev/cpqhealth/cevt Event Log
/linux-4.1.27/drivers/scsi/mpt3sas/mpi/
Dmpi2_ioc.h474 U16 Event; /*0x14 */ member
1062 U16 Event; /*0x0C */ member
/linux-4.1.27/drivers/scsi/mpt2sas/mpi/
Dmpi2_ioc.h482 U16 Event; /* 0x14 */ member
1068 U16 Event; /* 0x0C */ member
/linux-4.1.27/Documentation/usb/
DWUSB-Design-overview.txt182 handle called /neh/ (Notification/Event Handle) is opened with
421 *NEH* -- Notification/Event Handle
427 *NEEP* -- Notification/Event EndPoint
Dusbmon.txt119 - Event Type. This type refers to the format of the event, not URB type.
/linux-4.1.27/Documentation/arm64/
Dacpi_object_usage.txt98 == Event Timer Description Table ==
145 == High Precision Event timer Table ==
492 ACPI Event Model
/linux-4.1.27/drivers/net/hippi/
Drrunner.h26 u32 Event; member
Drrunner.c359 writel(0, &regs->Event); in rr_reset()
/linux-4.1.27/Documentation/acpi/apei/
Deinj.txt170 [22715.834759] EDAC sbridge MC3: CPU 0: Machine Check Event: 0 Bank 7: 8c00004000010090
/linux-4.1.27/Documentation/i2c/
Dslave-interface60 Event types:
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/
Ddcsr.txt55 Event Processing Unit
Dfman.txt395 Definition: Event interrupt of external MDIO controller.
/linux-4.1.27/drivers/macintosh/
DKconfig170 "Mouse Support" (CONFIG_INPUT_MOUSEDEV) and "Event interface
/linux-4.1.27/Documentation/sound/alsa/soc/
Ddapm.txt294 5.1 Event types
/linux-4.1.27/drivers/input/joystick/
DKconfig286 and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
/linux-4.1.27/Documentation/thermal/
Dsysfs-api.txt363 4. Event Notification
/linux-4.1.27/drivers/message/fusion/
Dmptbase.c644 event = le32_to_cpu(pEventReply->Event) & 0xFF; in mptbase_reply()
6315 pAck->Event = evnp->Event; in SendEventAck()
7280 event = le32_to_cpu(pEventReply->Event) & 0xFF; in mpt_display_event_info()
7741 event = le32_to_cpu(pEventReply->Event) & 0xFF; in ProcessEventNotification()
Dmptfc.c1372 u8 event = le32_to_cpu(pEvReply->Event) & 0xFF; in mptfc_event_process()
Dmptspi.c1178 u8 event = le32_to_cpu(pEvReply->Event) & 0xFF; in mptspi_event_process()
Dmptlan.c349 switch (le32_to_cpu(pEvReply->Event)) { in mpt_lan_event_process()
Dmptctl.c557 event = le32_to_cpu(pEvReply->Event) & 0xFF; in mptctl_event_process()
Dmptscsih.c2588 u8 event = le32_to_cpu(pEvReply->Event) & 0xFF; in mptscsih_event_process()
Dmptsas.c4981 u32 event = le32_to_cpu(reply->Event); in mptsas_event_process()
/linux-4.1.27/drivers/scsi/mpt2sas/
Dmpt2sas_base.c577 event = le16_to_cpu(mpi_reply->Event); in _base_display_event_data()
814 ack_request->Event = mpi_reply->Event; in _base_async_event()
Dmpt2sas_ctl.c361 event = le16_to_cpu(mpi_reply->Event); in mpt2sas_ctl_add_to_event_log()
Dmpt2sas_scsih.c4403 event_reply->Event = in _scsih_smart_predicted_fault()
7508 event = le16_to_cpu(mpi_reply->Event); in mpt2sas_scsih_event_callback()
/linux-4.1.27/Documentation/PCI/
Dpci-error-recovery.txt115 STEP 0: Error Event
/linux-4.1.27/Documentation/filesystems/
Dspufs.txt168 event_mask Event mask for SPU interrupts
/linux-4.1.27/Documentation/s390/
Ds390dbf.txt69 The default level is 3. Event and Exception functions have a 'level'
DDebugging390.txt85 1 1 Program Event Recording 1 PER enabled,
/linux-4.1.27/drivers/input/keyboard/
DKconfig508 tristate "Generic Input Event device for Goldfish"
/linux-4.1.27/drivers/char/
DKconfig519 bool "HPET - High Precision Event Timer" if (X86 || IA64)
/linux-4.1.27/sound/pci/
DKconfig623 Hoontech SoundTrack DSP 24/Value/Media7.1; Event EZ8;
/linux-4.1.27/Documentation/power/
Dpci.txt252 pass through root ports, but instead they cause a Root Complex Event Collector
/linux-4.1.27/arch/arm/
DKconfig1011 Event (WFE) IDLE states, a specific timing sensitivity exists between
/linux-4.1.27/init/
DKconfig1629 The Linux Performance Event subsystem provides an abstraction of
/linux-4.1.27/Documentation/sound/alsa/
DALSA-Configuration.txt1013 * Event Electronics, EZ8
/linux-4.1.27/arch/x86/
DKconfig731 Use the IA-PC HPET (High Precision Event Timer) to manage
/linux-4.1.27/
DMAINTAINERS4699 HPET: High Precision Event Timers driver