| /linux-4.1.27/Documentation/cpu-freq/ |
| D | core.txt | 22 2. CPUFreq notifiers
31 frequency transitions), as well as to "notifiers". These are device
44 2. CPUFreq notifiers
47 CPUFreq notifiers conform to the standard kernel notifier interface.
48 See linux/include/linux/notifier.h for details on notifiers.
50 There are two different CPUFreq notifiers - policy notifiers and
51 transition notifiers.
54 2.1 CPUFreq policy notifiers
60 1.) During CPUFREQ_ADJUST all CPUFreq notifiers may change the limit if
67 3.) And during CPUFREQ_NOTIFY all notifiers are informed of the new policy
[all …]
|
| D | index.txt | 22 of CPUFreq notifiers
|
| /linux-4.1.27/Documentation/power/ |
| D | notifiers.txt | 1 Suspend notifiers
15 The subsystems or drivers having such needs can register suspend notifiers that
20 below because here we do additional work between notifiers
42 It is generally assumed that whatever the notifiers do for
45 PM_POST_SUSPEND. Additionally, all of the notifiers are called for
47 all of the notifiers are called for PM_POST_SUSPEND if one of them fails for
50 The hibernation and suspend notifiers are called with pm_mutex held. They are
|
| D | 00-INDEX | 17 notifiers.txt
18 - Registering suspend notifiers in device drivers
|
| D | freezing-of-tasks.txt | 183 hibernation (and suspend) notifiers (in that case, though, we won't be able to
200 requested early enough using the suspend notifier API described in notifiers.txt.
209 notifiers to achieve mutual exclusion. Look at the CPU-Hotplug code
|
| D | pm_qos_interface.txt | 42 registered notifiers are called only if the target value is now different.
113 registered notifiers are called only if the target value is now different.
|
| D | devices.txt | 663 management notifiers that are called before tasks are frozen and after they have
664 been thawed. Generally speaking, the PM notifiers are suitable for performing
668 For details refer to Documentation/power/notifiers.txt.
|
| D | pci.txt | 716 in Documentation/power/notifiers.txt).
|
| /linux-4.1.27/kernel/power/ |
| D | qos.c | 73 .notifiers = &cpu_dma_lat_notifier,
87 .notifiers = &network_lat_notifier,
102 .notifiers = &network_throughput_notifier,
117 .notifiers = &memory_bandwidth_notifier,
315 if (c->notifiers) in pm_qos_update_target()
316 blocking_notifier_call_chain(c->notifiers, in pm_qos_update_target()
561 pm_qos_array[pm_qos_class]->constraints->notifiers, in pm_qos_add_notifier()
581 pm_qos_array[pm_qos_class]->constraints->notifiers, in pm_qos_remove_notifier()
|
| /linux-4.1.27/drivers/staging/unisys/visorchipset/ |
| D | visorchipset_main.c | 556 struct visorchipset_busdev_notifiers *notifiers, in visorchipset_register_busdev_server() argument
561 if (!notifiers) { in visorchipset_register_busdev_server()
566 busdev_server_notifiers = *notifiers; in visorchipset_register_busdev_server()
581 struct visorchipset_busdev_notifiers *notifiers, in visorchipset_register_busdev_client() argument
586 if (!notifiers) { in visorchipset_register_busdev_client()
591 busdev_client_notifiers = *notifiers; in visorchipset_register_busdev_client()
943 struct visorchipset_busdev_notifiers *notifiers = NULL; in device_epilog() local
957 notifiers = &busdev_server_notifiers; in device_epilog()
959 notifiers = &busdev_client_notifiers; in device_epilog()
971 if (notifiers->device_create) { in device_epilog()
[all …]
|
| D | visorchipset.h | 198 struct visorchipset_busdev_notifiers *notifiers,
210 struct visorchipset_busdev_notifiers *notifiers,
|
| /linux-4.1.27/Documentation/fault-injection/ |
| D | notifier-error-inject.txt | 7 modules that can be used to test the following notifiers.
16 This feature can be used to test the error handling of the CPU notifiers by
93 for CPU and memory notifiers.
|
| /linux-4.1.27/drivers/misc/vmw_vmci/ |
| D | vmci_context.c | 698 u32 *notifiers; in vmci_ctx_get_chkpt_notifiers() local
709 data_size = context->n_notifiers * sizeof(*notifiers); in vmci_ctx_get_chkpt_notifiers()
715 notifiers = kmalloc(data_size, GFP_ATOMIC); /* FIXME: want GFP_KERNEL */ in vmci_ctx_get_chkpt_notifiers()
716 if (!notifiers) in vmci_ctx_get_chkpt_notifiers()
720 notifiers[i++] = entry->handle.context; in vmci_ctx_get_chkpt_notifiers()
723 *pbuf = notifiers; in vmci_ctx_get_chkpt_notifiers()
|
| /linux-4.1.27/drivers/gpu/drm/nouveau/ |
| D | nouveau_abi16.c | 120 list_for_each_entry_safe(ntfy, temp, &chan->notifiers, head) { in nouveau_abi16_chan_fini()
278 INIT_LIST_HEAD(&chan->notifiers); in nouveau_abi16_ioctl_channel_alloc()
448 list_add(&ntfy->head, &chan->notifiers); in nouveau_abi16_ioctl_notifierobj_alloc()
528 list_for_each_entry(ntfy, &chan->notifiers, head) { in nouveau_abi16_ioctl_gpuobj_free()
|
| D | nouveau_abi16.h | 24 struct list_head notifiers; member
|
| /linux-4.1.27/drivers/base/power/ |
| D | qos.c | 207 c->notifiers = n; in dev_pm_qos_constraints_allocate()
284 kfree(c->notifiers); in dev_pm_qos_constraints_destroy()
503 ret = blocking_notifier_chain_register(dev->power.qos->resume_latency.notifiers, in dev_pm_qos_add_notifier()
530 retval = blocking_notifier_chain_unregister(dev->power.qos->resume_latency.notifiers, in dev_pm_qos_remove_notifier()
|
| /linux-4.1.27/Documentation/memory-devices/ |
| D | ti-emif.txt | 45 EMIF driver registers notifiers for voltage and frequency changes
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | changesets.txt | 9 at once before emitting OF_RECONFIG notifiers. This is so that the
|
| /linux-4.1.27/include/linux/ |
| D | pm_qos.h | 89 struct blocking_notifier_head *notifiers; member
|
| /linux-4.1.27/lib/ |
| D | Kconfig.kgdb | 62 bool "KGDB: Allow debugging with traps in notifiers"
|
| D | Kconfig.debug | 1370 the error handling of the cpu notifiers by injecting artificial
|
| /linux-4.1.27/Documentation/ |
| D | cpu-hotplug.txt | 306 You can fail PREPARE notifiers if something doesn't work to prepare resources.
313 A: Yes, CPU notifiers are called only when new CPUs are on-lined or offlined.
|
| D | kernel-parameters.txt | 2601 Run kdump after running panic-notifiers and dumping
2605 because some panic notifiers can make the crashed
|
| /linux-4.1.27/drivers/media/platform/soc_camera/ |
| D | soc_camera.c | 2007 LIST_HEAD(notifiers); in soc_camera_host_unregister()
2015 list_add(&icd->sasc->list, ¬ifiers); in soc_camera_host_unregister()
2019 list_for_each_entry(sasc, ¬ifiers, list) { in soc_camera_host_unregister()
|