| /linux-6.1.9/Documentation/cpu-freq/ |
| D | core.rst | 4 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-6.1.9/drivers/clk/renesas/ |
| D | rcar-cpg-lib.c | 58 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()
79 struct raw_notifier_head *notifiers) in cpg_sdh_clk_register() argument
98 cpg_simple_notifier_register(notifiers, csn); in cpg_sdh_clk_register()
129 struct raw_notifier_head *notifiers) in cpg_rpc_clk_register() argument
159 cpg_simple_notifier_register(notifiers, &rpc->csn); in cpg_rpc_clk_register()
|
| D | rcar-cpg-lib.h | 24 void cpg_simple_notifier_register(struct raw_notifier_head *notifiers,
31 struct raw_notifier_head *notifiers);
38 struct raw_notifier_head *notifiers);
|
| D | rcar-gen4-cpg.c | 187 struct raw_notifier_head *notifiers) in rcar_gen4_cpg_clk_register() argument
248 __clk_get_name(parent), notifiers); in rcar_gen4_cpg_clk_register()
286 __clk_get_name(parent), notifiers); in rcar_gen4_cpg_clk_register()
|
| D | clk-div6.h | 7 struct raw_notifier_head *notifiers);
|
| D | rcar-gen3-cpg.c | 336 struct raw_notifier_head *notifiers) in rcar_gen3_cpg_clk_register() argument
397 __clk_get_name(parent), notifiers); in rcar_gen3_cpg_clk_register()
425 cpg_simple_notifier_register(notifiers, csn); in rcar_gen3_cpg_clk_register()
513 __clk_get_name(parent), notifiers); in rcar_gen3_cpg_clk_register()
|
| D | clk-div6.c | 246 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()
|
| D | rcar-gen2-cpg.h | 36 struct raw_notifier_head *notifiers);
|
| D | r8a77970-cpg-mssr.c | 225 struct raw_notifier_head *notifiers) in r8a77970_cpg_clk_register() argument
242 notifiers); in r8a77970_cpg_clk_register()
|
| D | renesas-cpg-mssr.c | 161 struct raw_notifier_head notifiers; member
372 &priv->notifiers); in cpg_mssr_register_core_clk()
389 &priv->notifiers); in cpg_mssr_register_core_clk()
891 raw_notifier_call_chain(&priv->notifiers, PM_EVENT_SUSPEND, NULL); in cpg_mssr_suspend_noirq()
907 raw_notifier_call_chain(&priv->notifiers, PM_EVENT_RESUME, NULL); in cpg_mssr_resume_noirq()
996 RAW_INIT_NOTIFIER_HEAD(&priv->notifiers); in cpg_mssr_common_init()
|
| D | rcar-gen4-cpg.h | 75 struct raw_notifier_head *notifiers);
|
| D | rcar-gen3-cpg.h | 84 struct raw_notifier_head *notifiers);
|
| /linux-6.1.9/kernel/power/ |
| D | qos.c | 142 if (c->notifiers) in pm_qos_update_target()
143 blocking_notifier_call_chain(c->notifiers, curr_value, NULL); in pm_qos_update_target()
443 c->notifiers = &qos->min_freq_notifiers; in freq_constraints_init()
444 BLOCKING_INIT_NOTIFIER_HEAD(c->notifiers); in freq_constraints_init()
452 c->notifiers = &qos->max_freq_notifiers; in freq_constraints_init()
453 BLOCKING_INIT_NOTIFIER_HEAD(c->notifiers); in freq_constraints_init()
626 ret = blocking_notifier_chain_register(qos->min_freq.notifiers, in freq_qos_add_notifier()
630 ret = blocking_notifier_chain_register(qos->max_freq.notifiers, in freq_qos_add_notifier()
659 ret = blocking_notifier_chain_unregister(qos->min_freq.notifiers, in freq_qos_remove_notifier()
663 ret = blocking_notifier_chain_unregister(qos->max_freq.notifiers, in freq_qos_remove_notifier()
|
| /linux-6.1.9/Documentation/driver-api/pm/ |
| D | notifiers.rst | 26 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.
|
| D | index.rst | 11 notifiers
|
| /linux-6.1.9/drivers/net/ethernet/mellanox/mlx5/core/ |
| D | events.c | 58 struct mlx5_event_nb notifiers[ARRAY_SIZE(events_nbs_ref)]; member
378 events->notifiers[i].nb = events_nbs_ref[i]; in mlx5_events_start()
379 events->notifiers[i].ctx = events; in mlx5_events_start()
380 mlx5_eq_notifier_register(dev, &events->notifiers[i].nb); in mlx5_events_start()
390 mlx5_eq_notifier_unregister(dev, &events->notifiers[i].nb); in mlx5_events_stop()
|
| /linux-6.1.9/Documentation/devicetree/ |
| D | overlay-notes.rst | 122 There is the option to register notifiers that get called on
130 kfree()ed after OF_OVERLAY_POST_REMOVE notifiers are called. Note that the
134 The changeset notifiers in drivers/of/dynamic.c are a second type of notifier
135 that could be triggered by applying or removing an overlay. These notifiers
|
| D | changesets.rst | 15 at once before emitting OF_RECONFIG notifiers. This is so that the
|
| /linux-6.1.9/drivers/gpu/drm/nouveau/ |
| D | nouveau_abi16.c | 134 list_for_each_entry_safe(ntfy, temp, &chan->notifiers, head) { in nouveau_abi16_chan_fini()
299 INIT_LIST_HEAD(&chan->notifiers); in nouveau_abi16_ioctl_channel_alloc()
528 list_add(&ntfy->head, &chan->notifiers); in nouveau_abi16_ioctl_grobj_alloc()
569 list_add(&ntfy->head, &chan->notifiers); in nouveau_abi16_ioctl_notifierobj_alloc()
630 list_for_each_entry(ntfy, &chan->notifiers, head) { in nouveau_abi16_ioctl_gpuobj_free()
|
| D | nouveau_abi16.h | 25 struct list_head notifiers; member
|
| /linux-6.1.9/Documentation/driver-api/surface_aggregator/clients/ |
| D | cdev.rst | 34 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-6.1.9/drivers/misc/vmw_vmci/ |
| D | vmci_context.c | 700 u32 *notifiers; in vmci_ctx_get_chkpt_notifiers() local
711 data_size = context->n_notifiers * sizeof(*notifiers); in vmci_ctx_get_chkpt_notifiers()
717 notifiers = kmalloc(data_size, GFP_ATOMIC); /* FIXME: want GFP_KERNEL */ in vmci_ctx_get_chkpt_notifiers()
718 if (!notifiers) in vmci_ctx_get_chkpt_notifiers()
722 notifiers[i++] = entry->handle.context; in vmci_ctx_get_chkpt_notifiers()
725 *pbuf = notifiers; in vmci_ctx_get_chkpt_notifiers()
|
| /linux-6.1.9/Documentation/fault-injection/ |
| D | notifier-error-inject.rst | 7 modules that can be used to test the following notifiers.
92 for CPU and memory notifiers.
|
| /linux-6.1.9/Documentation/driver-api/surface_aggregator/ |
| D | client.rst | 153 (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
|
| /linux-6.1.9/drivers/base/power/ |
| D | qos.c | 216 c->notifiers = n; in dev_pm_qos_constraints_allocate()
312 kfree(qos->resume_latency.notifiers); in dev_pm_qos_constraints_destroy()
552 ret = blocking_notifier_chain_register(dev->power.qos->resume_latency.notifiers, in dev_pm_qos_add_notifier()
599 ret = blocking_notifier_chain_unregister(dev->power.qos->resume_latency.notifiers, in dev_pm_qos_remove_notifier()
|