Home
last modified time | relevance | path

Searched refs:event (Results 1 – 25 of 188) sorted by relevance

12345678

/Documentation/trace/
Devents.txt11 using the event tracing infrastructure.
13 Not all tracepoints can be traced using the event tracing system;
27 To enable a particular event, such as 'sched_wakeup', simply echo it
35 To disable an event, echo the event name to the set_event file prefixed
49 etc., and a full event name looks like this: <subsystem>:<event>. The
63 To enable event 'sched_wakeup':
84 ? - this file does not affect any event
91 trace_event=[event-list]
93 event-list is a comma separated list of events. See section 2.1 for event
96 3. Defining an event-enabled tracepoint
[all …]
Dkprobetrace.txt12 functions). Unlike the Tracepoint based event, this can be added and removed
30 EVENT : Event name. If omitted, the event name is generated
68 Per-probe event filtering feature allows you to set different filter on each
69 probe and gives you what arguments will be shown in trace buffer. If an event
70 name is specified right after 'p:' or 'r:' in kprobe_events, it adds an event
78 This shows the format of this probe event.
81 You can write filtering rules of this event.
84 This shows the id of this probe event.
91 The first column is event name, the second is the number of probe hits,
97 To add a probe as a new event, write a new definition to kprobe_events
[all …]
Dtracepoint-analysis.txt10 creating custom kernel modules to register probe functions using the event
44 ext4:ext4_free_inode [Tracepoint event]
45 ext4:ext4_request_inode [Tracepoint event]
46 ext4:ext4_allocate_inode [Tracepoint event]
47 ext4:ext4_write_begin [Tracepoint event]
48 ext4:ext4_ordered_write_end [Tracepoint event]
146 performance analyst to do it by hand. In the event that the discrete event
165 In the event that some higher-level event is required that depends on some
191 o Reading information from /proc for the PID that triggered the event
192 o Deriving a higher-level event from a series of lower-level events.
[all …]
Devents-kmem.txt35 it is likely easier to pin the event down to a specific cache. At the time
51 mm_page_alloc_zone_locked event is triggered. This event is important as high
56 When a page is freed directly by the caller, the only mm_page_free event
76 the zone->lock will be taken once and the per-CPU list refilled. The event
78 event indicating whether it is for a percpu_refill or not.
81 which triggers a mm_page_pcpu_drain event.
103 Large numbers of this event implies that memory is fragmenting and
105 means of reducing the occurrence of this event is to increase the size of
Devents-power.txt23 A 'cpu' event class gathers the CPU-related events: cpuidle and
29 A suspend event is used to indicate the system going in and out of the
40 The event which has 'state=4294967295' in the trace is very important to the user
67 power_start event.
/Documentation/timers/
Dhighres.txt17 Note: the paper and the slides are talking about "clock event source", while we
18 switched to the name "clock event devices" in meantime.
24 - clock event management
66 clock event management
70 value, clock event devices are used to schedule the next event
71 interrupt(s). The next event is currently defined to be periodic, with its
72 period defined at compile time. The setup and selection of the event device
73 for various event driven functionalities is hardwired into the architecture
76 event interrupt devices other than those already built into the
82 solution to manage clock event devices and their usage for the various clock
[all …]
/Documentation/hid/
Duhid.txt51 The "type" field contains the ID of the event. Depending on the ID different
52 payloads are sent. You must not split a single event across multiple read()'s or
53 multiple write()'s. A single event must always be sent as a whole. Furthermore,
54 only a single event can be sent per read() or write(). Pending data is ignored.
58 The first thing you should do is sending an UHID_CREATE event. This will
59 register the device. UHID will respond with an UHID_START event. You can now
61 UHID_OPEN event, the internally attached HID Device Driver has no user attached.
63 event. If you receive the UHID_OPEN event, you should start I/O. If the last
64 user closes the HID device, you will receive an UHID_CLOSE event. This may be
65 followed by an UHID_OPEN event again and so on. There is no need to perform
[all …]
/Documentation/input/
Devent-codes.txt5 A single hardware event generates multiple input events. Each input event
6 contains the new value of a single data item. A special event type, EV_SYN, is
8 the same moment in time. In the following, the term "event" refers to a single
9 input event encompassing a type, code, and value.
12 of event codes have changed. However, the state is maintained within the Linux
15 event code values using the EVIOCG* ioctls defined in linux/input.h. The event
17 class/input/event*/device/capabilities/, and the properties of a device are
18 provided in class/input/event*/device/properties.
68 Event codes define the precise type of event.
72 EV_SYN event values are undefined. Their usage is defined only by when they are
[all …]
Dnotifier.txt7 - 'vc' always provide the VC for which the keyboard event applies;
8 - 'down' is 1 for a key press event, 0 for a key release;
10 - 'value' depends on the type of event.
22 For each kind of event but the last, the callback may return NOTIFY_STOP in
23 order to "eat" the event: the notify loop is stopped and the keyboard event is
Dmulti-touch-protocol.txt19 describes how to send updates for individual contacts via event slots.
33 event, which instructs the receiver to accept the data for the current
38 This generates an ABS_MT_SLOT event, which instructs the receiver to
54 surface. The order in which the packets appear in the event stream is not
65 end. Upon receiving an MT event, one simply updates the appropriate
74 a BTN_TOOL_*TAP event to inform userspace of the total number of contacts
76 explicitly sending the corresponding BTN_TOOL_*TAP event and setting
80 by noting that the largest supported BTN_TOOL_*TAP event is larger than the
90 Here is what a minimal event sequence for a two-contact touch would look
118 ABS_MT events, the last SYN_MT_REPORT event may be omitted. Otherwise, the
[all …]
Djoystick-api.txt31 __u32 time; /* event timestamp in milliseconds */
33 __u8 type; /* event type */
38 you wanted to read more than one event per read as described in section 3.1.
51 events on open. That is, if it's issuing a INIT BUTTON event, the
66 generated the event. Note that they carry separate numeration (that
89 For a button, ``value'' for a press button event is 1 and for a release
90 button event is 0.
115 The time an event was generated is stored in ``js_event.time''. It's a time
125 wait) forever until an event is generated and effectively read. There
169 If time between reads is enough to fill the queue and lose an event,
[all …]
/Documentation/usb/
Ddwc3.txt23 goes through every event and calls generic_handle_irq() for event
24 it. On return from generic_handle_irq() in acknowledges the event
31 reads the event and tries to process it. Everything that requries
32 sleeping is handed over to the Thread. The event is saved in an
35 handed something to thread so we don't process event X prio Y
Dusbmon.txt105 URB callback, submission error. Every event is a text line, which consists
107 on the event type, but there is a set of words, common for all types.
119 - Event Type. This type refers to the format of the event, not URB type.
157 If an Isochronous transfer event has a set of descriptors, a total number
195 only the events are delivered in binary format. Each event is sent in
241 This call returns the length of data in the next event. Note that majority of
275 then return the first event. The argument is a pointer to the following
285 pointed by hdr contains the next event structure, and the data buffer contains
286 the data, if any. The event is removed from the kernel buffer.
306 Second, it waits for an event to be present in the buffer, unless the pseudo-
[all …]
/Documentation/device-mapper/
Ddm-uevent.txt4 is the event contains environment attributes providing increased context for
5 the event avoiding the need to query the state of the device-mapper device after
6 the event is received.
9 listed creates the event and the second function sends the event(s).
23 Value: Name of device-mapper target that generated the event.
43 event.
/Documentation/ptp/
Dtestptp.c126 struct ptp_extts_event event; in main() local
293 cnt = read(fd, &event, sizeof(event)); in main()
294 if (cnt != sizeof(event)) { in main()
298 printf("event index %u at %lld.%09u\n", event.index, in main()
299 event.t.sec, event.t.nsec); in main()
/Documentation/infiniband/
Dcore_locking.txt70 allowed for a low-level driver to call a consumer's completion event
76 completion event handlers for the same CQ are not called
77 simultaneously. The driver must guarantee that only one CQ event
84 consumer CQ event callback:
88 /* ... */ consumer CQ event callback:
90 return from CQ event handler
92 The context in which completion event and asynchronous event
/Documentation/hwmon/
Dacpi_power_meter28 When both of them are set, an ACPI event will be broadcast on the ACPI netlink
38 average power consumption exceeds the cap, an ACPI event will be broadcast on
39 the netlink event socket and a poll notification will be sent to the
45 all cases the ACPI event will be broadcast on the ACPI netlink event socket as
/Documentation/video4linux/
DREADME.ir33 Using the event devices (CONFIG_INPUT_EVDEV) it is possible for
34 applications to access the remote via /dev/input/event<n> devices.
36 input". The input layer tools mentioned above use the event device.
49 linux input layer (via event device). The input layer tools tarball
Domap3isp.txt70 The OMAP 3 ISP driver does support the V4L2 event interface on CCDC and
73 The CCDC subdev produces V4L2_EVENT_FRAME_SYNC type event on HS_VS
75 driver used V4L2_EVENT_OMAP3ISP_HS_VS for this purpose. The event is
77 in the CCDC module. The event can be subscribed on the CCDC subdev.
83 Each of the statistics subdevs is able to produce events. An event is
92 The type of the event data is struct omap3isp_stat_event_status for these
94 event as usual, but no related statistics buffer. In this case
244 user application receives an event for buffer availability or when a new
/Documentation/filesystems/
Dinotify.txt57 You can find the size of the current event queue via the standard FIONREAD
75 event callback.
91 mask - describes the event that occurred
93 name - the dentry name for affected files in a directory-based event
94 inode - the affected inode in a directory-based event
99 structure and specifying the inode to watch along with an inotify event mask.
130 Call inotify_find_update_watch() to update the event mask for an existing watch.
142 A watch may be removed while executing your event handler with the following:
152 When inotify removes a watch, it sends an IN_IGNORED event to your callback.
153 You may use this event as an indication to free the watch memory. Note that
[all …]
/Documentation/networking/
Dxfrm_sync.txt69 message (kernel<->user) as well the cause (config, query or event).
73 (0 to the kernel and pid = processid that created the event
84 last event.
88 last event.
138 In the case of success, additionally an event with
146 iii) kernel->user to report as event if someone sets any values or
152 iv) kernel->user to report event when replay threshold or a timeout
/Documentation/sound/alsa/soc/
Ddapm.txt140 static int spitz_mic_bias(struct snd_soc_dapm_widget* w, int event)
142 gpio_set_value(SPITZ_GPIO_MIC_BIAS, SND_SOC_DAPM_EVENT_ON(event));
152 The codec power domain has no widgets and is handled by the codecs DAPM event
154 stream event or by kernel PM events.
270 static int corgi_amp_event(struct snd_soc_dapm_widget *w, int event)
272 gpio_set_value(CORGI_GPIO_APM_ON, SND_SOC_DAPM_EVENT_ON(event));
286 The following event types are supported by event widgets.
288 /* dapm event types */
/Documentation/ABI/testing/
Dsysfs-firmware-acpi41 Or the handler may send send a Notify event
117 doesn't have an event handler.
138 Fixed Event with event handler installed.
140 Let's take power button fixed event for example, please kill acpid
159 * and it triggers an ACPI fixed event when the enable bit is set again
/Documentation/devicetree/bindings/input/
Dsamsung-keypad.txt7 event using a interrupt to the cpu.
46 - linux,keypad-wakeup: use any event on keypad as wakeup event.
/Documentation/video4linux/cx2341x/
Dfw-memory.txt126 28 Encoder Video Input Module reset event
128 24 Decoder audio mode change detection event (through event notification)
139 Decoder VTRACE event

12345678