| /linux/drivers/staging/greybus/ |
| H A 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/Documentation/devicetree/bindings/scsi/ |
| H A 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/Documentation/RCU/ |
| H A 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::
|
| H A D | rcuref.rst | 52 in this scenario as follows:
89 as follows:
140 delete(), so that el_free() can be subsumed into delete as follows::
|
| H A D | rcubarrier.rst | 13 as follows::
19 IRQ context. The function p_callback() might be defined as follows::
61 Pseudo-code using rcu_barrier() is as follows:
83 in its exit function as follows::
194 The original code for rcu_barrier() was roughly as follows::
233 to post an RCU callback, as follows::
255 reaches zero, as follows::
|
| /linux/Documentation/devicetree/bindings/gpio/ |
| H A 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/Documentation/userspace-api/media/v4l/ |
| H A D | metafmt-generic.rst | 61 The packing of the data follows the MIPI CSI-2 specification and the padding of
105 The packing of the data follows the MIPI CSI-2 specification and the padding of
151 The packing of the data follows the MIPI CSI-2 specification and the padding of
194 The packing of the data follows the MIPI CSI-2 specification and the padding of
243 The packing of the data follows the MIPI CSI-2 specification and the padding of
296 The packing of the data follows the MIPI CSI-2 specification and the padding of
|
| /linux/Documentation/pcmcia/ |
| H A D | locking.rst | 69 The "main" struct pcmcia_socket is protected as follows (read-only fields
112 The "main" struct pcmcia_device is protected as follows (read-only fields
|
| /linux/tools/perf/Documentation/ |
| H A 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/Documentation/bpf/ |
| H A 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::
|
| H A D | prog_flow_dissector.rst | 98 The takeaway here is as follows: BPF flow dissector program can be called with
108 ``flow_keys->flags`` might contain optional input flags that work as follows:
129 The reference implementation is organized as follows:
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | blocks.rst | 17 For 32-bit filesystems, limits are as follows:
79 For 64-bit filesystems, limits are as follows:
|
| /linux/tools/memory-model/Documentation/ |
| H A 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/Documentation/sound/soc/ |
| H A D | pops-clicks.rst | 23 shutdown and follows some basic rules:-
38 ADC until all the pops have occurred. This follows similar power rules to
|
| /linux/Documentation/userspace-api/ |
| H A 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/Documentation/devicetree/bindings/clock/ti/ |
| H A D | mux.txt | 13 results in programming the register as follows:
22 "index-starts-at-one" modified the scheme as follows:
|
| /linux/Documentation/devicetree/bindings/power/reset/ |
| H A D | mt6323-poweroff.txt | 7 - compatible: Should be one of follows
|
| /linux/samples/vfio-mdev/ |
| H A D | README.rst | 56 as follows::
75 In the Linux guest VM, dmesg output for the device is as follows:
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | img,pdc-intc.txt | 32 Interrupt specifiers consists of 2 cells encoded as follows:
39 flags as follows (only 4 valid for peripheral interrupts):
|
| H A D | open-pic.txt | 40 follows:
44 - <2nd-cell>: The level-sense information, encoded as follows:
|
| /linux/Documentation/driver-api/gpio/ |
| H A D | board.rst | 136 A lookup table can then be defined as follows, with an empty entry defining its
154 And the table can be added by the board code as follows::
158 The driver controlling "foo.0" will then be able to obtain its GPIOs as follows::
186 And the table can be added to the board code as follows::
|
| /linux/drivers/staging/media/meson/vdec/ |
| H A D | TODO | 5 stack that follows the latest version of the specification, especially
|
| /linux/Documentation/devicetree/bindings/media/i2c/ |
| H A D | tvp5150.txt | 20 are numbered as follows
30 as follows
|
| /linux/Documentation/devicetree/bindings/crypto/ |
| H A D | fsl-sec2.txt | 18 EU_SEL0 field documentation, i.e. as follows:
36 field documentation, i.e. as follows:
|
| /linux/Documentation/devicetree/bindings/mtd/ |
| H A D | ibm,ndfc.txt | 12 - partition(s) - follows the OF MTD standard for partitions
|