| /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/userspace-api/ |
| H A D | ntsync.rst | 104 The ioctls on the device file are as follows:
109 :c:type:`ntsync_sem_args`, which is used as follows:
124 :c:type:`ntsync_mutex_args`, which is used as follows:
140 :c:type:`ntsync_event_args`, which is used as follows:
153 The ioctls on the individual objects are as follows:
171 :c:type:`ntsync_mutex_args`, which is used as follows:
219 struct :c:type:`ntsync_sem_args`, which is used as follows:
231 :c:type:`ntsync_mutex_args`, which is used as follows:
248 :c:type:`ntsync_event_args`, which is used as follows:
272 used as follows:
|
| 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/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 | 62 The packing of the data follows the MIPI CSI-2 specification and the padding of
106 The packing of the data follows the MIPI CSI-2 specification and the padding of
152 The packing of the data follows the MIPI CSI-2 specification and the padding of
195 The packing of the data follows the MIPI CSI-2 specification and the padding of
244 The packing of the data follows the MIPI CSI-2 specification and the padding of
297 The packing of the data follows the MIPI CSI-2 specification and the padding of
|
| H A D | metafmt-uvc-msxu-1-5.rst | 19 The metadata format follows the specification from Microsoft(R) [1].
|
| /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/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/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/hwmon/ |
| H A D | hwmon-kernel-api.rst | 110 The hwmon_chip_info structure looks as follows::
150 defined as follows::
228 The remaining declarations are as follows.
242 is defined in include/linux/hwmon.h. Definition prefixes are as follows.
261 and return values for those functions are as follows::
372 variable, which is defined as follows::
|
| /linux/Documentation/networking/devlink/ |
| H A D | octeontx2.rst | 53 since the counters are scarce and driver follows a best effort approach.
56 Sample command to read hit counters for default rule from debugfs is as 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/virt/kvm/loongarch/ |
| H A D | hypercalls.rst | 40 The parameters are as follows:
66 The template for each hypercall is as follows:
|
| /linux/Documentation/leds/ |
| H A D | leds-blinkm.rst | 21 The registration follows the scheme::
43 The registration follows the scheme::
|
| /linux/drivers/staging/media/meson/vdec/ |
| H A D | TODO | 5 stack that follows the latest version of the specification, especially
|
| /linux/Documentation/iio/ |
| H A D | iio_devbuf.rst | 99 data is stored in two 8-bit registers is as follows::
131 If all channels are enabled, the data will be aligned in the buffer as follows::
139 buffer as follows::
|
| /linux/Documentation/kbuild/ |
| H A 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
|