Searched full:callback (Results 1 – 25 of 260) sorted by relevance
1234567891011
| /Documentation/trace/ |
| D | ftrace-uses.rst | 26 The ability to add a callback to almost any function within the
27 kernel comes with risks. A callback can be called from any context
30 This requires extra care to what can be done inside a callback. A callback
40 To register a function callback, a ftrace_ops is required. This structure
41 is used to tell ftrace what function should be called as the callback
42 as well as what protections the callback will perform and not require
70 The registered callback will start being called some time after the
73 of services. The callback itself will have to handle any synchronization if it
76 The unregister_ftrace_function() will guarantee that the callback is
82 The callback function
[all …]
|
| D | fprobe.rst | 22 The fprobe is a wrapper of ftrace (+ kretprobe-like return callback) to
90 The prototype of the entry/exit callback function are as follows:
99 If the entry callback function returns !0, the corresponding exit callback will be cancelled.
140 This is not a matter if the common callback code has its own recursion
146 Fprobe has FPROBE_FL_KPROBE_SHARED flag to do this. If your common callback
156 This will protect your common callback from the nested call.
172 skips both of entry and exit callback and the latter skips the exit
173 callback, but in both case the counter will increase by 1.
|
| /Documentation/livepatch/ |
| D | callbacks.rst | 6 to execute callback functions when a kernel object is (un)patched. They
34 2. Callback types
48 active), used to clean up post-patch callback
54 used to cleanup pre-patch callback resources
59 Each callback is optional, omitting one does not preclude specifying any
63 callback will only be executed if its corresponding patch callback was
68 A callback is only executed if its host klp_object is loaded. For
75 The pre-patch callback, if specified, is expected to return a status
79 callback is provided, the transition is assumed to be safe.) If a
80 pre-patch callback returns failure, the kernel's module loader will:
[all …]
|
| /Documentation/networking/ |
| D | strparser.rst | 17 The strparser works in one of two modes: receive callback or general
20 In receive callback mode, the strparser is called from the data_ready
21 callback of a TCP socket. Messages are parsed and delivered as they are
33 functions, and a data_ready function for receive callback mode. The
49 callback mode; in general mode this is set to NULL. Callbacks
100 from a data_ready callback that is set on the socket. Note that
144 zero) and the parser is in receive callback mode, then it will set
154 The lock callback is called to lock the strp structure when
156 processing a timeout). In receive callback mode the default
158 mode the callback must be set appropriately.
[all …]
|
| D | netdev-features.rst | 26 request. This set should be initialized in ndo_init callback and not
31 error paths of ndo_set_features callback.
39 This set is filtered by ndo_fix_features callback whenever it or
49 is calculated and filtered by calling ndo_fix_features callback
51 set, it is passed to ndo_set_features callback and (if the callback
67 driver except by means of ndo_fix_features callback.
81 This callback should not modify hardware nor driver state (should be
85 Callback must not alter features contained in NETIF_F_SOFT_FEATURES or
93 be reliably detected in ndo_fix_features. In this case, the callback
|
| /Documentation/power/ |
| D | runtime_pm.rst | 68 callback, the PM core will invoke the corresponding driver callback stored in
71 The PM core always checks which callback to use in the order given above, so the
81 interrupts disabled. This implies that the callback routines in question must
86 The subsystem-level suspend callback, if present, is _entirely_ _responsible_
88 include executing the device driver's own ->runtime_suspend() callback (from the
90 callback in a device driver as long as the subsystem-level suspend callback
93 * Once the subsystem-level suspend callback (or the driver suspend callback,
98 RAM until the appropriate resume callback is executed for it. The runtime
99 PM status of a device after successful execution of the suspend callback is
102 * If the suspend callback returns -EBUSY or -EAGAIN, the device's runtime PM
[all …]
|
| D | pci.rst | 378 driver has to provide a pm->runtime_suspend() callback (see below), which is
379 run by pci_pm_runtime_suspend() as the first action. If the driver's callback
392 It is expected that the device driver's pm->runtime_suspend() callback will
400 driver provides a pm->runtime_resume() callback (see below). However, before
401 the driver's callback is executed, pci_pm_runtime_resume() brings the device
404 callback need not worry about the PCI-specific aspects of the device resume.
417 callback, if defined, and if that callback doesn't return error code (or is not
424 pm->runtime_idle() callback.
432 each phase involves executing the same subsystem-level callback for every device
452 driver's pm->prepare() callback if defined (i.e. if the driver's struct
[all …]
|
| D | pm_qos_interface.rst | 56 Adds a notification callback function to the CPU latency QoS. The callback is
60 Removes the notification callback function from the CPU latency QoS.
143 or whose power.set_latency_tolerance callback pointer is not NULL (for
171 Adds a notification callback function for the device for a particular request
174 The callback is called when the aggregated value of the device constraints
178 Removes the notification callback function for the device.
191 to software, the .set_latency_tolerance callback in that device's dev_pm_info
197 .set_latency_tolerance() callback will be executed and the effective value will
199 latency tolerance requirements for the device is empty, the callback is expected
202 the hardware supports a special "no requirement" setting, the callback is
|
| /Documentation/core-api/ |
| D | memory-hotplug.rst | 23 Generated when memory has successfully brought online. The callback may
29 is still in use. The callback can be used to free memory known to a
39 A callback routine can be registered by calling::
43 Callback functions with higher values of priority are called before callback
46 A callback function must have the following prototype::
51 The first argument of the callback function (self) is a pointer to the block
52 of the notifier chain that points to the callback function itself.
71 If status_changed_nid* >= 0, callback should create/discard structures for the
74 The callback routine shall return one of the values
|
| D | cpu_hotplug.rst | 156 callback.
168 If a usage site requires only a callback in one direction of the hotplug
169 operations (CPU online or CPU offline) then the other not-required callback
192 The startup callbacks are allowed to fail. If a callback fails, the CPU
227 The callbacks are allowed to fail. When a callback fails the hotplug
347 startup callback has to be invoked before the PERF driver startup
350 callback. The statically allocated states are described by constants in
404 a startup callback
409 a startup callback
414 a startup callback
[all …]
|
| /Documentation/sound/designs/ |
| D | seq-oss.rst | 36 the patch loading is realized by callback to the synth driver.
205 callbacks. The following callback functions must be defined:
217 Each callback function takes the argument type ``snd_seq_oss_arg_t`` as the
238 filled by the synth driver at open callback. The ``addr`` contains
241 in close callback by itself.
250 Open Callback
254 using OSS sequencer. This must not be NULL. Typically, the open callback
269 Ioctl Callback
272 The ``ioctl`` callback is called when the sequencer receives device-specific
273 ioctls. The following two ioctls should be processed by this callback:
[all …]
|
| /Documentation/driver-api/dmaengine/ |
| D | client.rst | 27 - Issue pending requests and wait for callback notification
140 Once a descriptor has been obtained, the callback information can be
148 Although the async_tx API specifies that completion callback
153 for submission prior to callback function being invoked, so
157 For cyclic DMA, a callback function may wish to terminate the
161 locks before calling the callback function which may cause a
189 after their transfer completion callback has run for the descriptor.
190 If no completion callback has been defined for the transfer, then the
193 completed, then the client must use completion callback.
255 point when the completion callback returns if used).
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-state_synced | 7 callback. The number read from it (0 or 1) reflects the value
9 .sync_state() callback hasn't been called yet. A value of 1
10 means the .sync_state() callback has been called.
18 this only when the sync_state() callback has been called --
|
| D | sysfs-devices-online | 10 .offline() callback is executed for the device and (if
13 this file, the device bus type's .online() callback is executed
18 callback the device cannot be used for any purpose until either
|
| D | sysfs-class-extcon | 27 object. If the extcon object has an optional callback
28 "show_name" defined, the callback will provide the name with
37 If the extcon object has an optional callback "show_state"
39 callback.
41 If the default callback for showing function is used, the
|
| D | sysfs-devices-coredump | 7 callback. The attribute is write only. Anything written to this
8 file will trigger the .coredump() callback.
|
| /Documentation/driver-api/media/ |
| D | dtv-demux.rst | 48 Demux Callback API
51 This kernel-space API comprises the callback functions that deliver filtered
56 structure as in the other demux APIs, because the callback functions are
58 for the API client to provide several callback functions for receiving TS
61 The functions that implement the callback API need not be re-entrant: when
63 call the function again before the original call returns. If a callback is
65 bottom half mechanism or start a tasklet instead of making the callback
|
| D | tx-rx.rst | 52 ``.s_stream()`` callback
55 The struct struct v4l2_subdev_video_ops->s_stream() callback is used by the
113 The ``.pre_streamon()`` callback may be used to prepare a transmitter for
115 ``.post_streamoff()`` callback is used to undo what was done by the
116 ``.pre_streamon()`` callback. The caller of ``.pre_streamon()`` is thus required
119 In the context of CSI-2, the ``.pre_streamon()`` callback is used to transition
130 calling the ``.s_stream()`` callback. Some transmitters may stop the
|
| /Documentation/driver-api/pm/ |
| D | cpuidle.rst | 53 containing four callback pointers, :c:member:`enable`, :c:member:`disable`,
80 The role of this callback is to prepare the governor for handling the
91 until the ``->enable()`` governor callback is invoked for that CPU
104 callback when it was last invoked for the target CPU, free all memory
105 allocated by that callback and so on.
121 value returned by this callback is interpreted as an index into that
127 to ``true`` before invoking this callback) is cleared to ``false``, the
133 This callback is mandatory (i.e. the :c:member:`select` callback pointer
143 selection made by the ``->select()`` callback (when it was invoked last
153 callback must not return the index of an indle state whose
[all …]
|
| /Documentation/sound/kernel-api/ |
| D | writing-an-alsa-driver.rst | 188 - create ``probe`` callback.
190 - create ``remove`` callback.
353 The real constructor of PCI drivers is the ``probe`` callback. The
354 ``probe`` callback and other component-constructors which are called
355 from the ``probe`` callback cannot be used with the ``__init`` prefix
358 In the ``probe`` callback, the following scheme is often used.
377 Each time the ``probe`` callback is called, check the availability of
472 remove callback and power-management callbacks, too.
477 The destructor, the remove callback, simply releases the card instance.
566 data pointer, and the callback pointers (``&ops``). The device-level
[all …]
|
| /Documentation/infiniband/ |
| D | core_locking.rst | 69 A low-level driver must not perform a callback directly from the
73 driver should defer this callback by, for example, scheduling a
74 tasklet to perform the callback.
85 consumer CQ event callback:
89 /* ... */ consumer CQ event callback:
96 Upper level protocol consumers may not sleep in a callback.
|
| /Documentation/driver-api/usb/ |
| D | callbacks.rst | 11 completion callback can be found in :ref:`usb-urb`.
73 The probe() callback
92 The disconnect() callback
99 This callback is a signal to break any connection with an interface.
101 callback. You also may not do any other operation that may interfere
104 aborted before this callback may return.
109 to deal with failing IO even prior to the callback.
|
| /Documentation/fb/ |
| D | deferred_io.rst | 59 and when the deferred_io callback is called. The deferred_io callback is
62 2. Setup your deferred IO callback. Eg::
67 The deferred_io callback is where you would perform all your IO to the display
69 to during the delay. You must not modify this list. This callback is called
|
| /Documentation/driver-api/driver-model/ |
| D | binding.rst | 31 algorithm, it is up to the bus driver to provide a callback to compare
38 and the driver's probe callback is called. This gives the driver a
50 class's register_dev callback.
92 go to 0. When it does, the remove callback of the driver is called. It
97 iterated over, and the driver's remove callback is called for each
|
| /Documentation/driver-api/ |
| D | connector.rst | 11 netlink based network. One must register a callback and an identifier.
13 identifier, the appropriate callback will be called.
28 …int cn_add_callback(const struct cb_id *id, char *name, void (*callback) (struct cn_msg *, struct …
39 connector.h header for in-kernel usage. `void (*callback) (void *)` is a
40 callback function which will be called when a message with above idx.val
62 When registering new callback user, connector core assigns
93 callback). It is done by sending a special command to the connector
|
1234567891011