| /linux-6.15/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-6.15/Documentation/devicetree/bindings/display/ |
| H A D | lvds-data-mapping.yaml | 43 LVDS data mappings are defined as follows.
46 [VESA] specifications. Data are transferred as follows on 3 LVDS lanes.
57 specifications. Data are transferred as follows on 4 LVDS lanes.
69 are transferred as follows on 5 LVDS lanes.
82 Data are transferred as follows on 4 LVDS lanes.
94 transferred as follows on 5 LVDS lanes.
106 Control signals are mapped as follows.
|
| /linux-6.15/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-6.15/Documentation/devicetree/bindings/input/ |
| H A 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:
377 Specifies the channel's sensing mode as follows:
561 Specifies the trackpad's ATI mode as follows:
590 sensing as follows:
[all …]
|
| H A D | iqs269a.yaml | 53 Specifies the power mode during suspend as follows:
178 Specifies the inductive sensing excitation frequency as follows (paren-
195 long-term average) of an associated channel as follows:
347 Specifies the capacitance to be added to the channel as follows:
364 sensing as follows:
375 Specifies the channel's sensing mode as follows:
387 Specifies the channel's sensing frequency as follows (parenthesized
403 Specifies the channel's ATI mode as follows:
|
| /linux-6.15/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-6.15/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-6.15/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-6.15/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-6.15/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-6.15/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-6.15/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-6.15/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-6.15/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-6.15/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-6.15/tools/testing/selftests/devices/probe/boards/ |
| H A D | google,spherion.yaml | 29 # follows the format \d(.\d)* and denotes the port in the hub at each level in
30 # the USB topology. For PCI devices it follows the format \d.\d(/\d.\d)*
|
| /linux-6.15/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-6.15/drivers/staging/media/meson/vdec/ |
| H A D | TODO | 5 stack that follows the latest version of the specification, especially
|
| /linux-6.15/Documentation/hwmon/ |
| H A D | hwmon-kernel-api.rst | 100 The hwmon_chip_info structure looks as follows::
140 defined as follows::
217 The remaining declarations are as follows.
231 is defined in include/linux/hwmon.h. Definition prefixes are as follows.
250 and return values for those functions are as follows::
359 variable, which is defined as follows::
|
| /linux-6.15/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-6.15/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):
|