Searched full:follows (Results 1 – 25 of 1450) sorted by relevance
12345678910>>...58
| /Linux-v6.1/drivers/staging/greybus/ |
| D | Kconfig | 8 Select this option if you have a device that follows the
29 Select this option if you have a device that follows the
39 Select this option if you have a device that follows the
49 Select this option if you have a device that follows the
59 Select this option if you have a device that follows the
69 Select this option if you have a device that follows the
78 Select this option if you have a device that follows the
87 Select this option if you have a device that follows the
97 Select this option if you have a device that follows the
106 Select this option if you have a device that follows the
[all …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/display/ |
| D | lvds.yaml | 38 LVDS data mappings are defined as follows.
41 [VESA] specifications. Data are transferred as follows on 3 LVDS lanes.
52 specifications. Data are transferred as follows on 4 LVDS lanes.
64 Data are transferred as follows on 4 LVDS lanes.
75 Control signals are mapped as follows.
|
| /Linux-v6.1/arch/x86/include/asm/ |
| D | sigframe.h | 38 /* fp state follows here */
53 /* fp state follows here */
63 /* fp state follows here */
81 /* fp state follows here */
|
| /Linux-v6.1/Documentation/devicetree/bindings/input/ |
| D | iqs626a.yaml | 42 Specifies the power mode during suspend as follows:
64 updated during ultra-low-power mode as follows:
88 represents touch state as follows:
104 long-term average) of an associated channel as follows:
199 Specifies how inactive CRX pins are to be terminated as follows:
226 Specifies the channel's ATI mode as follows:
269 sensing as follows:
281 Specifies the channel's sensing frequency as follows (parenthesized
364 Specifies the capacitance to be added to the channel as follows:
377 Specifies the channel's sensing mode as follows:
[all …]
|
| D | iqs269a.yaml | 47 Specifies the power mode during suspend as follows:
172 Specifies the inductive sensing excitation frequency as follows (paren-
189 long-term average) of an associated channel as follows:
274 Specifies the capacitance to be added to the channel as follows:
291 sensing as follows:
302 Specifies the channel's sensing mode as follows:
314 Specifies the channel's sensing frequency as follows (parenthesized
330 Specifies the channel's ATI mode as follows:
|
| D | azoteq,iqs7222.yaml | 45 reported as follows:
56 generated as follows:
225 Specifies the cycle's sensing mode as follows:
296 follows:
343 capacitive sensing as follows:
367 Specifies the channel's ATI mode as follows:
433 Specifies one or more GPIO mapped to the event as follows:
614 Specifies one or more GPIO mapped to the event as follows:
636 Represents a GPIO mapped to one or more events as follows:
|
| /Linux-v6.1/drivers/gpu/drm/gma500/ |
| D | oaktrail.h | 77 u16 Panel_Backlight_Inverter_Descriptor;/* 16 bits, as follows */
81 /*16 bits, Defined as follows: */
106 u16 Panel_Backlight_Inverter_Descriptor;/*16 bits, as follows*/
111 /*16 bits, Defined as follows: */
147 union { /*8 bits,Defined as follows: */
164 union { /*8 bits,Defined as follows: */
|
| /Linux-v6.1/tools/perf/Documentation/ |
| D | jitdump-specification.txt | 48 The flags currently defined are as follows:
53 …ollowed by records. Each record starts with a fixed size header describing the record that follows.
55 The record header is specified in order as follows:
126 The debug_entry describes the source line information. It is defined as follows in order:
164 The EH Frame header follows the Linux Standard Base (LSB) specification as described in the documen…
167 The EH Frame follows the LSB specification as described in the document at https://refspecs.linuxba…
|
| /Linux-v6.1/tools/memory-model/Documentation/ |
| D | control-dependencies.txt | 23 as follows:
50 the original example by eliminating the "if" statement as follows:
60 identical stores on both branches of the "if" statement as follows:
73 Unfortunately, current compilers will transform this as follows at high
146 make sure that MAX is greater than one, perhaps as follows:
171 always true, the compiler can transform this example as follows, again
|
| /Linux-v6.1/Documentation/devicetree/bindings/scsi/ |
| D | hisilicon-sas.txt | 6 - compatible : value should be as follows:
22 sources; the interrupts are ordered in 3 groups, as follows:
35 Fatal interrupts : the fatal interrupts are ordered as follows:
39 the interrupts are ordered in 3 groups, as follows:
|
| /Linux-v6.1/Documentation/RCU/ |
| D | rcubarrier.rst | 38 context might then be as follows::
44 IRQ context. The function p_callback() might be defined as follows::
85 Pseudo-code using rcu_barrier() is as follows:
104 as follows::
214 The original code for rcu_barrier() was as follows::
240 to post an RCU callback, as follows::
262 reaches zero, as follows::
|
| D | lockdep-splat.rst | 68 Line 2776 of block/cfq-iosched.c in v3.0-rc5 is as follows::
78 which would permit us to invoke rcu_dereference_protected as follows::
93 add rcu_read_lock() and rcu_read_unlock() as follows::
110 by rcu_access_pointer() as follows::
|
| D | listRCU.rst | 78 implementation of ``audit_filter_task()`` might be as follows::
102 This means that RCU can be easily applied to the read side, as follows::
127 might be used as follows for deletion and insertion::
212 if it did, the reader-writer-locked code to do so might look as follows
241 RCU (*read-copy update*) its name. The RCU code is as follows::
305 audit_entry structure, and modify ``audit_filter_task()`` as follows::
336 spinlock as follows::
|
| /Linux-v6.1/include/linux/sunrpc/ |
| D | rpc_rdma.h | 135 * Pointer to the XDR position that follows the encoded RDMA segment
154 * Pointer to the XDR position that follows the encoded Read segment
172 * Pointer to the XDR item that follows the RDMA segment
191 * Pointer to the XDR item that follows the Read segment
|
| /Linux-v6.1/arch/powerpc/kernel/ptrace/ |
| D | ptrace-tm.c | 80 * The userspace interface buffer layout is as follows.
128 * The userspace interface buffer layout is as follows.
222 * The userspace interface buffer layout is as follows.
266 * FPR registers. The userspace interface buffer layout is as follows.
334 * layout is as follows.
385 * layout is as follows.
463 * The userspace interface buffer layout is as follows.
506 * FPR registers. The userspace interface buffer layout is as follows.
566 * The userspace interface buffer layout is as follows.
608 * The userspace interface buffer layout is as follows.
|
| /Linux-v6.1/Documentation/bpf/ |
| D | s390.rst | 36 Once on Debian, the build prerequisites can be installed as follows::
62 Latest Clang targeting BPF can be installed as follows::
130 The virtual machine can be started as follows::
153 need to be mounted as follows::
|
| /Linux-v6.1/Documentation/userspace-api/ |
| D | vduse.rst | 23 VDUSE devices are created as follows:
36 VDUSE devices are destroyed as follows:
109 module as follows:
155 able to start the dataplane processing as follows:
|
| /Linux-v6.1/drivers/clk/sunxi/ |
| D | clk-sun9i-core.c | 19 * PLL4 rate is calculated as follows
95 * GT rate is calculated as follows
150 * AHB rate is calculated as follows
230 * APB1 rate is calculated as follows
|
| /Linux-v6.1/Documentation/hwmon/ |
| D | hwmon-kernel-api.rst | 132 The hwmon_chip_info structure looks as follows::
172 defined as follows::
249 The remaining declarations are as follows.
263 is defined in include/linux/hwmon.h. Definition prefixes are as follows.
282 and return values for those functions are as follows::
393 variable, which is defined as follows::
|
| /Linux-v6.1/Documentation/devicetree/bindings/gpio/ |
| D | sodaville.txt | 13 The interrupt specifier consists of two cells encoded as follows:
15 - <2nd cell>: The level-sense information, encoded as follows:
|
| /Linux-v6.1/tools/lib/subcmd/ |
| D | run-command.h | 25 * - Specify -1 to have a pipe allocated as follows:
32 * - Specify > 0 to set a channel to a particular FD as follows:
|
| /Linux-v6.1/Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 14 can write a makefile like follows::
24 and handles as if the source file were input like follows::
156 to make "info" function print " hello", you can write like follows::
241 Instead, you can do like follows so that any function call is statically
|
| /Linux-v6.1/Documentation/trace/ |
| D | user_events.rst | 64 The command string format is as follows::
128 A byte-wise index check is performed as follows::
142 A long-wise index check is performed as follows::
166 the user_events_status file directly via a terminal. The output is as follows::
|
| /Linux-v6.1/arch/powerpc/include/asm/ |
| D | user.h | 14 * are as follows:
22 * data: The data segment follows next. We use current->end_text to
|
| /Linux-v6.1/Documentation/driver-api/gpio/ |
| D | board.rst | 142 A lookup table can then be defined as follows, with an empty entry defining its
160 And the table can be added by the board code as follows::
164 The driver controlling "foo.0" will then be able to obtain its GPIOs as follows::
192 And the table can be added to the board code as follows::
|
12345678910>>...58
