Searched full:event (Results 1 – 25 of 494) sorted by relevance
12345678910>>...20
| /Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-dfl_fme | 13 event = "config:0-11" - event ID
14 evtype = "config:12-15" - event type
15 portid = "config:16-23" - event source
19 fab_mmio_read = "event=0x06,evtype=0x02,portid=0xff"
21 It shows this fab_mmio_read is a fabric type (0x02) event with
22 0x06 local event id for overall monitoring (portid=0xff).
37 a single performance monitoring event supported by this fme pmu.
38 The name of the file is the name of the event.
45 clock = "event=0x00,evtype=0x00,portid=0xff"
49 cache_read_hit = "event=0x00,evtype=0x01,portid=0xff"
[all …]
|
| D | sysfs-class-devfreq-event | 1 What: /sys/class/devfreq-event/event(x)/
5 Provide a place in sysfs for the devfreq-event objects.
6 This allows accessing various devfreq-event specific variables.
7 The name of devfreq-event object denoted as 'event(x)' which
8 includes the unique number of 'x' for each devfreq-event object.
10 What: /sys/class/devfreq-event/event(x)/name
14 The /sys/class/devfreq-event/event(x)/name attribute contains
15 the name of the devfreq-event object. This attribute is
18 What: /sys/class/devfreq-event/event(x)/enable_count
22 The /sys/class/devfreq-event/event(x)/enable_count attribute
[all …]
|
| D | sysfs-bus-event_source-devices-events | 23 event=0xNNNN
26 "raw code" for the perf event identified by the file's
30 What: /sys/bus/event_source/devices/<pmu>/events/<event>
37 performance monitoring event supported by the <pmu>. The name
38 of the file is the name of the event.
52 event=0x2abc
53 event=0x423,inv,cmask=0x3
63 need to be provided by the user selecting the particular event.
64 This is referred to as "event parameterization". Event
67 What: /sys/bus/event_source/devices/<pmu>/events/<event>.unit
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-event.rst | 6 Event Interface
9 The V4L2 event interface provides a means for a user to get immediately
18 an event is subscribed, the events of subscribed types are dequeueable
20 unsubscribed using VIDIOC_UNSUBSCRIBE_EVENT ioctl. The special event
24 The event subscriptions and event queues are specific to file handles.
25 Subscribing an event on one file handle does not affect other file
35 1. Each subscribed event has its own internal dedicated event queue.
36 This means that flooding of one event type will not interfere with
37 other event types.
39 2. If the internal event queue for a particular subscribed event becomes
[all …]
|
| D | vidioc-dqevent.rst | 13 VIDIOC_DQEVENT - Dequeue event
34 Dequeue an event from a video device. No input is required for this
53 - Type of the event, see :ref:`event-type`.
58 - Event data for event ``V4L2_EVENT_VSYNC``.
61 - Event data for event ``V4L2_EVENT_CTRL``.
64 - Event data for event ``V4L2_EVENT_FRAME_SYNC``.
67 - Event data for event V4L2_EVENT_MOTION_DET.
70 - Event data for event V4L2_EVENT_SOURCE_CHANGE.
73 - Event data. Defined by the event type. The union should be used to
82 - Event sequence number. The sequence number is incremented for
[all …]
|
| D | vidioc-subscribe-event.rst | 14 VIDIOC_SUBSCRIBE_EVENT - VIDIOC_UNSUBSCRIBE_EVENT - Subscribe or unsubscribe event
39 Subscribe or unsubscribe V4L2 event. Subscribed events are dequeued by
53 - Type of the event, see :ref:`event-type`.
62 - ID of the event source. If there is no ID associated with the
63 event source, then set this to 0. Whether or not an event needs an
64 ID depends on the event type.
67 - Event flags, see :ref:`event-flags`.
78 .. flat-table:: Event Flags
85 - When this event is subscribed an initial event will be sent
97 another, and then receives an event telling it that that control
[all …]
|
| /Documentation/powerpc/ |
| D | pmu-ebb.rst | 2 PMU Event Based Branches
5 Event Based Branches (EBBs) are a feature which allows the hardware to
12 One type of event for which EBBs can be configured is PMU exceptions. This
20 Throughout this document we will refer to an "EBB event" or "EBB events". This
39 and attach an EBB event to the process, which will then cause EBBs to be
44 user process. This means once an EBB event is scheduled on the PMU, no non-EBB
49 kernel will in general schedule the EBB event, and perf will be notified that
55 If an EBB event and a regular event are both pinned, then whichever is enabled
57 section below titled "Enabling an EBB event" for more information.
60 Creating an EBB event
[all …]
|
| D | imc.rst | 30 and passes on to the kernel via the device tree. The event's information
33 - Event name
34 - Event Offset
35 - Event description
39 - Event scale
40 - Event unit
46 The event offset in the memory is where the counter data gets accumulated.
54 and their event's information and register the PMU and its attributes in the
64 nest_mcs01/PM_MCS01_64B_RD_DISP_PORT01/ [Kernel PMU event]
65 nest_mcs01/PM_MCS01_64B_RD_DISP_PORT23/ [Kernel PMU event]
[all …]
|
| /Documentation/devicetree/bindings/net/wireless/ |
| D | qcom,ath11k.yaml | 33 - description: interrupt event for ring CE0
34 - description: interrupt event for ring CE1
35 - description: interrupt event for ring CE2
36 - description: interrupt event for ring CE3
37 - description: interrupt event for ring CE4
38 - description: interrupt event for ring CE5
39 - description: interrupt event for ring CE6
40 - description: interrupt event for ring CE7
41 - description: interrupt event for ring CE8
42 - description: interrupt event for ring CE9
[all …]
|
| /Documentation/driver-api/media/ |
| D | v4l2-event.rst | 9 Events are subscribed per-filehandle. An event specification consists of a
11 ``id`` field. If unused, then the ``id`` is 0. So an event is uniquely
17 When the user subscribes to an event, a :c:type:`v4l2_subscribed_event`
19 subscribed event.
26 So every ``(type, ID)`` event tuple will have its own
32 :c:type:`v4l2_kevent` ringbuffer, then the oldest event will be dropped
37 know which event to dequeue first.
39 Finally, if the event subscription is associated with a particular object
41 so that an event can be raised by that object. So the ``node`` field can
56 event to that object.
[all …]
|
| /Documentation/trace/ |
| D | events.rst | 2 Event Tracing
13 using the event tracing infrastructure.
15 Not all tracepoints can be traced using the event tracing system;
20 2. Using Event Tracing
29 To enable a particular event, such as 'sched_wakeup', simply echo it
36 To disable an event, echo the event name to the set_event file prefixed
50 etc., and a full event name looks like this: <subsystem>:<event>. The
64 To enable event 'sched_wakeup'::
85 - ? - this file does not affect any event
92 trace_event=[event-list]
[all …]
|
| D | boottime-trace.rst | 13 device initialization with full features of ftrace including per-event
37 Output trace-event data on printk buffer too.
66 (you can enable it by the "traceon" event trigger action)
81 ftrace.[instance.INSTANCE.]events = EVENT[, EVENT2[...]]
82 Enable given events on boot. You can use a wild card in EVENT.
94 Ftrace Per-Event Options
97 These options are setting per-event options.
99 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.enable
100 Enable GROUP:EVENT tracing.
102 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.filter = FILTER
[all …]
|
| D | uprobetracer.rst | 2 Uprobe-tracer: Uprobe-based Event Tracing
13 Similar to the kprobe-event tracer, this doesn't need to be activated via
16 /sys/kernel/debug/tracing/events/uprobes/<EVENT>/enable.
18 However unlike kprobe-event tracer, the uprobe event interface expects the
29 p[:[GRP/]EVENT] PATH:OFFSET [FETCHARGS] : Set a uprobe
30 r[:[GRP/]EVENT] PATH:OFFSET [FETCHARGS] : Set a return uprobe (uretprobe)
31 p[:[GRP/]EVENT] PATH:OFFSET%return [FETCHARGS] : Set a return uprobe (uretprobe)
32 -:[GRP/]EVENT : Clear uprobe or uretprobe event
35 EVENT : Event name. If omitted, the event name is generated based
58 (\*3) Unlike kprobe event, "u" prefix will just be ignored, becuse uprobe
[all …]
|
| D | kprobetrace.rst | 2 Kprobe-based Event Tracing
13 Unlike the Tracepoint based event, this can be added and removed
21 /sys/kernel/debug/tracing/events/kprobes/<EVENT>/enable.
31 p[:[GRP/]EVENT] [MOD:]SYM[+offs]|MEMADDR [FETCHARGS] : Set a probe
32 r[MAXACTIVE][:[GRP/]EVENT] [MOD:]SYM[+0] [FETCHARGS] : Set a return probe
33 p:[GRP/]EVENT] [MOD:]SYM[+0]%return [FETCHARGS] : Set a return probe
34 -:[GRP/]EVENT : Clear a probe
37 EVENT : Event name. If omitted, the event name is generated
117 Note that kprobe-event provides the user-memory access syntax but it doesn't
122 Per-Probe Event Filtering
[all …]
|
| /Documentation/timers/ |
| D | highres.rst | 18 Note: the paper and the slides are talking about "clock event source", while we
19 switched to the name "clock event devices" in meantime.
25 - clock event management
69 clock event management
73 value, clock event devices are used to schedule the next event
74 interrupt(s). The next event is currently defined to be periodic, with its
75 period defined at compile time. The setup and selection of the event device
76 for various event driven functionalities is hardwired into the architecture
79 event interrupt devices other than those already built into the
85 solution to manage clock event devices and their usage for the various clock
[all …]
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-ioc-dqevent.rst | 13 CEC_DQEVENT - Dequeue a CEC event
35 non-blocking mode and no event is pending, then it will return -1 and
38 The internal event queues are per-filehandle and per-event type. If
39 there is no more room in a queue then the last event is overwritten with
41 that the latest event is always available. This also means that is it
43 two :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` events with
87 or since the last time this event was dequeued for this
107 - Timestamp of the event in ns.
113 - ``event``
114 - The CEC event type, see :ref:`cec-events`.
[all …]
|
| /Documentation/devicetree/bindings/devfreq/event/ |
| D | exynos-ppmu.txt | 9 The Exynos PPMU driver uses the devfreq-event class to provide event data
10 to various devfreq devices. The devfreq devices would use the event data when
22 - event-name : the unique event name among PPMU device
24 - event-data-type : Define the type of data which shell be counted
73 event-name = "ppmu-event3-dmc0";
77 event-name = "ppmu-event2-dmc0";
81 event-name = "ppmu-event1-dmc0";
85 event-name = "ppmu-event0-dmc0";
95 event-name = "ppmu-event3-dmc1";
105 event-name = "ppmu-event3-leftbus";
[all …]
|
| /Documentation/hid/ |
| D | uhid.rst | 38 The "type" field contains the ID of the event. Depending on the ID different
39 payloads are sent. You must not split a single event across multiple read()'s or
40 multiple write()'s. A single event must always be sent as a whole. Furthermore,
41 only a single event can be sent per read() or write(). Pending data is ignored.
48 The first thing you should do is sending an UHID_CREATE2 event. This will
49 register the device. UHID will respond with an UHID_START event. You can now
51 UHID_OPEN event, the internally attached HID Device Driver has no user attached.
53 event. If you receive the UHID_OPEN event, you should start I/O. If the last
54 user closes the HID device, you will receive an UHID_CLOSE event. This may be
55 followed by an UHID_OPEN event again and so on. There is no need to perform
[all …]
|
| /Documentation/input/ |
| D | event-codes.rst | 1 .. _input-event-codes:
4 Input event codes
12 A single hardware event generates multiple input events. Each input event
13 contains the new value of a single data item. A special event type, EV_SYN, is
15 the same moment in time. In the following, the term "event" refers to a single
16 input event encompassing a type, code, and value.
19 of event codes have changed. However, the state is maintained within the Linux
22 event code values using the EVIOCG* ioctls defined in linux/input.h. The event
24 class/input/event*/device/capabilities/, and the properties of a device are
25 provided in class/input/event*/device/properties.
[all …]
|
| D | notifier.rst | 9 - 'vc' always provide the VC for which the keyboard event applies;
10 - 'down' is 1 for a key press event, 0 for a key release;
12 - 'value' depends on the type of event.
24 For each kind of event but the last, the callback may return NOTIFY_STOP in
25 order to "eat" the event: the notify loop is stopped and the keyboard event is
|
| /Documentation/mhi/ |
| D | mhi.rst | 40 Event Doorbell array: Associated with event context array, the Event Doorbell
61 Event context array: All event configurations are organized in the event context
64 Event rings: Used by the device to send completion and state transition messages
113 Event rings
116 Events from the device to host are organized in event rings and defined by Event
117 Descriptors (ED). Event rings are used by the device to report events such as
119 to the host. Event rings are the array of EDs that resides in the host
128 Below is the basic usage of event rings:
130 * Host allocates memory for event ring.
136 * When there is a new event the device needs to send, the device updates ED
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe-get-event.rst | 31 Points to the location where the event, if any, is to be stored.
36 This ioctl call returns a frontend event if available. If an event is
40 an event becomes available.
58 - There is no event pending, and the device is in non-blocking mode.
64 - Overflow in event queue - one or more events were lost.
|
| /Documentation/riscv/ |
| D | pmu.rst | 62 2. Event Initialization
71 The main purpose of this function is to translate the event provided by user
84 if (!is_sampling_event(event)) {
123 *release_pmc_hardware* serves the opposite purpose, and it is used in event
128 It does NOT deal with the binding between an event and a physical counter,
137 get the event of this counter
142 update the event->count (# event occurs) by adding delta, and
143 event->hw.period_left by subtracting delta
145 if the event overflows
149 if the event overflows again
[all …]
|
| /Documentation/usb/ |
| D | dwc3.rst | 30 goes through every event and calls generic_handle_irq() for event
31 it. On return from generic_handle_irq() in acknowledges the event
38 reads the event and tries to process it. Everything that requires
39 sleeping is handed over to the Thread. The event is saved in an
42 handed something to thread so we don't process event X prio Y
|
| /Documentation/s390/ |
| D | qeth.rst | 17 event with ACTION=CHANGE is emitted on behalf of the corresponding
18 ccwgroup device. The event has the following attributes:
31 notifications enabled, a udev event with ACTION=CHANGE is emitted.
34 The event has the following attributes:
43 VLAN ID on which the event occurred. Not included
44 if no VLAN is involved in the event.
49 event reports the creation or destruction of a VLAN.
|
12345678910>>...20