| /Documentation/driver-api/usb/ |
| D | callbacks.rst | 1 USB core callbacks
4 What callbacks will usbcore do?
7 Usbcore will call into a driver through callbacks defined in the driver
10 callbacks are completely independent of each other. Information on the
13 The callbacks defined in the driver structure are:
15 1. Hotplugging callbacks:
34 3. Power management (PM) callbacks:
55 reason. Sysfs is preferred these days. The PM callbacks are covered
61 All callbacks are mutually exclusive. There's no need for locking
62 against other USB callbacks. All callbacks are called from a task
[all …]
|
| D | index.rst | 11 callbacks
|
| /Documentation/livepatch/ |
| D | callbacks.rst | 2 (Un)patching Callbacks
5 Livepatch (un)patch-callbacks provide a mechanism for livepatch modules
16 In most cases, (un)patch callbacks will need to be used in conjunction
23 Callbacks differ from existing kernel facilities:
30 Callbacks are part of the klp_object structure and their implementation
37 Callbacks can be registered for the following livepatch actions:
61 symmetry: pre-patch callbacks have a post-unpatch counterpart and
62 post-patch callbacks have a pre-unpatch counterpart. An unpatch
69 in-kernel vmlinux targets, this means that callbacks will always execute
71 callbacks will only execute if the target module is loaded. When a
[all …]
|
| D | cumulative-patches.rst | 70 extra modifications in (un)patching callbacks or in the module_init()
77 - Only the (un)patching callbacks from the _new_ cumulative livepatch are
78 executed. Any callbacks from the replaced patches are ignored.
84 older ones. The old livepatches might not provide the necessary callbacks.
92 the various callbacks and their interactions if the callbacks from all
|
| /Documentation/core-api/ |
| D | cpu_hotplug.rst | 133 Once a CPU has been logically shutdown the teardown callbacks of registered
158 When a CPU is onlined, the startup callbacks are invoked sequentially until
160 callbacks of a state are set up or an instance is added to a multi-instance
163 When a CPU is offlined the teardown callbacks are invoked in the reverse
165 be invoked when the callbacks of a state are removed or an instance is
179 The startup callbacks in this section are invoked before the CPU is
180 started during a CPU online operation. The teardown callbacks are invoked
183 The callbacks are invoked on a control CPU as they can't obviously run on
187 The startup callbacks are used to setup resources which are required to
188 bring a CPU successfully online. The teardown callbacks are used to free
[all …]
|
| /Documentation/RCU/ |
| D | UP.rst | 77 It is far better to guarantee that callbacks are invoked
85 What locking restriction must RCU callbacks respect?
90 permit call_rcu() to directly invoke callbacks, but only if a full
91 grace period has elapsed since those callbacks were queued. This is
94 encouraged to avoid invoking callbacks from call_rcu(), thus obtaining
102 infrastructure *must* respect grace periods, and *must* invoke callbacks
123 What locking restriction must RCU callbacks respect?
134 then, since RCU callbacks can be invoked from softirq context,
140 callbacks acquire locks directly. However, a great many RCU
141 callbacks do acquire locks *indirectly*, for example, via
|
| D | rcubarrier.rst | 34 If we unload the module while some RCU callbacks are pending,
35 the CPUs executing these callbacks are going to be severely
41 grace period to elapse, it does not wait for the callbacks to complete.
45 heavy RCU-callback load, then some of the callbacks might be deferred in
56 outstanding RCU callbacks to complete. Please note that rcu_barrier()
58 callbacks queued anywhere, rcu_barrier() is within its rights to return
63 1. Prevent any new RCU callbacks from being posted.
136 52 /* Wait for all RCU callbacks to fire. */
149 Line 6 sets a global variable that prevents any RCU callbacks from
151 RCU callbacks rarely include calls to call_rcu(). However, the rcutorture
[all …]
|
| D | checklist.rst | 333 memory exhaustion when any given CPU has too many callbacks,
336 CPUs has been configured to offload all of its RCU callbacks onto
375 12. RCU callbacks can be and are executed in parallel. In many cases,
379 if the callbacks do manipulate a shared data structure, they
383 Do not assume that RCU callbacks will be executed on the same
391 RCU callbacks executed on some other CPUs, in fact, for some
395 In addition, do not assume that callbacks queued in a given order
397 same CPU. Furthermore, do not assume that same-CPU callbacks will
400 and while a given CPU is undergoing such a switch, its callbacks
402 that CPU's rcuo kthread. At such times, that CPU's callbacks
[all …]
|
| /Documentation/networking/ |
| D | sriov.rst | 16 it consists of a number of ``ndo_set_vf_*`` and ``ndo_get_vf_*`` callbacks.
20 will be accepted. New drivers should not implement the uncommon callbacks;
21 namely the following callbacks are off limits:
|
| D | strparser.rst | 32 The API includes a context structure, a set of callbacks, utility
34 callbacks include a parse_msg function that is called to perform
49 callback mode; in general mode this is set to NULL. Callbacks
50 are called by the stream parser (the callbacks are listed below).
112 Callbacks chapter
115 There are seven callbacks:
|
| D | xfrm_device.rst | 60 Callbacks to implement
67 /* Crypto and Packet offload callbacks */
76 /* Solely packet offload callbacks */
82 The NIC driver offering ipsec offload will need to implement callbacks
93 set up local data structures and XFRM callbacks, and set the feature bits.
|
| /Documentation/driver-api/pm/ |
| D | devices.rst | 272 executing callbacks for every device before the next phase begins. Not all
273 buses or classes support all these callbacks and not all drivers use all the
274 callbacks. The various phases always run after tasks have been frozen and
279 All phases use PM domain, bus, type, class or driver callbacks (that is, methods
281 ``dev->class->pm`` or ``dev->driver->pm``). These callbacks are regarded by the
282 PM core as mutually exclusive. Moreover, PM domain callbacks always take
283 precedence over all of the other callbacks and, for example, type callbacks take
284 precedence over bus, class and driver callbacks. To be precise, the following
300 This allows PM domains and device types to override callbacks provided by bus
303 The PM domain, type, class and bus callbacks may in turn invoke device- or
[all …]
|
| D | notifiers.rst | 16 ``->resume()`` or even ``->prepare()`` and ``->complete()`` callbacks are not
33 callbacks for the "freeze" transition.
37 error occurred during hibernation. Device restore callbacks have been
47 callbacks have been executed and tasks have been thawed.
54 resume callbacks have been executed and tasks have been thawed.
|
| /Documentation/power/ |
| D | pci.rst | 272 2.1. Device Power Management Callbacks
280 pointers to several device power management callbacks::
302 These callbacks are executed by the PM core in various situations related to
303 device power management and they, in turn, execute power management callbacks
309 that these callbacks operate on::
363 Namely, it provides subsystem-level callbacks::
431 management callbacks for this purpose. They are executed in phases such that
444 The following PCI bus type's callbacks, respectively, are used in these phases::
459 pointers to the driver's callbacks), pci_pm_default_suspend() is called, which
483 device driver's callbacks executed before might do that), pci_pm_suspend_noirq()
[all …]
|
| D | runtime_pm.rst | 28 * Three device runtime PM callbacks in 'struct dev_pm_ops' (defined in
36 The runtime PM callbacks present in 'struct dev_pm_ops', the device runtime PM
40 2. Device Runtime PM Callbacks
43 There are three device runtime PM callbacks defined in 'struct dev_pm_ops'::
53 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks
72 priority order of callbacks from high to low is: PM domain, device type, class
74 a low-priority one. The PM domain, bus type, device type and class callbacks
75 are referred to as subsystem-level callbacks in what follows.
77 By default, the callbacks are always invoked in process context with interrupts
80 and ->runtime_idle() callbacks for the given device in atomic context with
[all …]
|
| /Documentation/driver-api/media/ |
| D | v4l2-event.rst | 59 ``merge()`` and ``replace()`` callbacks which drivers can set. These
60 callbacks are called when a new event is raised and there is no more room.
75 A good example of these ``replace``/``merge`` callbacks is in v4l2-event.c:
76 ``ctrls_replace()`` and ``ctrls_merge()`` callbacks for the control event.
79 these callbacks can be called from interrupt context, so they must
110 The ops argument allows the driver to specify a number of callbacks:
124 All 4 callbacks are optional, if you don't want to specify any callbacks
|
| D | cec-core.rst | 107 /* Low-level callbacks */
120 /* Error injection callbacks */
326 be exposed through the Error Injection callbacks:
331 /* Low-level callbacks */
334 /* Error injection callbacks */
342 If both callbacks are set, then an ``error-inj`` file will appear in debugfs.
388 CEC protocol driven. The high-level callbacks are called without the adap->lock
389 mutex being held. The following high-level callbacks are available:
394 /* Low-level callbacks */
397 /* Error injection callbacks */
|
| /Documentation/driver-api/80211/ |
| D | mac80211.rst | 25 Additionally, some discussion about the callbacks and the general
49 This chapter should describe PHY handling including start/stop callbacks
64 the add_iface/remove_iface callbacks as well as the interface
65 configuration callbacks.
|
| /Documentation/driver-api/phy/ |
| D | samsung-usb2.rst | 22 the probe function and provides two callbacks to the Generic PHY
23 Framework. This two callbacks are used to power on and power off the
26 specific callbacks. The specific SoC version is selected by choosing
104 These two callbacks are used to power on and power off the phy
|
| /Documentation/driver-api/ |
| D | isa.rst | 44 callbacks, and as indicated that .match callback.
50 The platform_driver callbacks are called with a platform_device param;
51 the isa_driver callbacks are being called with a ``struct device *dev,
55 struct device anyways, and it makes for nicer code in the callbacks as
|
| /Documentation/RCU/Design/Data-Structures/ |
| D | Data-Structures.rst | 121 RCU updaters wait for normal grace periods by registering RCU callbacks,
123 ``synchronize_rcu()`` and friends. RCU callbacks are represented by
156 serves as short-term repository for callbacks orphaned by CPU-hotplug
182 #. ``rcu_head``: This structure represents RCU callbacks, and is the
670 The ``rcu_segcblist`` structure maintains a segmented list of callbacks
691 #. ``RCU_DONE_TAIL``: Callbacks whose grace periods have elapsed. These
692 callbacks are ready to be invoked.
693 #. ``RCU_WAIT_TAIL``: Callbacks that are waiting for the current grace
696 #. ``RCU_NEXT_READY_TAIL``: Callbacks waiting for the next grace period
698 #. ``RCU_NEXT_TAIL``: Callbacks that have not yet been associated with a
[all …]
|
| /Documentation/driver-api/gpio/ |
| D | driver.rst | 85 and direction control callbacks) if it is expected to call GPIO APIs from
274 callbacks from the GPIO and irq_chip APIs. Do not rely on gpiod_to_irq() having
304 and .irq_bus_unlock() callbacks, as these are the only slowpath callbacks
305 on an irqchip. Create the callbacks if needed.[2]
327 struct gpio_chip, as everything happens directly in the callbacks: no
393 associated irqdomain and resource allocation callbacks. These are activated
461 * callbacks to the structure.
470 /* Provide the gpio resource callbacks */
535 * callbacks to the structure.
544 /* Provide the gpio resource callbacks */
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-gsmi | 7 triggers. Some of the callbacks are similar to those
13 these firmware callbacks. Currently, this functionality
|
| /Documentation/driver-api/virtio/ |
| D | writing_virtio_drivers.rst | 66 /* from this point on, the device can notify and get callbacks */
175 The virtqueue callbacks can be disabled and re-enabled using the
185 But note that some spurious callbacks can still be triggered under
186 certain scenarios. The way to disable callbacks reliably is to reset the
|
| /Documentation/pcmcia/ |
| D | locking.rst | 25 The following functions and callbacks to struct pcmcia_socket must
42 The following functions and callbacks to struct pcmcia_socket must
|