Home
last modified time | relevance | path

Searched full:invoked (Results 1 – 25 of 826) sorted by relevance

12345678910>>...34

/Linux-v5.4/Documentation/networking/dsa/
Ddsa.rst109 - receive function is invoked
136 - invoked ``netif_receive_skb()``
228 function hooks should be invoked, information about the directly attached
359 - ``probe``: probe routine which will be invoked by the DSA platform device upon
387 - ``phy_read``: Function invoked by the DSA slave MDIO bus when attempting to read
392 - ``phy_write``: Function invoked by the DSA slave MDIO bus when attempting to write
396 - ``adjust_link``: Function invoked by the PHY library when a slave network device
401 - ``fixed_link_update``: Function invoked by the PHY library, and specifically by
455 - ``suspend``: function invoked by the DSA platform device when the system goes to
460 - ``resume``: function invoked by the DSA platform device when the system resumes,
[all …]
/Linux-v5.4/tools/testing/selftests/bpf/prog_tests/
Dtcp_rtt.c6 __u32 invoked; member
45 static int verify_sk(int map_fd, int client_fd, const char *msg, __u32 invoked, in verify_sk() argument
57 if (val.invoked != invoked) { in verify_sk()
58 log_err("%s: unexpected bpf_tcp_sock.invoked %d != %d", in verify_sk()
59 msg, val.invoked, invoked); in verify_sk()
155 /*invoked=*/1, in run_test()
169 /*invoked=*/2, in run_test()
/Linux-v5.4/Documentation/scsi/
Dscsi_eh.txt60 scsi_finish_command() is invoked for the command. The
73 scsi_eh_scmd_add(scmd) is invoked for the command. See
95 2. scsi_abort_command() is invoked to schedule an asynchrous abort.
96 Asynchronous abort are not invoked for commands which the
101 3. scsi_eh_scmd_add(scmd, SCSI_EH_CANCEL_CMD) is invoked for the
110 Otherwise scsi_eh_scmd_add() is invoked for the command.
226 recovered (eh_work_q is empty), scsi_eh_flush_done_q() is invoked to
238 ACTION: scsi_eh_scmd_add() is invoked for scmd
251 ACTION: scsi_eh_finish_cmd() is invoked to EH-finish scmd
266 - otherwise, scsi_finish_command() is invoked for scmd
[all …]
Dscsi_mid_low_api.txt168 remove() callback being invoked. In either case, the sequence is the
374 * Notes: Can be invoked any time on a SCSI device controlled by this
376 * slave_destroy().] Can safely be invoked from interrupt code.
527 * lead to the slave_destroy() callback being invoked. sdev is an
543 * Notes: Should only be invoked if the "hotplug initialization
630 * Notes: Should not be invoked if the "hotplug initialization
747 * will be invoked from scsi_eh thread. No other commands
767 * Notes: Invoked from scsi_eh thread. No other commands will be
785 * Notes: Invoked from scsi_eh thread. No other commands will be
803 * Notes: Invoked from scsi_eh thread. No other commands will be
[all …]
/Linux-v5.4/drivers/crypto/qce/
Dcore.h26 * @async_req_enqueue: invoked by every algorithm to enqueue a request
27 * @async_req_done: invoked by every algorithm to finish its request
49 * @register_algs: invoked by core to register the algorithms
50 * @unregister_algs: invoked by core to unregister the algorithms
51 * @async_req_handle: invoked by core to handle enqueued request
/Linux-v5.4/Documentation/RCU/
Dlockdep.txt37 invoked by both RCU readers and updaters.
41 is invoked by both RCU-bh readers and updaters.
45 is invoked by both RCU-sched readers and updaters.
49 is invoked by both SRCU readers and updaters.
56 invoked only by updaters.
84 from taking place. If the above statement was invoked only from updater
DUP.rst30 This same problem can occur if call_rcu() is invoked from a hardware
59 Suppose that call_rcu() is invoked while holding a lock, and that the
76 It is far better to guarantee that callbacks are invoked
110 Therefore, the called function has been invoked within an RCU
125 then, since RCU callbacks can be invoked from softirq context,
/Linux-v5.4/Documentation/core-api/
Dcpu_hotplug.rst153 hotplug states will be invoked, starting with ``CPUHP_ONLINE`` and terminating
178 will be invoked during registration on all online CPUs. If an error
180 invoked on all CPUs on which the online callback was previously invoked.
181 After registration completed, the *Y_online* callback will be invoked
182 once a CPU is brought online and *Y_prepare_down* will be invoked when a
192 During the removal of a hotplug state the teardown callback will be invoked.
219 should be invoked which will invoke the teardown callback on all online
238 * The states *CPUHP_OFFLINE* … *CPUHP_AP_OFFLINE* are invoked before the
240 * The states *CPUHP_AP_OFFLINE* … *CPUHP_AP_ONLINE* are invoked
243 the callbacks are invoked on the target CPU.
[all …]
/Linux-v5.4/drivers/net/fddi/skfp/h/
Dhwmtm.h202 * This macro may be invoked by the OS-specific module to read
216 * This macro may be invoked by the OS-specific module to read
232 * This macro may be invoked by the OS-specific module to get the
249 * This macro may be invoked by the OS-specific module to get the
268 * This macro may be invoked by the OS-specific module to read
285 * This macro may be invoked by the OS-specific module to read
301 * This macro may be invoked by the OS-specific module to get
318 * This macro may be invoked by the OS-specific module to get
332 * This macro may be invoked by the OS-specific module to get the
348 * This macro is invoked by the OS-specific before it left the
/Linux-v5.4/include/drm/
Ddrm_bridge.h42 * This callback is invoked whenever our bridge is being attached to a
56 * This callback is invoked whenever our bridge is being detached from a
256 * Note that this function will only be invoked in the context of an
257 * atomic commit. It will not be invoked from &drm_bridge_pre_enable. It
281 * Note that this function will only be invoked in the context of an
282 * atomic commit. It will not be invoked from &drm_bridge_enable. It
303 * Note that this function will only be invoked in the context of an
304 * atomic commit. It will not be invoked from &drm_bridge_disable. It
327 * Note that this function will only be invoked in the context of an
328 * atomic commit. It will not be invoked from &drm_bridge_post_disable.
/Linux-v5.4/include/linux/regulator/
Dcoupler.h23 * @attach_regulator: Callback invoked on creation of a coupled regulator,
29 * @detach_regulator: Callback invoked on destruction of a coupled regulator.
31 * @balance_voltage: Callback invoked when voltage of a coupled regulator is
/Linux-v5.4/Documentation/virt/kvm/
Dhalt-polling.txt16 invoked. Thus halt polling is especially useful on workloads with very short
46 received during the polling interval (and thus schedule is invoked) there are
72 invoked and a wakeup source received (irrespective of
73 whether the scheduler is invoked within that function).
135 schedule will be invoked to allow that other task to run. Thus this doesn't
/Linux-v5.4/drivers/crypto/caam/
Dqi.h29 * caam_qi_cbk - application's callback function invoked by the driver when the
134 * Invoked when shared descriptor is required to be change in driver context.
155 * Invoked when a user of the CAAM-QI (i.e. caamalg-qi) needs data which has
169 * Invoked when a user of the CAAM-QI (i.e. caamalg-qi) no longer needs
/Linux-v5.4/arch/mips/sgi-ip27/
DTODO11 being invoked on all nodes in ip27-memory.c.
12 8. Too many do_page_faults invoked - investigate.
/Linux-v5.4/include/linux/
Drpmsg.h81 * the rpmsg channel), the driver's handler is invoked to process it.
102 * @probe: invoked when a matching rpmsg channel (i.e. device) is found
103 * @remove: invoked when the rpmsg channel is removed
104 * @callback: invoked when an inbound message is received on the channel
/Linux-v5.4/tools/testing/selftests/bpf/progs/
Dtcp_rtt.c9 __u32 invoked; member
53 storage->invoked++; in _sockops()
/Linux-v5.4/tools/testing/selftests/rseq/
Drseq.h123 * does not need to be invoked.
150 * rseq_prepare_unload() should be invoked by each thread executing a rseq
154 * JIT: rseq_prepare_unload() should be invoked at least once by each
/Linux-v5.4/Documentation/admin-guide/pm/
Dcpufreq.rst119 the scaling driver, the ``CPUFreq`` core will be invoked to take note of them
122 In any case, the ``CPUFreq`` core is invoked to take note of any logical CPU it
130 Once invoked, the ``CPUFreq`` core checks if the policy pointer is already set
136 Next, the scaling driver's ``->init()`` callback is invoked with the policy
159 The utilization update callbacks will be invoked by the CPU scheduler on
165 the P-state selection. The scaling driver may be invoked directly from
185 new policy objects. Instead, the driver's ``->setpolicy()`` callback is invoked
187 callbacks are invoked by the CPU scheduler in the same way as for scaling
398 invoking its utilization update callback for that CPU. If it is invoked by the
401 if it is invoked by the CFS scheduling class, the governor will use the
[all …]
/Linux-v5.4/drivers/media/platform/mtk-vcodec/
Dvdec_vpu_if.h45 * vpu_dec_start - start decoding, basically the function will be invoked once
55 * vpu_dec_end - end decoding, basically the function will be invoked once
/Linux-v5.4/drivers/pci/hotplug/
DTODO65 removed and its functions invoked directly? This has already been done in
69 * The ->get_mode1_ECC_cap callback in shpchp_hpc_ops is never invoked.
/Linux-v5.4/Documentation/driver-api/pm/
Dcpuidle.rst48 A CPU idle time (``CPUIdle``) governor is a bundle of policy code invoked when
97 until the ``->enable()`` governor callback is invoked for that CPU
110 callback when it was last invoked for the target CPU, free all memory
149 selection made by the ``->select()`` callback (when it was invoked last
261 be invoked for the logical CPU represented by it, so it must take place after
/Linux-v5.4/drivers/base/power/
Dcommon.c92 * This function should typically be invoked from subsystem level code during
128 * This function should typically be invoked by a driver during the probe phase,
177 * Typically it should be invoked during the remove phase, either from
/Linux-v5.4/kernel/rcu/
Dsync.c55 * rcu_sync_exit(), so that it is invoked after a grace period following the
65 * If another rcu_sync_enter() is invoked before the grace period
68 * another rcu_sync_enter() and its matching rcu_sync_exit() are invoked
/Linux-v5.4/Documentation/admin-guide/
Dbinfmt-misc.rst8 To achieve this you must tell binfmt_misc which interpreter has to be invoked
50 is the program that should be invoked with the binary as first
85 binary lazily when the misc format file is invoked. However,
/Linux-v5.4/drivers/media/platform/exynos4-is/
Dfimc-is-param.h970 u32 assert_flag; /* 0: Not invoked, 1: Invoked */
971 u32 pabort_flag; /* 0: Not invoked, 1: Invoked */
972 u32 dabort_flag; /* 0: Not invoked, 1: Invoked */

12345678910>>...34