Home
last modified time | relevance | path

Searched refs:notifiers (Results 1 – 25 of 27) sorted by relevance

12

/linux/Documentation/cpu-freq/
H A Dcore.rst4 General description of the CPUFreq core and CPUFreq notifiers
16 2. CPUFreq notifiers
25 frequency transitions), as well as to "notifiers". These are device
39 2. CPUFreq notifiers
42 CPUFreq notifiers conform to the standard kernel notifier interface.
43 See linux/include/linux/notifier.h for details on notifiers.
45 There are two different CPUFreq notifiers - policy notifiers and
46 transition notifiers.
49 2.1 CPUFreq policy notifiers
63 2.2 CPUFreq transition notifiers
/linux/drivers/clk/renesas/
H A Drcar-cpg-lib.c58 void cpg_simple_notifier_register(struct raw_notifier_head *notifiers, in cpg_simple_notifier_register() argument
62 raw_notifier_chain_register(notifiers, &csn->nb); in cpg_simple_notifier_register()
92 struct raw_notifier_head *notifiers) in cpg_sdh_clk_register() argument
111 cpg_simple_notifier_register(notifiers, csn); in cpg_sdh_clk_register()
142 struct raw_notifier_head *notifiers) in cpg_rpc_clk_register() argument
172 cpg_simple_notifier_register(notifiers, &rpc->csn); in cpg_rpc_clk_register()
H A Drcar-cpg-lib.h24 void cpg_simple_notifier_register(struct raw_notifier_head *notifiers,
31 struct raw_notifier_head *notifiers);
38 struct raw_notifier_head *notifiers);
H A Drcar-gen3-cpg.c345 struct raw_notifier_head *notifiers = &pub->notifiers; in rcar_gen3_cpg_clk_register() local
403 __clk_get_name(parent), notifiers); in rcar_gen3_cpg_clk_register()
431 cpg_simple_notifier_register(notifiers, csn); in rcar_gen3_cpg_clk_register()
523 __clk_get_name(parent), notifiers); in rcar_gen3_cpg_clk_register()
H A Dclk-div6.h7 struct raw_notifier_head *notifiers);
H A Dclk-div6.c246 struct raw_notifier_head *notifiers) in cpg_div6_register() argument
307 if (notifiers) { in cpg_div6_register()
309 raw_notifier_chain_register(notifiers, &clock->nb); in cpg_div6_register()
H A Drcar-gen4-cpg.c425 struct raw_notifier_head *notifiers = &pub->notifiers; in rcar_gen4_cpg_clk_register() local
486 __clk_get_name(parent), notifiers); in rcar_gen4_cpg_clk_register()
524 __clk_get_name(parent), notifiers); in rcar_gen4_cpg_clk_register()
H A Drenesas-cpg-mssr.c470 &priv->pub.notifiers); in cpg_mssr_register_core_clk()
1114 raw_notifier_call_chain(&priv->pub.notifiers, PM_EVENT_SUSPEND, NULL); in cpg_mssr_suspend_noirq()
1131 raw_notifier_call_chain(&priv->pub.notifiers, PM_EVENT_RESUME, NULL); in cpg_mssr_resume_noirq()
1304 RAW_INIT_NOTIFIER_HEAD(&priv->pub.notifiers); in cpg_mssr_common_init()
/linux/Documentation/driver-api/pm/
H A Dnotifiers.rst26 Subsystems or drivers having such needs can register suspend notifiers that
32 additional work is done between the notifiers and the invocation of PM
56 It is generally assumed that whatever the notifiers do for
61 Moreover, if one of the notifiers fails for the ``PM_HIBERNATION_PREPARE`` or
62 ``PM_SUSPEND_PREPARE`` event, the notifiers that have already succeeded for that
66 The hibernation and suspend notifiers are called with :c:data:`pm_mutex` held.
/linux/drivers/net/ethernet/mellanox/mlx5/core/
H A Devents.c59 struct mlx5_event_nb notifiers[ARRAY_SIZE(events_nbs_ref)]; member
408 events->notifiers[i].nb = events_nbs_ref[i]; in mlx5_events_start()
409 events->notifiers[i].ctx = events; in mlx5_events_start()
410 mlx5_eq_notifier_register(dev, &events->notifiers[i].nb); in mlx5_events_start()
420 mlx5_eq_notifier_unregister(dev, &events->notifiers[i].nb); in mlx5_events_stop()
/linux/Documentation/driver-api/surface_aggregator/clients/
H A Dcdev.rst34 Before events are available to be read, however, the desired notifiers must be
43 notifiers work per-client (i.e. per-device-file-instance), events are enabled
53 instances. For example, it is valid to set up notifiers and read events on
195 Note that this will not unregister any notifiers. Events may still be received
198 notifiers.
/linux/drivers/misc/vmw_vmci/
H A Dvmci_context.c680 u32 *notifiers; in vmci_ctx_get_chkpt_notifiers() local
691 data_size = context->n_notifiers * sizeof(*notifiers); in vmci_ctx_get_chkpt_notifiers()
697 notifiers = kmalloc(data_size, GFP_ATOMIC); /* FIXME: want GFP_KERNEL */ in vmci_ctx_get_chkpt_notifiers()
698 if (!notifiers) in vmci_ctx_get_chkpt_notifiers()
702 notifiers[i++] = entry->handle.context; in vmci_ctx_get_chkpt_notifiers()
705 *pbuf = notifiers; in vmci_ctx_get_chkpt_notifiers()
/linux/Documentation/fault-injection/
H A Dnotifier-error-inject.rst7 modules that can be used to test the following notifiers.
92 for CPU and memory notifiers.
/linux/Documentation/driver-api/surface_aggregator/
H A Dclient.rst153 (un-)registering event notifiers (and thus should generally be avoided). This
321 Event notifiers are registered by providing (at minimum) a callback to call
331 By default, event notifiers will receive all events for the specific target
377 * This essentially tells the core if it can skip notifiers that
388 Multiple event notifiers can be registered for the same event. The event
389 handler core takes care of enabling and disabling events when notifiers are
390 registered and unregistered, by keeping track of how many notifiers for a
396 should take care that notifiers for a specific event are always registered
H A Dinternal.rst530 Note that due to the way notifiers are (or rather have to be) stored, client
536 is applied when iterating over the notifiers at the time they are executed.
/linux/drivers/base/power/
H A Dqos.c217 c->notifiers = n; in dev_pm_qos_constraints_allocate()
313 kfree(qos->resume_latency.notifiers); in dev_pm_qos_constraints_destroy()
553 ret = blocking_notifier_chain_register(dev->power.qos->resume_latency.notifiers, in dev_pm_qos_add_notifier()
600 ret = blocking_notifier_chain_unregister(dev->power.qos->resume_latency.notifiers, in dev_pm_qos_remove_notifier()
/linux/Documentation/networking/
H A Dnetdevices.rst412 some of the notifiers (``enum netdev_cmd``) are running under the netdev
415 The following netdev notifiers are always run under the instance lock:
418 For devices with locked ops, currently only the following notifiers are
427 The following notifiers are running without the lock:
435 There are no clear expectations for the remaining notifiers. Notifiers not on
439 exceptions) notifiers run under the instance lock. Please extend this
/linux/Documentation/devicetree/
H A Dchangesets.rst15 at once before emitting OF_RECONFIG notifiers. This is so that the
/linux/Documentation/driver-api/memory-devices/
H A Dti-emif.rst50 EMIF driver registers notifiers for voltage and frequency changes
/linux/Documentation/gpu/rfc/
H A Dgpusvm.rst62 (rather than seqno due to wider notifiers), pagetable entries, and
107 * May be desirable for faster notifiers.
/linux/Documentation/admin-guide/pm/
H A Dsuspend-flows.rst48 1. Invoking system-wide suspend notifiers.
157 4. Invoking system-wide resume notifiers.
170 1. Invoking system-wide suspend notifiers.
267 6. Invoking system-wide resume notifiers.
/linux/Documentation/power/
H A Dfreezing-of-tasks.rst204 hibernation (and suspend) notifiers (in that case, though, we won't be able to
222 Documentation/driver-api/pm/notifiers.rst.
232 suspend/hibernation notifiers to achieve mutual exclusion. Look at the
/linux/Documentation/virt/kvm/
H A Dlocking.rst28 are taken on the waiting side when modifying memslots, so MMU notifiers
317 in notifiers, e.g. __kvmclock_cpufreq_notifier(), that may be invoked while
/linux/lib/
H A DKconfig.kgdb83 bool "KGDB: Allow debugging with traps in notifiers"
/linux/Documentation/driver-api/media/
H A Dv4l2-subdev.rst205 Asynchronous sub-device notifiers
236 a path via async sub-devices and notifiers to a notifier that is not an

12