Searched full:handler (Results 1 – 25 of 252) sorted by relevance
1234567891011
| /Documentation/RCU/ |
| D | NMI-RCU.rst | 21 The dummy_nmi_callback() function is a "dummy" NMI handler that does
23 the NMI handler to take the default machine-specific action::
28 NMI handler::
47 count of NMIs. It then invokes the NMI handler stored in the nmi_callback
48 function pointer. If this handler returns zero, do_nmi() invokes the
70 The set_nmi_callback() function registers an NMI handler. Note that any
73 writes, the rcu_assign_pointer() ensures that the NMI handler sees the
81 This function unregisters an NMI handler, restoring the original
82 dummy_nmi_handler(). However, there may well be an NMI handler
84 up any data structures used by the old NMI handler until execution
[all …]
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | restart-handler.yaml | 4 $id: http://devicetree.org/schemas/power/reset/restart-handler.yaml#
7 title: Restart and shutdown handler Common Properties
13 Restart and shutdown handler device is responsible for powering off the
22 0:: Restart handler of last resort, with limited restart capabilities.
23 128:: Typical, default restart handler; use if no other restart handler
26 255:: Highest priority restart handler, will preempt all other restart handlers.
|
| D | gpio-restart.yaml | 13 Drive a GPIO line that can be used to restart the system from a restart handler.
16 request the given gpio line and install a restart handler. If the optional properties
20 When the system is restarted, the restart handler will be invoked in priority order. The GPIO
26 restart handler completes allowing other restart handlers to be attempted.
29 - $ref: restart-handler.yaml#
|
| /Documentation/arch/arm/ |
| D | interrupts.rst | 39 SA1111 IRQ handler, SA1111 IRQs can hold off SMC9196 IRQs indefinitely.
45 to the Neponset handler, the "parent" is GPIO25, and the "children"d
90 the hardware IRQ if possible. If not, may call the handler
104 - per-IRQ handler
107 The handler can be one of the 3 standard handlers - "level", "edge" and
108 "simple", or your own specific handler if you need to do something special.
110 The "level" handler is what we currently have - its pretty simple.
114 "simple" handler is very basic, and does not perform any hardware
131 set_irq_handler(irq,handler)
132 Set the handler for this IRQ (level, edge, simple)
[all …]
|
| /Documentation/usb/ |
| D | dwc3.rst | 11 - Convert interrupt handler to per-ep-thread-irq
27 - the interrupt handler is split into the following pieces:
29 - primary handler of the device
34 - threaded handler of the device
37 - primary handler of the EP-interrupt
45 - threaded handler of the EP-interrupt
|
| /Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 48 where ids is the list of IDs of device nodes the given handler is supposed to
52 unregistration of device nodes the handler attached to previously.
56 to match a scan handler against each of them using the ids arrays of the
57 available scan handlers. If a matching scan handler is found, its .attach()
59 that means that the handler has claimed the device node and is now responsible
62 The device node's handler field is then populated with the address of the scan
63 handler that has claimed it.
66 interesting to the given scan handler and may be matched against the next scan
67 handler in the list. If it returns a (negative) error code, that means that
78 handler as an argument. The order in which scan handlers are added to the list
|
| /Documentation/netlink/specs/ |
| D | handshake.yaml | 17 name: handler-class
48 name: handler-class
50 enum: handler-class
96 doc: Handler retrieves next queued handshake request
102 - handler-class
114 doc: Handler reports handshake completion
|
| /Documentation/core-api/ |
| D | genericirq.rst | 29 __do_IRQ() super-handler, which is able to deal with every type of
33 a quite universal set for the ARM interrupt handler implementation in
46 In the SMP world of the __do_IRQ() super-handler another type was
58 the flow control in the super-handler. This leads to a mix of flow logic
74 Each interrupt descriptor is assigned its own high-level flow handler,
76 flow handler implementation also makes it simple to provide
86 of existing implementations, the __do_IRQ() super-handler is still
219 Default flow handler implementations
222 Default Level IRQ flow handler
235 Default Fast EOI IRQ flow handler
[all …]
|
| /Documentation/driver-api/usb/ |
| D | URB.rst | 36 - Each URB has a completion handler, which is called after the action
38 context-pointer for passing information to the completion handler.
122 length, the completion handler, and its context. Take a look at the some
175 returns; you must still wait for the completion handler to be called.
182 until after the URB has been returned and the completion handler
184 that if the completion handler or anyone else tries to resubmit it
189 time, and the completion handler may free the URB. If this happens
196 completion handler, the handler must not take any lock that is held
208 by the completion handler.
211 What about the completion handler?
[all …]
|
| /Documentation/driver-api/media/ |
| D | v4l2-controls.rst | 57 1.1) Add the handler to your driver's top-level struct:
83 1.2) Initialize the handler:
90 handler is expected to handle. It will allocate a hashtable based on this
93 1.3) Hook the control handler into the driver:
107 1.4) Clean up the handler at the end:
235 This makes it easy to init the handler and just add all controls and only check
266 struct foo *state = container_of(ctrl->handler, struct foo, ctrl_handler);
396 by the same handler since the handler's lock is held. If you need to access
410 will result in a deadlock since these helpers lock the handler as well.
412 You can also take the handler lock yourself:
[all …]
|
| /Documentation/trace/ |
| D | events-nmi.rst | 17 INFO: NMI handler took too long to run: 9.207 msecs
23 you some problems and you only want to trace that handler
35 echo 'handler==0xffffffff81625600 && delta_ns>1000000' > filter
|
| D | kprobes.rst | 30 can trap at almost any kernel code address [1]_, specifying a handler
45 the probe is to be inserted and what handler is to be called when
71 associated with the kprobe, passing the handler the addresses of the
119 handler calls the user-specified return handler associated with the
142 Kretprobe entry-handler
145 Kretprobes also provides an optional user-specified handler which runs
146 on function entry. This handler is specified by setting the entry_handler
149 If the entry_handler returns 0 (success) then a corresponding return handler
154 Multiple entry and return handler invocations are matched using the unique
269 while the interrupt handler is running. When the interrupt
[all …]
|
| D | fprobe.rst | 16 instrumentation for multiple functions with single handler. This document
87 The fprobe entry/exit handler
98 Note that the @entry_ip is saved at function entry and passed to exit handler.
102 This is the address of `fprobe` data structure related to this handler.
136 handler from recursion in all cases. On the other hand, fprobe uses
138 call another (or same) fprobe while the fprobe user handler is running.
|
| D | boottime-trace.rst | 160 Set histogram 'onmatch' handler matching event parameter.
161 The 'M' is a digit string for the multiple 'onmatch' handler. You can omit it
162 if there is one 'onmatch' handler on this histogram.
170 Set histogram 'onmax' handler variable parameter.
173 Set histogram 'onchange' handler variable parameter.
176 Set histogram 'save' action parameters for 'onmax' or 'onchange' handler.
181 Set histogram 'snapshot' action for 'onmax' or 'onchange' handler.
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb-switch.yaml | 17 description: Possible handler of altmode switching
21 description: Possible handler of orientation switching
25 description: Possible handler of SuperSpeed signals retiming
|
| /Documentation/tools/rtla/ |
| D | common_timerlat_description.rst | 8 prints the timer latency at the timer *IRQ* handler and the *Thread*
9 handler. It also enable the trace of the most relevant information via
|
| /Documentation/PCI/ |
| D | boot-interrupts.rst | 30 trigger a new interrupt for which the OS likely lacks a handler. When an
65 handler wakes. These "one shot" conditions mean that the threaded interrupt
66 needs to keep the interrupt line masked until the threaded handler has run.
111 purposes of redirecting the interrupt handler to the rerouted interrupt
114 interrupt. This redirection of the handler will prevent the occurrence of
119 disable) the redirection of the interrupt handler to the PCH interrupt
143 Example of handler rerouting
|
| /Documentation/driver-api/gpio/ |
| D | driver.rst | 314 an SoC. This means that there is a fast IRQ flow handler for the GPIOs that
315 gets called in a chain from the parent IRQ handler, most typically the
316 system interrupt controller. This means that the GPIO irqchip handler will
319 sequence in its interrupt handler::
332 runtime) can't be used in a chained IRQ handler.
335 see below) a chained IRQ handler can be converted to generic irq handler and
336 this way it will become a threaded IRQ handler on -RT and a hard IRQ handler
340 so the IRQ core will complain if it is called from an IRQ handler which is
353 performed by generic IRQ handler which is configured using request_irq().
355 its interrupt handler::
[all …]
|
| /Documentation/arch/powerpc/ |
| D | pmu-ebb.rst | 122 EBB Handler
125 The EBB handler is just regular userspace code, however it must be written in
126 the style of an interrupt handler. When the handler is entered all registers
127 are live (possibly) and so must be saved somehow before the handler can invoke
|
| /Documentation/livepatch/ |
| D | livepatch.rst | 44 a base. A Kprobe is registered as a ftrace handler when the function entry
46 a live patch is called with the help of a custom ftrace handler. But there are
90 An interrupt handler inherits the patched state of the task it
327 ftrace handler is registered\ [#]_. This stage is indicated by a value of '1'
336 Note that functions might be patched multiple times. The ftrace handler
339 The right implementation is selected by the ftrace handler, see
356 the ftrace handler is unregistered and the struct klp_ops is
378 patch are removed from the corresponding struct klp_ops. The ftrace handler
416 implementing ftrace or the livepatch ftrace handler could not be
432 the ftrace handler. This operation has to be reverted on return.
[all …]
|
| /Documentation/timers/ |
| D | highres.rst | 91 service handler, which is almost inherently hardware dependent.
115 from the hardware level handler. This removes a lot of duplicated code from the
174 When the timer interrupt happens, the next event interrupt handler is called
177 handler. An additional mode field in the hrtimer structure allows the system to
178 execute callback functions directly from the next event interrupt handler. This
181 used by nanosleep. The advantage of executing the handler in the interrupt
225 reschedule. The call is necessary as the interrupt handler might have armed a
235 handler has not to deal with an eventually stale jiffy value.
|
| /Documentation/arch/s390/ |
| D | driver-model.rst | 95 void (*handler) (struct ccw_device *dev, unsigned long intparm,
135 the interrupt handler (see below) should be set here.
219 The handler field of the struct ccw_device is meant to be set to the interrupt
220 handler for the device. In order to accommodate drivers which use several
223 The handler is registered with the common layer during set_online() processing
230 void (*handler) (struct ccw_device *dev, unsigned long intparm, struct irb *irb);
232 Parameters: dev - the device the handler is called for
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-acpi | 110 A GPE vectors to a specified handler in AML, which
113 to a level or edge handler called _L12 or _E12.
114 The handler may do its business and return.
115 Or the handler may send send a Notify event
192 doesn't have an event handler.
216 Fixed Event with event handler installed.
|
| /Documentation/infiniband/ |
| D | core_locking.rst | 72 handler directly from its post_send method. Instead, the low-level
79 handler for a given CQ is running at a time. In other words, the
91 return from CQ event handler
|
| /Documentation/driver-api/rapidio/ |
| D | rio_cm.rst | 66 handler checks for a pending connection request and if one is not available
72 The handler for this request assumes that message buffer specified by
78 handler will wait for new message until timeout specified by a caller
79 expires. If timeout value is set to 0, ioctl handler uses a default value
|
1234567891011