| /Documentation/networking/ |
| D | radiotap-headers.rst | 36 argument bitmap extensions..." above), and the start of the arguments is moved
40 covered by the ieee80211_radiotap_header and any arguments following.
43 Requirements for arguments
46 After the fixed part of the header, the arguments follow for each argument
50 - the arguments are all stored little-endian!
57 - the arguments must be aligned to a boundary of the argument size using
75 - The arguments for a given argument index can be a compound of multiple types
|
| /Documentation/firmware-guide/acpi/ |
| D | chromeos-acpi-device.rst | 52 Arguments:
83 Arguments:
99 Arguments:
113 Arguments:
126 Arguments:
188 Arguments:
261 Arguments:
297 Arguments:
311 Arguments:
326 Arguments:
[all …]
|
| /Documentation/filesystems/ |
| D | coda.rst | 478 Arguments
506 Arguments
554 Arguments
588 The vattr structure included in the input arguments is superfluous and
599 Arguments
631 Arguments
665 Arguments
728 Arguments
774 Arguments
807 Arguments
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | delay.rst | 8 Arguments::
13 Table line has to either have 3, 6 or 9 arguments:
21 9: same as 6 arguments plus define flush_offset and flush_delay explicitely
|
| 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.
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | mediatek,mt8365-pinctrl.yaml | 82 resistance. Valid arguments are described as below:
96 different resistance. Valid arguments are described as below:
135 Valid arguments are described as below:
144 So the valid arguments are from 0 to 7.
153 configure those special pins. Valid arguments are described as
167 configure those special pins. Valid arguments are described as
179 cycle when asserted (high pulse width adjustment). Valid arguments
186 when asserted (high pulse width adjustment). Valid arguments are
|
| 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 | mediatek,mt8183-pinctrl.yaml | 131 Valid arguments are described as below:
140 So the valid arguments are from 0 to 7.
147 configure those special pins. Valid arguments are described as
159 configure those special pins. Valid arguments are described as
171 cycle when asserted (high pulse width adjustment). Valid arguments
178 when asserted (high pulse width adjustment). Valid arguments are
|
| 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
|
| D | mediatek,mt65xx-pinctrl.yaml | 103 valid arguments.
121 Can support some arguments, such as MTK_DRIVE_4mA, MTK_DRIVE_6mA,
122 etc. See dt-bindings/pinctrl/mt65xx.h for valid arguments.
|
| /Documentation/sphinx/ |
| D | kernel_feat.py | 90 os.path.join(srctree, 'Documentation', self.arguments[0]),
93 if len(self.arguments) > 1:
94 args.extend(['--arch', self.arguments[1]])
112 nodeList = self.nestedParse(out_lines, self.arguments[0])
|
| /Documentation/trace/ |
| D | fprobetrace.rst | 43 FETCHARGS : Arguments. Each probe can have up to 128 args.
64 the stack. But this only support the arguments via registers.
73 Function arguments at exit
75 Function arguments can be accessed at exit probe using $arg<N> fetcharg. This
81 BTF arguments
113 If user unsures the name of arguments, ``$arg*`` will be helpful. The ``$arg*``
114 is expanded to all function arguments of the function or the tracepoint. ::
146 For these BTF arguments and fields, ``:string`` and ``:ustring`` change the
165 and exit, with BTF arguments.
186 You can see all function arguments and return values are recorded as signed int.
[all …]
|
| D | kprobetrace.rst | 47 FETCHARGS : Arguments. Each probe can have up to 128 args.
67 the stack. But this only support the arguments via registers.
74 Function arguments at kretprobe
76 Function arguments can be accessed at kretprobe using $arg<N> fetcharg. This
89 respectively. 'x' prefix implies it is unsigned. Traced arguments are shown
101 Char type can be used to show the character value of traced arguments.
153 probe and gives you what arguments will be shown in trace buffer. If an event
204 1st to 4th arguments as "myprobe" event. Note, which register/stack entry is
208 As this example shows, users can choose more familiar names for each arguments.
239 You can see that the event has 4 arguments as in the expressions you specified.
|
| /Documentation/arch/arm64/ |
| D | tagged-address-abi.rst | 58 - The ``range.start``, ``start`` and ``dst`` arguments to the
80 Arguments ``arg3``, ``arg4``, and ``arg5`` must be 0.
85 Arguments ``arg2``, ``arg3``, ``arg4``, and ``arg5`` must be 0.
119 indirectly as arguments to be accessed by the kernel.
122 indirectly as arguments to be accessed by the kernel.
|
| /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
100 Permitting call_rcu() to immediately invoke its arguments breaks RCU,
|
| /Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_audio.rst | 469 Arguments subsection
520 Arguments subsection
571 Arguments subsection
624 Arguments subsection
677 Arguments subsection
739 Arguments subsection
813 Arguments subsection
884 Arguments subsection
958 Arguments subsection
1020 Arguments subsection
[all …]
|
| D | legacy_dvb_video.rst | 820 Arguments subsection
894 Arguments subsection
949 Arguments subsection
1009 Arguments subsection
1064 Arguments subsection
1133 Arguments subsection
1203 Arguments subsection
1262 Arguments subsection
1351 Arguments subsection
1410 Arguments subsection
[all …]
|
| /Documentation/virt/kvm/arm/ |
| D | mmio-guard.rst | 43 Arguments: r1-r3 Reserved / Must be zero
55 Arguments: none
64 Arguments: (uint64) The base of the PG-sized IPA range
85 Arguments: (uint64) The base of the PG-sized IPA range
|
| /Documentation/userspace-api/netlink/ |
| D | intro-specs.rst | 19 a handul of arguments, the most important ones are:
44 The input arguments are parsed as JSON, while the output is only
79 but it takes a few arguments so calling it directly for each file
120 // 4. Free the request arguments
|
| /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
|
| D | classic_vs_extended.rst | 16 pointer. Since 64-bit CPUs are passing arguments to functions via registers
19 function. Natively, x86_64 passes first 6 arguments in registers, aarch64/
20 sparcv9/mips64 have 7 - 8 registers for arguments; x86_64 has 6 callee saved
65 place function arguments into R1 to R5 registers to satisfy calling
69 doesn't need to emit extra moves. Function arguments will be in the correct
109 can call kernel functions with up to 5 arguments. Calls with 6 or more arguments
185 arg2, u64 arg3, u64 arg4, u64 arg5); will receive arguments in proper
|
| /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/features/ |
| D | list-arch.sh | 6 # (If no arguments are given then it will print the host architecture's status.)
|
| /Documentation/ABI/testing/ |
| D | debugfs-msi-wmi-platform | 8 To start the execution, write a buffer containing the method arguments
|