| /linux/Documentation/cpu-freq/ |
| H A 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/drivers/clk/renesas/ |
| H A 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() 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 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);
|
| H A D | rcar-gen3-cpg.c | 345 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 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()
|
| H A D | rcar-gen4-cpg.c | 425 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 D | clk-div6.h | 7 struct raw_notifier_head *notifiers);
|
| H A D | renesas-cpg-mssr.c | 452 &priv->pub.notifiers); in cpg_mssr_register_core_clk() 1096 raw_notifier_call_chain(&priv->pub.notifiers, PM_EVENT_SUSPEND, NULL); in cpg_mssr_suspend_noirq() 1113 raw_notifier_call_chain(&priv->pub.notifiers, PM_EVENT_RESUME, NULL); in cpg_mssr_resume_noirq() 1286 RAW_INIT_NOTIFIER_HEAD(&priv->pub.notifiers); in cpg_mssr_common_init()
|
| /linux/kernel/power/ |
| H A 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() 559 c->notifiers = &qos->min_freq_notifiers; in freq_constraints_init() 560 BLOCKING_INIT_NOTIFIER_HEAD(c->notifiers); in freq_constraints_init() 568 c->notifiers = &qos->max_freq_notifiers; in freq_constraints_init() 569 BLOCKING_INIT_NOTIFIER_HEAD(c->notifiers); in freq_constraints_init() 742 ret = blocking_notifier_chain_register(qos->min_freq.notifiers, in freq_qos_add_notifier() 746 ret = blocking_notifier_chain_register(qos->max_freq.notifiers, in freq_qos_add_notifier() 775 ret = blocking_notifier_chain_unregister(qos->min_freq.notifiers, in freq_qos_remove_notifier() 779 ret = blocking_notifier_chain_unregister(qos->max_freq.notifiers, in freq_qos_remove_notifier()
|
| /linux/Documentation/driver-api/pm/ |
| H A 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.
|
| /linux/drivers/md/dm-vdo/ |
| H A D | flush.c | 34 struct vdo_wait_queue notifiers; member 199 vdo_waitq_dequeue_waiter(&flusher->notifiers)); in finish_notification() 201 if (vdo_waitq_has_waiters(&flusher->notifiers)) in finish_notification() 252 vdo_waiter_as_flush(vdo_waitq_get_first_waiter(&flusher->notifiers)); in notify_flush() 284 may_notify = !vdo_waitq_has_waiters(&flusher->notifiers); in flush_vdo() 285 vdo_waitq_enqueue_waiter(&flusher->notifiers, &flush->waiter); in flush_vdo() 357 (vdo_waitq_has_waiters(&flusher->notifiers) ? "not empty" : "empty"), in vdo_dump_flusher()
|
| /linux/drivers/net/ethernet/mellanox/mlx5/core/ |
| H A D | events.c | 59 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/drivers/misc/vmw_vmci/ |
| H A D | vmci_context.c | 680 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/driver-api/surface_aggregator/clients/ |
| H A 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/Documentation/driver-api/surface_aggregator/ |
| H A 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/Documentation/fault-injection/ |
| H A D | notifier-error-inject.rst | 7 modules that can be used to test the following notifiers. 92 for CPU and memory notifiers.
|
| /linux/drivers/gpu/drm/nouveau/ |
| H A D | nouveau_abi16.c | 188 list_for_each_entry_safe(ntfy, temp, &chan->notifiers, head) { in nouveau_abi16_chan_fini() 404 INIT_LIST_HEAD(&chan->notifiers); in nouveau_abi16_ioctl_channel_alloc() 604 list_add(&ntfy->head, &chan->notifiers); in nouveau_abi16_ioctl_grobj_alloc() 642 list_add(&ntfy->head, &chan->notifiers); in nouveau_abi16_ioctl_notifierobj_alloc() 701 list_for_each_entry(ntfy, &chan->notifiers, head) { in nouveau_abi16_ioctl_gpuobj_free()
|
| H A D | nouveau_abi16.h | 25 struct list_head notifiers; member
|
| /linux/drivers/base/power/ |
| H A D | qos.c | 217 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/kernel/rcu/ |
| H A D | Kconfig.debug | 154 bool "Provide RCU CPU-stall notifiers" 162 Enable RCU CPU-stall notifiers, which are invoked just before 175 Say Y here if you want RCU CPU stall notifiers (you don't want them)
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | suspend-flows.rst | 48 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/devicetree/ |
| H A D | changesets.rst | 15 at once before emitting OF_RECONFIG notifiers. This is so that the
|
| /linux/Documentation/driver-api/memory-devices/ |
| H A D | ti-emif.rst | 50 EMIF driver registers notifiers for voltage and frequency changes
|
| /linux/Documentation/gpu/rfc/ |
| H A D | gpusvm.rst | 62 (rather than seqno due to wider notifiers), pagetable entries, and 107 * May be desirable for faster notifiers.
|
| /linux/Documentation/power/ |
| H A D | freezing-of-tasks.rst | 204 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
|