/kernel/linux/linux-5.10/drivers/net/wireless/broadcom/b43/ |
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 …]
|
/kernel/linux/linux-5.10/drivers/net/wireless/broadcom/b43legacy/ |
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 …]
|
/kernel/linux/linux-5.10/Documentation/admin-guide/ |
D | xfs.rst | 30 The default behaviour is for dynamic end-of-file 35 the dynamic behaviour. 45 The default behaviour is determined by the on-disk feature 46 bit indicating that ``attr2`` behaviour is active. If either 112 (in bytes) will be returned instead. Otherwise the behaviour 393 different error handlers for which behaviour can be configured. 442 If set to 0, the configured retry behaviour will continue until all 456 propagation behaviour for specific errors. There is also a "default" error 457 handler defined, which defines the behaviour for all errors that don't have 493 **Note:** The default behaviour for a specific error handler is dependent on both [all …]
|
D | dynamic-debug-howto.rst | 43 Controlling dynamic debug Behaviour 46 The behaviour of ``pr_debug()``/``dev_dbg()`` are controlled via writing to a 65 Viewing Dynamic Debug Behaviour 68 You can view the currently configured behaviour of all the debug
|
/kernel/linux/linux-5.10/Documentation/admin-guide/mm/ |
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``.
|
/kernel/linux/linux-5.10/Documentation/sound/designs/ |
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
|
/kernel/linux/linux-5.10/Documentation/arm64/ |
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
|
/kernel/linux/linux-5.10/Documentation/driver-api/thermal/ |
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,
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/ |
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.
|
/kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/ |
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
|
/kernel/linux/linux-5.10/drivers/mfd/ |
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 …]
|
/kernel/linux/linux-5.10/lib/ |
D | Kconfig.ubsan | 6 bool "Undefined behaviour sanity checker" 8 This option enables the Undefined Behaviour sanity checker.
|
/kernel/linux/linux-5.10/include/uapi/linux/ |
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 */
|
/kernel/linux/linux-5.10/Documentation/usb/ |
D | functionfs.rst | 6 unique behaviour. It may be added to an USB configuration only after 59 parameter's value is just a one-element list, then the behaviour
|
/kernel/linux/linux-5.10/Documentation/arm/ |
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
|
/kernel/linux/linux-5.10/Documentation/scheduler/ |
D | sched-rt-group.rst | 13 2.2 Default behaviour 105 2.2 Default behaviour 112 it. By setting runtime to -1 you'd get the old behaviour back.
|
/kernel/linux/linux-5.10/Documentation/dev-tools/ |
D | ubsan.rst | 4 UBSAN is a runtime undefined behaviour checker. 20 UBSAN: Undefined behaviour in ../include/linux/bitops.h:110:33
|
D | kcsan.rst | 18 KCSAN provides several other configuration options to customize behaviour (see 106 behaviour when encountering a data race is deemed safe. 158 changes the report filtering behaviour. For example, the blacklist feature 224 operations result in unexpected system behaviour. On the other hand, data races
|
/kernel/linux/linux-5.10/drivers/char/hw_random/ |
D | xiphera-trng.c | 79 * hence we incorporate a small delay to ensure proper behaviour in xiphera_trng_probe() 97 * once again, to ensure proper behaviour we sleep in xiphera_trng_probe()
|
/kernel/linux/linux-5.10/drivers/gpu/drm/sun4i/ |
D | sunxi_engine.h | 19 * implement the proper behaviour. 103 * behaviour part of the VBLANK event. It is run with all the
|
/kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/ |
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
|
/kernel/linux/linux-5.10/Documentation/driver-api/ |
D | isa.rst | 59 ALSA would want to keep the old non-load behaviour, it could stick all 62 behaviour of always loading as it inadvertently did for a bit after the
|
/kernel/linux/linux-5.10/Documentation/hwmon/ |
D | abituguru-datasheet.rst | 220 Alarm behaviour for the selected sensor. A 1 enables the described 221 behaviour. 311 Alarm behaviour for the selected sensor. A 1 enables the described behaviour.
|
/kernel/linux/linux-5.10/arch/powerpc/platforms/pseries/ |
D | setup.c | 525 if (result->behaviour & H_CPU_BEHAV_FLUSH_COUNT_CACHE) in init_cpu_char_feature_flags() 528 if (result->behaviour & H_CPU_BEHAV_FLUSH_LINK_STACK) in init_cpu_char_feature_flags() 535 if (!(result->behaviour & H_CPU_BEHAV_FAVOUR_SECURITY)) in init_cpu_char_feature_flags() 538 if (!(result->behaviour & H_CPU_BEHAV_L1D_FLUSH_PR)) in init_cpu_char_feature_flags() 541 if (result->behaviour & H_CPU_BEHAV_NO_L1D_FLUSH_ENTRY) in init_cpu_char_feature_flags() 544 if (result->behaviour & H_CPU_BEHAV_NO_L1D_FLUSH_UACCESS) in init_cpu_char_feature_flags() 547 if (!(result->behaviour & H_CPU_BEHAV_BNDS_CHK_SPEC_BAR)) in init_cpu_char_feature_flags()
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
D | aspeed-scu.txt | 1 The Aspeed System Control Unit manages the global behaviour of the SoC,
|