Searched full:behaviour (Results 1 – 25 of 143) sorted by relevance
123456
| /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/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
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 …]
|
| /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/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/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
|
| /Documentation/devicetree/bindings/mfd/ |
| D | aspeed-scu.txt | 1 The Aspeed System Control Unit manages the global behaviour of the SoC,
|
| /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
|
| /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
|
| /Documentation/watchdog/ |
| D | watchdog-pm.rst | 12 handling to ensure a uniform behaviour for Linux systems.
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | axp20x_usb_power.txt | 9 The AXP223 PMIC shares most of its behaviour with the AXP221 but has slight
|
| /Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra30-actmon.txt | 3 The activity monitor block collects statistics about the behaviour of other
|
| /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.
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-i2c-devices-pca954x | 7 written to control the behaviour of the multiplexer on
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe-set-frontend-tune-mode.rst | 34 zigzagging or other "normal" tuning behaviour. Additionally,
|
| /Documentation/userspace-api/media/v4l/ |
| D | v4l2-selection-flags.rst | 27 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/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/devicetree/bindings/media/ |
| D | renesas,fcp.yaml | 19 FCP for FDP (FCPF). Their configuration and behaviour depend on the module
|
| /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 | x25.rst | 33 format and behaviour of the protocol. If time permits this option will also
|
| /Documentation/devicetree/bindings/dma/ |
| D | ingenic,dma.yaml | 56 1, which can be configured to have special behaviour for NAND/BCH
|
123456