Searched full:behaviour (Results 1 – 25 of 171) sorted by relevance
1234567
| /Documentation/hwmon/ |
| D | oxp-sensors.rst | 21 Some OneXPlayer and AOKZOE models have a toggle for changing the behaviour
55 "Turbo/Silent" button behaviour toggle is only supported on:
86 button behaviour function. Write "1" to activate the switch and "0" to
87 deactivate it. The specific keycodes and behaviour is specific to the device
|
| D | pwm-fan.rst | 26 pwm1_enable rw keep enable mode, defines behaviour when pwm1=0
|
| /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.
|
| /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,
|
| /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
|
| /Documentation/arch/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
|
| /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``.
|
| /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
|
| /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
398 different error handlers for which behaviour can be configured.
447 If set to 0, the configured retry behaviour will continue until all
461 propagation behaviour for specific errors. There is also a "default" error
462 handler defined, which defines the behaviour for all errors that don't have
498 **Note:** The default behaviour for a specific error handler is dependent on both
[all …]
|
| 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
|
| /Documentation/arch/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
|
| /Documentation/dev-tools/ |
| D | ubsan.rst | 6 UBSAN is a runtime undefined behaviour checker.
22 UBSAN: Undefined behaviour in ../include/linux/bitops.h:110:33
|
| 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
|
| /Documentation/watchdog/ |
| D | watchdog-pm.rst | 12 handling to ensure a uniform behaviour for Linux systems.
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-i2c-devices-pca954x | 7 written to control the behaviour of the multiplexer on
|
| /Documentation/usb/ |
| 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
|
| /Documentation/scheduler/ |
| D | sched-rt-group.rst | 13 2.2 Default behaviour
107 2.2 Default behaviour
114 it. By setting runtime to -1 you'd get the old behaviour back.
|
| /Documentation/userspace-api/media/v4l/ |
| D | v4l2-selection-flags.rst | 33 flag (and ``V4L2_SEL_FLAG_LE``) the behaviour is to choose the
|
| D | selection-api-configuration.rst | 19 control the rounding behaviour using
62 control rounding behaviour using
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe-set-frontend-tune-mode.rst | 34 zigzagging or other "normal" tuning behaviour. Additionally,
|
| /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
|
| /Documentation/core-api/ |
| D | boot-time-mm.rst | 21 Memblock also offers a variety of APIs that control its own behaviour.
|
| /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
|
| /Documentation/networking/ |
| D | seg6-sysctl.rst | 29 Controls the behaviour of computing the flowlabel of outer
|
| D | x25.rst | 31 format and behaviour of the protocol. If time permits this option will also
|
1234567