| /linux/drivers/net/wireless/broadcom/b43/ |
| H A D | leds.c | 148 enum b43_led_behaviour behaviour, in b43_map_led() argument
154 /* Map the b43 specific LED behaviour value to the in b43_map_led()
156 switch (behaviour) { in b43_map_led()
194 b43warn(dev->wl, "LEDs: Unknown behaviour 0x%02X\n", in b43_map_led()
195 behaviour); in b43_map_led()
202 enum b43_led_behaviour *behaviour, in b43_led_get_sprominfo() argument
218 *behaviour = B43_LED_ACTIVITY; in b43_led_get_sprominfo()
221 *behaviour = B43_LED_RADIO_ALL; in b43_led_get_sprominfo()
224 *behaviour = B43_LED_RADIO_B; in b43_led_get_sprominfo()
226 *behaviour = B43_LED_ASSOC; in b43_led_get_sprominfo()
[all …]
|
| /linux/drivers/net/wireless/broadcom/b43legacy/ |
| H A D | leds.c | 117 enum b43legacy_led_behaviour behaviour, in b43legacy_map_led() argument
123 /* Map the b43 specific LED behaviour value to the in b43legacy_map_led()
125 switch (behaviour) { in b43legacy_map_led()
170 b43legacywarn(dev->wl, "LEDs: Unknown behaviour 0x%02X\n", in b43legacy_map_led()
171 behaviour); in b43legacy_map_led()
181 enum b43legacy_led_behaviour behaviour; in b43legacy_leds_init() local
196 behaviour = B43legacy_LED_ACTIVITY; in b43legacy_leds_init()
199 behaviour = B43legacy_LED_RADIO_ALL; in b43legacy_leds_init()
202 behaviour = B43legacy_LED_RADIO_B; in b43legacy_leds_init()
204 behaviour = B43legacy_LED_ASSOC; in b43legacy_leds_init()
[all …]
|
| /linux/arch/arm64/kvm/ |
| H A D | emulate-nested.c | 30 const enum trap_behaviour behaviour; member
147 .behaviour = BEHAVE_FORWARD_READ,
153 .behaviour = BEHAVE_FORWARD_RW,
159 .behaviour = BEHAVE_FORWARD_READ,
165 .behaviour = BEHAVE_FORWARD_WRITE,
171 .behaviour = BEHAVE_FORWARD_WRITE,
177 .behaviour = BEHAVE_FORWARD_RW,
183 .behaviour = BEHAVE_FORWARD_RW,
189 .behaviour = BEHAVE_FORWARD_RW,
195 .behaviour = BEHAVE_FORWARD_RW,
[all …]
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | nommu-mmap.rst | 12 Memory mapping behaviour also involves the way fork(), vfork(), clone() and
16 The behaviour is similar between the MMU and no-MMU cases, but not identical;
31 the no-MMU case doesn't support these, behaviour is identical to
272 Adjusting page trimming behaviour
277 fragmentation, and as such, is left configurable. The default behaviour is to
280 behaviour can either be disabled completely, or bumped up to a higher page
283 Page trimming behaviour is configurable via the sysctl ``vm.nr_trim_pages``.
|
| /linux/Documentation/arch/arm64/ |
| H A D | tagged-address-abi.rst | 54 NOTE: This behaviour changed in v5.6 and so some earlier kernels may
64 NOTE: This behaviour changed in v5.14 and so some earlier kernels may
101 - The syscall behaviour is undefined for invalid tagged pointers: it may
105 - The syscall behaviour for a valid tagged pointer is the same as for
|
| /linux/Documentation/sound/designs/ |
| H A D | tracepoints.rst | 47 convenient parameters or change their behaviour.
93 it. Else, zero. But this behaviour depends on implementations in driver
99 it. Else, zero. But this behaviour depends on implementations in driver
105 also calculated according to it. Else, zero. But this behaviour depends
|
| /linux/Documentation/driver-api/thermal/ |
| H A D | cpu-cooling-api.rst | 78 - In running time the 'execution' behaviour (instruction types, memory
87 f(run) here represents the described execution behaviour and its
91 The detailed behaviour for f(run) could be modelled on-line. However,
|
| /linux/Documentation/admin-guide/ |
| H A D | xfs.rst | 30 The default behaviour is for dynamic end-of-file
35 the dynamic behaviour.
90 (in bytes) will be returned instead. Otherwise the behaviour
384 different error handlers for which behaviour can be configured.
433 If set to 0, the configured retry behaviour will continue until all
447 propagation behaviour for specific errors. There is also a "default" error
448 handler defined, which defines the behaviour for all errors that don't have
484 **Note:** The default behaviour for a specific error handler is dependent on both
487 to "fail immediately" behaviour. This is done because ENODEV is a fatal,
|
| H A D | dynamic-debug-howto.rst | 34 Viewing Dynamic Debug Behaviour
37 You can view the currently configured behaviour in the *prdbg* catalog::
51 Controlling dynamic debug Behaviour
54 The behaviour of *prdbg* sites are controlled by writing
|
| /linux/drivers/mfd/ |
| H A D | si476x-cmd.c | 488 * #SI476X_DCLK_NOOP - do not modify the behaviour
494 * #SI476X_DFS_NOOP - do not modify the behaviour
500 * SI476X_DOUT_NOOP - do not modify the behaviour
508 * SI476X_XOUT_NOOP - do not modify the behaviour
545 * SI476X_IQCLK_NOOP - do not modify the behaviour
551 * SI476X_IQFS_NOOP - do not modify the behaviour
557 * SI476X_IOUT_NOOP - do not modify the behaviour
562 * SI476X_QOUT_NOOP - do not modify the behaviour
595 * SI476X_ICIN_NOOP - do not modify the behaviour
602 * SI476X_ICIP_NOOP - do not modify the behaviour
[all …]
|
| /linux/kernel/ |
| H A D | Kconfig.preempt | 115 This switch provides the old behaviour for testing reasons. Select
117 the old synchronized behaviour.
127 bool "Preemption behaviour defined on boot"
|
| /linux/Documentation/devicetree/bindings/ |
| H A D | ABI.rst | 15 then default to the previous behaviour if it is missing. If a binding
32 behaviour when a newly added property is missing.
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-flakey.rst | 6 unreliable behaviour periodically. It's been found useful in simulating
10 <up interval> seconds, then exhibits unreliable behaviour for <down
|
| /linux/sound/hda/common/ |
| H A D | Kconfig | 72 controls (old behaviour until this option is available).
78 The old behaviour (Y) is obsolete and will be removed. Consider
|
| /linux/arch/powerpc/platforms/pseries/ |
| H A D | setup.c | 562 if (result->behaviour & H_CPU_BEHAV_FLUSH_COUNT_CACHE) in init_cpu_char_feature_flags()
565 if (result->behaviour & H_CPU_BEHAV_FLUSH_LINK_STACK) in init_cpu_char_feature_flags()
574 if (!(result->behaviour & H_CPU_BEHAV_FAVOUR_SECURITY)) { in init_cpu_char_feature_flags()
577 } else if (result->behaviour & H_CPU_BEHAV_FAVOUR_SECURITY_H) in init_cpu_char_feature_flags()
582 if (!(result->behaviour & H_CPU_BEHAV_L1D_FLUSH_PR)) in init_cpu_char_feature_flags()
585 if (result->behaviour & H_CPU_BEHAV_NO_L1D_FLUSH_ENTRY) in init_cpu_char_feature_flags()
588 if (result->behaviour & H_CPU_BEHAV_NO_L1D_FLUSH_UACCESS) in init_cpu_char_feature_flags()
591 if (result->behaviour & H_CPU_BEHAV_NO_STF_BARRIER) in init_cpu_char_feature_flags()
594 if (!(result->behaviour & H_CPU_BEHAV_BNDS_CHK_SPEC_BAR)) in init_cpu_char_feature_flags()
|
| /linux/include/uapi/linux/ |
| H A D | eventpoll.h | 65 /* Set the One Shot behaviour for the target file descriptor */
68 /* Set the Edge Triggered behaviour for the target file descriptor */
|
| /linux/drivers/firmware/arm_scmi/transports/ |
| H A D | Kconfig | 58 mode, avoiding any kind of sleeping behaviour for selected
115 mode, avoiding any kind of sleeping behaviour for selected
|
| /linux/Documentation/arch/arm/ |
| H A D | mem_alignment.rst | 26 Please note that randomly changing the behaviour without good thought is
27 real bad - it changes the behaviour of all unaligned instructions in user
|
| /linux/Documentation/scheduler/ |
| H A D | sched-rt-group.rst | 13 2.2 Default behaviour
110 2.2 Default behaviour
117 it. By setting runtime to -1 you'd get the old behaviour back.
|
| /linux/Documentation/dev-tools/ |
| H A D | ubsan.rst | 6 UBSAN is a runtime undefined behaviour checker.
22 UBSAN: Undefined behaviour in ../include/linux/bitops.h:110:33
|
| H A D | testing-overview.rst | 21 If you're looking to verify the behaviour of the Kernel — particularly specific
91 concurrency issues such as data races, or other undefined behaviour like
100 * UBSAN detects behaviour that is undefined by the C standard, like integer
|
| /linux/drivers/char/hw_random/ |
| H A D | xiphera-trng.c | 76 * hence we incorporate a small delay to ensure proper behaviour in xiphera_trng_probe()
94 * once again, to ensure proper behaviour we sleep in xiphera_trng_probe()
|
| /linux/arch/arm64/boot/dts/marvell/ |
| H A D | cn9130-cf-base.dts | 65 * Configure LEDs default behaviour:
105 * Configure LEDs default behaviour:
|
| /linux/Documentation/usb/ |
| H A D | functionfs.rst | 9 unique behaviour. It may be added to an USB configuration only after
64 parameter's value is just a one-element list, then the behaviour
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A D | video_extension.rst | 118 directly. This behaviour can be controlled through the brightness_switch_enabled
120 recommended to disable this behaviour once a GUI environment starts up and
|