Home
last modified time | relevance | path

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

123

/openbmc/qemu/util/
H A Dnotify.c21 QLIST_INIT(&list->notifiers); in notifier_list_init()
26 QLIST_INSERT_HEAD(&list->notifiers, notifier, node); in notifier_list_add()
38 QLIST_FOREACH_SAFE(notifier, &list->notifiers, node, next) { in notifier_list_notify()
45 return QLIST_EMPTY(&list->notifiers); in notifier_list_empty()
50 QLIST_INIT(&list->notifiers); in notifier_with_return_list_init()
56 QLIST_INSERT_HEAD(&list->notifiers, notifier, node); in notifier_with_return_list_add()
70 QLIST_FOREACH_SAFE(notifier, &list->notifiers, node, next) { in notifier_with_return_list_notify()
/openbmc/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
/openbmc/qemu/include/qemu/
H A Dnotify.h29 QLIST_HEAD(, Notifier) notifiers;
33 { QLIST_HEAD_INITIALIZER((head).notifiers) }
62 QLIST_HEAD(, NotifierWithReturn) notifiers;
66 { QLIST_HEAD_INITIALIZER((head).notifiers) }
/openbmc/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 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 Dclk-div6.h7 struct raw_notifier_head *notifiers);
H A Drcar-gen3-cpg.c350 struct raw_notifier_head *notifiers) in rcar_gen3_cpg_clk_register() argument
407 __clk_get_name(parent), notifiers); in rcar_gen3_cpg_clk_register()
435 cpg_simple_notifier_register(notifiers, csn); in rcar_gen3_cpg_clk_register()
527 __clk_get_name(parent), notifiers); in rcar_gen3_cpg_clk_register()
H A Drcar-gen2-cpg.h36 struct raw_notifier_head *notifiers);
H A Dr8a77970-cpg-mssr.c226 struct raw_notifier_head *notifiers) in r8a77970_cpg_clk_register() argument
243 notifiers); in r8a77970_cpg_clk_register()
H A Drenesas-cpg-mssr.c161 struct raw_notifier_head notifiers; member
366 &priv->notifiers); in cpg_mssr_register_core_clk()
383 &priv->notifiers); in cpg_mssr_register_core_clk()
885 raw_notifier_call_chain(&priv->notifiers, PM_EVENT_SUSPEND, NULL); in cpg_mssr_suspend_noirq()
902 raw_notifier_call_chain(&priv->notifiers, PM_EVENT_RESUME, NULL); in cpg_mssr_resume_noirq()
984 RAW_INIT_NOTIFIER_HEAD(&priv->notifiers); in cpg_mssr_common_init()
H A Drcar-gen4-cpg.c334 struct raw_notifier_head *notifiers) in rcar_gen4_cpg_clk_register() argument
404 __clk_get_name(parent), notifiers); in rcar_gen4_cpg_clk_register()
442 __clk_get_name(parent), notifiers); in rcar_gen4_cpg_clk_register()
/openbmc/linux/kernel/power/
H A Dqos.c142 if (c->notifiers) in pm_qos_update_target()
143 blocking_notifier_call_chain(c->notifiers, curr_value, NULL); in pm_qos_update_target()
453 c->notifiers = &qos->min_freq_notifiers; in freq_constraints_init()
454 BLOCKING_INIT_NOTIFIER_HEAD(c->notifiers); in freq_constraints_init()
462 c->notifiers = &qos->max_freq_notifiers; in freq_constraints_init()
463 BLOCKING_INIT_NOTIFIER_HEAD(c->notifiers); in freq_constraints_init()
636 ret = blocking_notifier_chain_register(qos->min_freq.notifiers, in freq_qos_add_notifier()
640 ret = blocking_notifier_chain_register(qos->max_freq.notifiers, in freq_qos_add_notifier()
669 ret = blocking_notifier_chain_unregister(qos->min_freq.notifiers, in freq_qos_remove_notifier()
673 ret = blocking_notifier_chain_unregister(qos->max_freq.notifiers, in freq_qos_remove_notifier()
/openbmc/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.
H A Dindex.rst11 notifiers
/openbmc/linux/drivers/net/ethernet/mellanox/mlx5/core/
H A Devents.c58 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()
/openbmc/qemu/hw/xen/
H A Dxen-operations.c213 NotifierList notifiers; member
227 notifier_list_notify(&h->notifiers, v); in watch_event()
244 notifier_list_init(&h->notifiers); in libxenstore_open()
252 g_assert(notifier_list_empty(&h->notifiers)); in libxenstore_close()
362 notifier_list_add(&h->notifiers, &w->notifier); in libxenstore_watch()
/openbmc/linux/Documentation/devicetree/
H A Doverlay-notes.rst122 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
/openbmc/linux/drivers/gpu/drm/nouveau/
H A Dnouveau_abi16.c146 list_for_each_entry_safe(ntfy, temp, &chan->notifiers, head) { in nouveau_abi16_chan_fini()
350 INIT_LIST_HEAD(&chan->notifiers); in nouveau_abi16_ioctl_channel_alloc()
584 list_add(&ntfy->head, &chan->notifiers); in nouveau_abi16_ioctl_grobj_alloc()
625 list_add(&ntfy->head, &chan->notifiers); in nouveau_abi16_ioctl_notifierobj_alloc()
686 list_for_each_entry(ntfy, &chan->notifiers, head) { in nouveau_abi16_ioctl_gpuobj_free()
H A Dnouveau_abi16.h25 struct list_head notifiers; member
/openbmc/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.
/openbmc/linux/drivers/misc/vmw_vmci/
H A Dvmci_context.c700 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()
/openbmc/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
/openbmc/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.
/openbmc/qemu/include/hw/virtio/
H A Dvhost-user.h68 GPtrArray *notifiers; member

123