Searched full:allowed (Results 1 – 25 of 425) sorted by relevance
12345678910>>...17
/Documentation/devicetree/bindings/regulator/ |
D | mt6360-regulator.yaml | 51 regulator-allowed-modes = <MT6360_OPMODE_NORMAL 60 regulator-allowed-modes = <MT6360_OPMODE_NORMAL 69 regulator-allowed-modes = <MT6360_OPMODE_NORMAL 77 regulator-allowed-modes = <MT6360_OPMODE_NORMAL 85 regulator-allowed-modes = <MT6360_OPMODE_NORMAL 93 regulator-allowed-modes = <MT6360_OPMODE_NORMAL 101 regulator-allowed-modes = <MT6360_OPMODE_NORMAL 109 regulator-allowed-modes = <MT6360_OPMODE_NORMAL
|
D | act8945a-regulator.txt | 18 regulator-initial-mode, regulator-allowed-modes and regulator-mode could be 42 regulator-allowed-modes = <ACT8945A_REGULATOR_MODE_FIXED>, 61 regulator-allowed-modes = <ACT8945A_REGULATOR_MODE_FIXED>, 83 regulator-allowed-modes = <ACT8945A_REGULATOR_MODE_NORMAL>,
|
D | mcp16502-regulator.txt | 41 regulator-allowed-modes = <2>, <4>; 60 regulator-allowed-modes = <2>, <4>; 79 regulator-allowed-modes = <2>, <4>; 98 regulator-allowed-modes = <2>, <4>;
|
D | act8865-regulator.txt | 37 regulator-initial-mode, regulator-allowed-modes and regulator-mode could be specified 75 regulator-allowed-modes = <ACT8865_REGULATOR_MODE_FIXED>, 101 regulator-allowed-modes = <ACT8865_REGULATOR_MODE_NORMAL>,
|
/Documentation/admin-guide/mm/ |
D | numa_memory_policy.rst | 252 the user should not be remapped if the task or VMA's set of allowed 256 change in the set of allowed nodes, the node (Preferred) or 258 allowed nodes. This may result in nodes being used that were 262 nodes allowed by the task's cpuset, then the memory policy is 270 3 is allowed from the user's nodemask, the "interleave" only 272 now allowed, the Default behavior is used. 282 set of allowed nodes. The kernel stores the user-passed nodemask, 283 and if the allowed nodes changes, then that original nodemask will 284 be remapped relative to the new set of allowed nodes. 287 mempolicy is rebound because of a change in the set of allowed [all …]
|
D | hugetlbpage.rst | 160 over all the set of allowed nodes specified by the NUMA memory policy of the 161 task that modifies ``nr_hugepages``. The default for the allowed nodes--when the 162 task has default memory policy--is all on-line nodes with memory. Allowed 188 indicates that the hugetlb subsystem is allowed to try to obtain that 211 no more surplus huge pages will be allowed to be allocated. 276 possibly, allocation of persistent huge pages on nodes not allowed by 289 #. The nodes allowed mask will be derived from any non-default task mempolicy, 362 The ``size`` option sets the maximum value of memory (huge pages) allowed 367 The ``min_size`` option sets the minimum value of memory (huge pages) allowed
|
/Documentation/admin-guide/LSM/ |
D | Yama.rst | 26 exist and remain possible if ptrace is allowed to operate as before. 28 builders should be allowed the option to disable this debugging system. 40 other process (and its descendants) are allowed to call ``PTRACE_ATTACH`` 46 so that any otherwise allowed process (even those in external pid namespaces) 64 an allowed debugger PID to call ``PTRACE_ATTACH`` on the inferior.
|
/Documentation/admin-guide/device-mapper/ |
D | dm-init.rst | 46 `crypt` allowed 47 `delay` allowed 50 `linear` allowed 55 `snapshot-origin` allowed 57 `striped` allowed 61 `verity` allowed
|
/Documentation/devicetree/bindings/mfd/ |
D | mxs-lradc.txt | 15 Allowed value is 1 ... 32, default is 4 16 - fsl,ave-delay: delay between consecutive samples. Allowed value is 19 - fsl,settling: delay between plate switch to next sample. Allowed value is
|
/Documentation/userspace-api/media/dvb/ |
D | frontend_f_open.rst | 33 Multiple opens are allowed with ``O_RDONLY``. In this mode, only 34 query and read ioctls are allowed. 36 Only one open is allowed in ``O_RDWR``. In this mode, all ioctls are 37 allowed.
|
/Documentation/admin-guide/cgroup-v1/ |
D | cpusets.rst | 61 schedule a task on a CPU that is not allowed in its cpus_allowed 63 node that is not allowed in the requesting task's mems_allowed vector. 122 - Cpusets are sets of allowed CPUs and Memory Nodes, known to the 127 allowed in that task's cpuset. 129 those Memory Nodes allowed in that task's cpuset. 147 allowed in that task's cpuset. 149 the CPUs allowed by their cpuset, if possible. 151 Memory Nodes by what's allowed in that task's cpuset. 152 - in page_alloc.c, to restrict memory to allowed nodes. 181 - cpuset.memory_spread_page flag: if set, spread page cache evenly on allowed nodes [all …]
|
/Documentation/ABI/testing/ |
D | sysfs-memory-page-offline | 21 the file is not allowed. 44 Reading the file is not allowed.
|
D | sysfs-class-powercap | 119 Maximum allowed power in micro watts for this constraint. 127 Minimum allowed power in micro watts for this constraint. 135 Maximum allowed time window in micro seconds for this 143 Minimum allowed time window in micro seconds for this
|
D | sysfs-class-net-queues | 78 Indicates the current limit of bytes allowed to be queued 87 Indicates the absolute maximum limit of bytes allowed to be 96 Indicates the absolute minimum limit of bytes allowed to be
|
D | sysfs-module | 18 Description: Maximum time allowed for periodic transfers per microframe (μs) 21 USB 2.0 sets maximum allowed time for periodic transfers per
|
D | sysfs-driver-ppi | 59 This attribute shows whether it is allowed to request an 70 This attribute shows whether it is allowed to request an
|
/Documentation/devicetree/bindings/i2c/ |
D | i2c-st.txt | 18 allowed through the deglitch circuit. In units of us. 20 allowed through the deglitch circuit. In units of us.
|
/Documentation/devicetree/bindings/usb/ |
D | octeon-usb.txt | 21 - clock-frequency: speed of the USB reference clock. Allowed values are 24 - cavium,refclk-type: type of the USB reference clock. Allowed values are
|
/Documentation/devicetree/bindings/dma/ |
D | renesas,nbpfaxi.txt | 28 than using the maximum burst size allowed by the hardware's buffer size. 31 than using the maximum burst size allowed by the hardware's buffer size.
|
/Documentation/core-api/ |
D | debug-objects.rst | 74 whether the object can be initialized. Initializing is not allowed for 97 whether the object can be initialized. Initializing is not allowed for 121 whether the object can be activated. Activating is not allowed for 146 the object can be deactivated. Deactivating is not allowed for untracked 161 the object can be destroyed. Destruction is not allowed for active and 177 the object can be freed. Free is not allowed for active objects. When
|
/Documentation/arm/ |
D | kernel_mode_neon.rst | 53 implies that interruptions of a kernel mode NEON section can only be allowed if 56 * NEON/VFP code is not allowed in interrupt context; 57 * NEON/VFP code is not allowed to sleep; 82 kernel_neon_end(), i.e., that it is only allowed to issue NEON/VFP instructions
|
/Documentation/networking/devlink/ |
D | devlink-reload.rst | 54 - No reset allowed, no down time allowed, no link flap and no
|
/Documentation/power/powercap/ |
D | powercap.rst | 229 Maximum allowed power in micro watts. 232 Minimum allowed power in micro watts. 235 Maximum allowed time window in micro seconds. 238 Minimum allowed time window in micro seconds.
|
/Documentation/devicetree/bindings/serial/ |
D | efm32-uart.txt | 10 Allowed range : [0 .. 5]
|
/Documentation/livepatch/ |
D | system-state.rst | 71 - Any completely new system state modification is allowed. 73 - System state modifications with the same or higher version are allowed 79 - Non-cumulative livepatches are allowed to touch already modified
|
12345678910>>...17