Searched full:arguments (Results 1 – 25 of 404) sorted by relevance
12345678910>>...17
| /Documentation/devicetree/bindings/pinctrl/ |
| D | brcm,bcm11351-pinctrl.txt | 61 - input-schmitt-enable: No arguments. Enable schmitt-trigger mode.
62 - input-schmitt-disable: No arguments. Disable schmitt-trigger mode.
63 - bias-pull-up: No arguments. Pull up on pin.
64 - bias-pull-down: No arguments. Pull down on pin.
65 - bias-disable: No arguments. Disable pin bias.
76 - input-enable: No arguments. Enable input (does not affect
78 - input-disable: No arguments. Disable input (does not affect
91 - bias-disable: No arguments. Disable pin bias.
102 - input-enable: No arguments. Enable input (does not affect
104 - input-disable: No arguments. Disable input (does not affect
[all …]
|
| D | pinctrl-mt8183.txt | 52 "mediatek,pull-down-adv" to support arguments for those special pins.
53 Valid arguments are from 0 to 3.
56 duty cycle when asserted (high pulse width adjustment). Valid arguments
59 duty cycle when asserted (high pulse width adjustment). Valid arguments
62 When config drive-strength, it can support some arguments, such as
82 So the valid arguments of "mediatek,drive-strength-adv" are from 0 to 7.
|
| D | pinctrl-mt6797.txt | 46 Valid arguments for 'slew-rate' are '0' for no slew rate controlled and
47 '1' for slower slew rate respectively. Valid arguments for 'drive-strength'
53 duty cycle when asserted (high pulse width adjustment). Valid arguments
56 duty cycle when asserted (high pulse width adjustment). Valid arguments
|
| D | bitmain,bm1880-pinctrl.txt | 90 - bias-disable: No arguments. Disable pin bias.
91 - bias-pull-down: No arguments. The specified pins should be configured as
93 - bias-pull-up: No arguments. The specified pins should be configured as
95 - input-schmitt-enable: No arguments: Enable schmitt trigger for the specified
97 - input-schmitt-disable: No arguments: Disable schmitt trigger for the specified
|
| D | actions,s900-pinctrl.txt | 152 - bias-bus-hold: No arguments. The specified pins should retain the previous
154 - bias-high-impedance: No arguments. The specified pins should be configured
156 - bias-pull-down: No arguments. The specified pins should be configured as
158 - bias-pull-up: No arguments. The specified pins should be configured as
160 - input-schmitt-enable: No arguments: Enable schmitt trigger for the specified
162 - input-schmitt-disable: No arguments: Disable schmitt trigger for the specified
|
| D | actions,s700-pinctrl.txt | 127 - bias-pull-down: No arguments. The specified pins should be configured as
129 - bias-pull-up: No arguments. The specified pins should be configured as
131 - input-schmitt-enable: No arguments: Enable schmitt trigger for the specified
133 - input-schmitt-disable: No arguments: Disable schmitt trigger for the specified
|
| /Documentation/networking/ |
| D | radiotap-headers.txt | 31 argument bitmap extensions..." above), and the start of the arguments is moved
35 covered by the ieee80211_radiotap_header and any arguments following.
38 Requirements for arguments
41 After the fixed part of the header, the arguments follow for each argument
45 - the arguments are all stored little-endian!
52 - the arguments must be aligned to a boundary of the argument size using
70 - The arguments for a given argument index can be a compound of multiple types
|
| /Documentation/bpf/ |
| D | prog_cgroup_sockopt.rst | 16 all input arguments: ``level``, ``optname``, ``optval`` and ``optlen``.
22 sockopt and it has writable context: it can modify the supplied arguments
84 to the input arguments (``level``, ``optname``, ``optval``, ``optlen``),
86 *not* the original input ``setsockopt`` arguments. The potentially
|
| /Documentation/devicetree/bindings/usb/ |
| D | generic.txt | 5 speed. Valid arguments are "super-speed", "high-speed",
10 particular mode. Valid arguments are "host",
16 selected. Valid arguments are "utmi" and "utmi_wide".
|
| /Documentation/RCU/ |
| D | UP.rst | 25 Now, if call_rcu() were to directly invoke its arguments, then upon return
37 by having call_rcu() directly invoke its arguments only if it was called
47 its arguments would cause it to fail to make the fundamental guarantee
48 underlying RCU, namely that call_rcu() defers invoking its arguments until
91 Permitting call_rcu() to immediately invoke its arguments breaks RCU,
|
| /Documentation/arm64/ |
| D | tagged-address-abi.rst | 63 Arguments ``arg3``, ``arg4``, and ``arg5`` must be 0.
68 Arguments ``arg2``, ``arg3``, ``arg4``, and ``arg5`` must be 0.
102 indirectly as arguments to be accessed by the kernel.
105 indirectly as arguments to be accessed by the kernel.
|
| /Documentation/process/ |
| D | adding-syscalls.rst | 68 For simpler system calls that only take a couple of arguments, the preferred
79 For more sophisticated system calls that involve a larger number of arguments,
80 it's preferred to encapsulate the majority of the arguments into a structure
171 arguments (i.e. parameter 1, 3, 5), to allow use of contiguous pairs of 32-bit
172 registers. (This concern does not apply if the arguments are part of a
202 number of arguments to the system call, and the macro takes the system call name
203 followed by the (type, name) pairs for the parameters as arguments. Using
291 system call's arguments has a type that is explicitly 64-bit even on a 32-bit
297 does **not** need a compatibility layer; for example, :manpage:`splice(2)`'s arguments of
320 parse the arguments from a 32-bit invocation.
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | statistics.rst | 62 The number of optional arguments
65 The following optional arguments are supported:
94 If we omit the number of optional arguments, program id must not
96 optional arguments.
|
| D | dm-integrity.rst | 54 Target arguments:
87 5. the number of additional arguments
89 Additional arguments:
183 tables with suspend and resume). The other arguments should not be changed
193 area is specified in the target arguments
|
| D | dm-clone.rst | 150 #feature args Number of feature arguments passed
153 #core args An even number of arguments corresponding to key/value pairs
159 Optional feature arguments are:
167 Optional core arguments are:
197 #feature args Number of feature arguments to follow
198 feature args Feature arguments, e.g. `no_hydration`
199 #core args Even number of core arguments to follow
|
| /Documentation/ABI/testing/ |
| D | debugfs-olpc | 12 are optional (hex) arguments.
|
| /Documentation/trace/ |
| D | kprobetrace.rst | 45 FETCHARGS : Arguments. Each probe can have up to 128 args.
71 respectively. 'x' prefix implies it is unsigned. Traced arguments are shown
122 probe and gives you what arguments will be shown in trace buffer. If an event
173 1st to 4th arguments as "myprobe" event. Note, which register/stack entry is
177 As this example shows, users can choose more familiar names for each arguments.
208 You can see that the event has 4 arguments as in the expressions you specified.
|
| /Documentation/devicetree/bindings/mmc/ |
| D | fsl-imx-mmc.txt | 9 - dmas: One DMA phandle with arguments as defined by the devicetree bindings
|
| /Documentation/virt/kvm/ |
| D | hypercalls.txt | 8 Up to four arguments may be passed in rbx, rcx, rdx, and rsi respectively.
33 number in $2 (v0). Up to four arguments may be placed in $4-$7 (a0-a3) and
139 bitmap contained in the first two arguments (a0 and a1). Bit 0 of
|
| /Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 97 particular number of arguments.
122 The "warning-if" function takes two arguments. If the condition part is "y",
154 while whitespaces in the other arguments are kept. You need to use a kind of
191 accepts only one. To pass commas in arguments, you can use the following trick::
|
| /Documentation/devicetree/bindings/mips/pic32/ |
| D | microchip,pic32mzda.txt | 29 bootloader must pass the following arguments to the kernel:
|
| /Documentation/userspace-api/ |
| D | seccomp_filter.rst | 20 number and the system call arguments. This allows for expressive
28 call arguments directly.
54 reflecting the system call number, arguments, and other
263 arguments to the syscall, but does not contain pointers to memory. The task's
266 above in this document: all arguments being read from the tracee's memory
268 This allows for an atomic decision on syscall arguments.
|
| /Documentation/sphinx/ |
| D | kernel_include.py | 63 os.path.expandvars(self.arguments[0]))
71 self.arguments[0] = path
89 path = directives.path(self.arguments[0])
180 [self.options.pop('code')], # arguments
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | reboot-mode.txt | 3 This driver get reboot mode arguments and call the write
|
| /Documentation/features/ |
| D | list-arch.sh | 5 # (If no arguments are given then it will print the host architecture's status.)
|
12345678910>>...17