Searched full:event (Results 1 – 25 of 647) sorted by relevance
12345678910>>...26
| /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.
40 As performance monitoring event names are case
42 for lower or upper case event names in sysfs to avoid
44 name of the event here is either lower or upper case.
58 event=0x2abc
59 event=0x423,inv,cmask=0x3
[all …]
|
| /Documentation/trace/ |
| 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.enable
[all …]
|
| 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 | user_events.rst | 2 user_events: User-based Event Tracing
20 requires CAP_PERFMON due to the event persisting, otherwise -EPERM is returned.
25 enabled the event and data should be written. The registration will give back
59 /* Input: Pointer to string with event name, description and flags */
62 /* Output: Index of the event to use when writing data */
70 + enable_bit: The bit to reflect the event status at the address specified by
82 + enable_addr: The address of the value to use to reflect event status. This
85 + name_args: The name and arguments to describe the event, see command format
90 + USER_EVENT_REG_PERSIST: The event will not delete upon the last reference
91 closing. Callers may use this if an event should exist even after the
[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/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, because uprobe
[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
52 - Type of the event, see :ref:`event-type`.
57 - Event data for event ``V4L2_EVENT_VSYNC``.
60 - Event data for event ``V4L2_EVENT_CTRL``.
63 - Event data for event ``V4L2_EVENT_FRAME_SYNC``.
66 - Event data for event V4L2_EVENT_MOTION_DET.
69 - Event data for event V4L2_EVENT_SOURCE_CHANGE.
72 - Event data. Defined by the event type. The union should be used to
81 - 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/devicetree/bindings/net/wireless/ |
| D | qcom,ath11k.yaml | 109 - description: interrupt event for ring CE0
110 - description: interrupt event for ring CE1
111 - description: interrupt event for ring CE2
112 - description: interrupt event for ring CE3
113 - description: interrupt event for ring CE4
114 - description: interrupt event for ring CE5
115 - description: interrupt event for ring CE6
116 - description: interrupt event for ring CE7
117 - description: interrupt event for ring CE8
118 - description: interrupt event for ring CE9
[all …]
|
| /Documentation/arch/x86/x86_64/ |
| D | fred.rst | 4 Flexible Return and Event Delivery (FRED)
14 1) Improve overall performance and response time by replacing event
15 delivery through the interrupt descriptor table (IDT event
16 delivery) and event return by the IRET instruction with lower
19 2) Improve software robustness by ensuring that event delivery
20 establishes the full supervisor context and that event return
23 The new transitions defined by the FRED architecture are FRED event
25 FRED event delivery can effect a transition from ring 3 to ring 0, but
29 event delivery and the FRED return instructions are FRED transitions.
39 Software based event dispatching
[all …]
|
| /Documentation/arch/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/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/devicetree/bindings/perf/ |
| D | riscv,pmu.yaml | 18 The platform must provide information about PMU event to counter mappings
20 Without the event to counter mappings, the SBI PMU extension cannot be used.
22 Platforms should provide information about the PMU event selector values
24 MHPMCOUNTERx for that specific event. The can either be done via device tree
37 riscv,event-to-mhpmevent:
40 Represents an ONE-to-ONE mapping between a PMU event and the event
42 CSR for that event.
44 an event.
45 This property shouldn't encode any raw hardware event.
48 - description: event_idx, a 20-bit wide encoding of the event type and
[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/admin-guide/perf/ |
| D | starfive_starlink_pmu.rst | 10 event counters, and an independent 64bit cycle counter.
23 Driver describes the format of config (event ID) in sysfs "format" directory
32 starfive_starlink_pmu/cycles/ [Kernel PMU event]
33 starfive_starlink_pmu/read_hit/ [Kernel PMU event]
34 starfive_starlink_pmu/read_miss/ [Kernel PMU event]
35 starfive_starlink_pmu/read_request/ [Kernel PMU event]
36 starfive_starlink_pmu/release_request/ [Kernel PMU event]
37 starfive_starlink_pmu/write_hit/ [Kernel PMU event]
38 starfive_starlink_pmu/write_miss/ [Kernel PMU event]
39 starfive_starlink_pmu/write_request/ [Kernel PMU event]
[all …]
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | mediatek,gce-props.yaml | 30 GCE has an event table in SRAM, consisting of 1024 event IDs (0~1023).
31 Each event ID has a boolean event value with the default value 0.
32 The property mediatek,gce-events is used to obtain the event IDs.
35 send an event signal to GCE, setting the value of event ID 597 to 1.
36 Similarly, in MT8188, the value of event ID 574 will be set to 1 when
40 event ID 855, which is not bound to any hardware, to 1 when the driver
41 in the secure world completes a task. However, in MT8195, event ID 855
42 is already bound to VDEC_LAT1, so we need to select another event ID to
43 achieve the same purpose. This event ID can be any ID that is not bound
45 To determine if the event ID is bound to the hardware or used by a
|
| /Documentation/devicetree/bindings/devfreq/event/ |
| D | samsung,exynos-ppmu.yaml | 4 $id: http://devicetree.org/schemas/devfreq/event/samsung,exynos-ppmu.yaml#
19 Exynos PPMU driver uses the devfreq-event class to provide event data to
20 various devfreq devices. The devfreq devices would use the event data when
43 '^ppmu-event[0-9]+(-[a-z0-9]+){,2}$':
46 event-name:
48 The unique event name among PPMU device
51 event-data-type:
61 - event-name
84 event-name = "ppmu-event3-dmc0";
88 event-name = "ppmu-event2-dmc0";
[all …]
|
| /Documentation/tools/rtla/ |
| D | common_options.rst | 17 **-e**, **--event** *sys:event*
19 …Enable an event in the trace (**-t**) session. The argument can be a specific event, e.g., **-e** …
23 …*sys:event* event with *<filter>*. For further information about event filtering see https://www.k…
26 Enable a trace event trigger to the previous **-e** *sys:event*.
32 …cally save the content of the histogram associated to *osnoise:irq_noise* event in *osnoise_irq_no…
34 …For further information about event trigger see https://www.kernel.org/doc/html/latest/trace/event…
|
| /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 send a UHID_CREATE2 event. This will
49 register the device. UHID will respond with a 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 a UHID_CLOSE event. This may be
55 followed by a 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 …]
|
| /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 …]
|
12345678910>>...26