| /linux-4.4.14/security/yama/ |
| D | yama_lsm.c | 50 struct ptrace_relation *relation; in yama_relation_cleanup() local
54 list_for_each_entry_rcu(relation, &ptracer_relations, node) { in yama_relation_cleanup()
55 if (relation->invalid) { in yama_relation_cleanup()
56 list_del_rcu(&relation->node); in yama_relation_cleanup()
57 kfree_rcu(relation, rcu); in yama_relation_cleanup()
77 struct ptrace_relation *relation, *added; in yama_ptracer_add() local
89 list_for_each_entry_rcu(relation, &ptracer_relations, node) { in yama_ptracer_add()
90 if (relation->invalid) in yama_ptracer_add()
92 if (relation->tracee == tracee) { in yama_ptracer_add()
93 list_replace_rcu(&relation->node, &added->node); in yama_ptracer_add()
[all …]
|
| /linux-4.4.14/drivers/cpufreq/ |
| D | freq_table.c | 123 unsigned int relation, in cpufreq_frequency_table_target() argument
138 target_freq, relation, policy->cpu); in cpufreq_frequency_table_target()
140 switch (relation) { in cpufreq_frequency_table_target()
160 switch (relation) { in cpufreq_frequency_table_target()
|
| D | integrator-cpufreq.c | 78 unsigned int relation) in integrator_set_target() argument
112 if (relation == CPUFREQ_RELATION_L) in integrator_set_target()
|
| D | s3c24xx-cpufreq.c | 277 unsigned int relation) in s3c_cpufreq_target() argument
291 __func__, policy, target_freq, relation); in s3c_cpufreq_target()
295 target_freq, relation, in s3c_cpufreq_target()
330 target_freq, relation, in s3c_cpufreq_target()
|
| D | unicore2-cpufreq.c | 39 unsigned int relation) in ucv2_target() argument
|
| D | amd_freq_sensitivity.c | 42 unsigned int relation) in amd_powersave_bias_target() argument
|
| D | sh-cpufreq.c | 43 unsigned int relation) in sh_cpufreq_target() argument
|
| D | cppc_cpufreq.c | 37 unsigned int relation) in cppc_cpufreq_set_target() argument
|
| D | cpufreq_governor.h | 240 unsigned int freq_next, unsigned int relation);
|
| D | cpufreq_ondemand.c | 77 unsigned int freq_next, unsigned int relation) in generic_powersave_bias_target() argument
95 relation, &index); in generic_powersave_bias_target()
|
| D | cpufreq.c | 1846 unsigned int relation) in __cpufreq_driver_target() argument
1861 policy->cpu, target_freq, relation, old_target_freq); in __cpufreq_driver_target()
1876 retval = cpufreq_driver->target(policy, target_freq, relation); in __cpufreq_driver_target()
1888 target_freq, relation, &index); in __cpufreq_driver_target()
1909 unsigned int relation) in cpufreq_driver_target() argument
1915 ret = __cpufreq_driver_target(policy, target_freq, relation); in cpufreq_driver_target()
|
| D | cpufreq-nforce2.c | 253 unsigned int target_freq, unsigned int relation) in nforce2_target() argument
|
| D | gx-suspmod.c | 377 unsigned int relation) in cpufreq_gx_target() argument
|
| D | pcc-cpufreq.c | 199 unsigned int relation) in pcc_cpufreq_target() argument
|
| /linux-4.4.14/include/linux/ |
| D | cpufreq.h | 241 unsigned int relation); /* Deprecated */
461 unsigned int relation);
464 unsigned int relation);
568 unsigned int relation,
|
| /linux-4.4.14/Documentation/devicetree/bindings/iommu/ |
| D | samsung,sysmmu.txt | 13 System MMUs are in many to one relation with peripheral devices, i.e. single
16 device. The relation between a System MMU and the peripheral device needs to be
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | cpu-drivers.txt | 174 unsigned int target_frequency, unsigned int relation.
181 - if relation==CPUFREQ_REL_L, try to select a new_freq higher than or equal
183 - if relation==CPUFREQ_REL_H, try to select a new_freq lower than or equal
249 unsigned int relation,
|
| D | governors.txt | 254 unsigned int relation);
258 unsigned int relation);
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-class-bdi | 37 writeout speed in relation to the other devices.
|
| /linux-4.4.14/Documentation/extcon/ |
| D | porting-android-switch-class | 103 ****** STEP 4. Inter-cable relation (mutually exclusive)
|
| /linux-4.4.14/Documentation/devicetree/bindings/thermal/ |
| D | thermal.txt | 156 Type: sub-node map nodes, used to describe the relation between trips
161 Type: array coefficients to compose a linear relation between
552 * linear relation. E.g.:
|
| /linux-4.4.14/Documentation/locking/ |
| D | lockstat.txt | 16 The graph below shows the relation between the lock functions and the various
|
| /linux-4.4.14/Documentation/power/ |
| D | power_supply_class.txt | 95 no direct relation between voltage and battery capacity, but some dumb
|
| /linux-4.4.14/Documentation/usb/ |
| D | mass-storage.txt | 22 relation to mass storage function (or MSF) and different gadgets
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | README.pvrusb2 | 79 relation to the Linux kernel's concept of a loadable module.)
|
| /linux-4.4.14/Documentation/trace/ |
| D | ftrace-design.txt | 45 is a major issue at this point, especially in relation to the location of the
|
| /linux-4.4.14/arch/x86/math-emu/ |
| D | README | 363 accuracy is discussed above in relation to the Turbo C "emulator", and
|
| /linux-4.4.14/Documentation/thermal/ |
| D | sysfs-api.txt | 141 .trip_mask:This is a bit mask that gives the binding relation between
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | kconfig-language.txt | 405 symbols, this is currently not possible if there is a circular relation
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cpusets.txt | 453 This mismatch is why there is not a simple one-to-one relation
|
| /linux-4.4.14/Documentation/ |
| D | pinctrl.txt | 806 The GPIO portions of a pin and its relation to a certain pin controller
|
| /linux-4.4.14/Documentation/security/ |
| D | keys.txt | 1189 The payload attached need not bear any relation to the data passed to this
|