| /linux/drivers/staging/greybus/ |
| 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/display/panel/ |
| A D | lvds.yaml | 49 LVDS data mappings are defined as follows.
52 [VESA] specifications. Data are transferred as follows on 3 LVDS lanes.
63 specifications. Data are transferred as follows on 4 LVDS lanes.
75 Data are transferred as follows on 4 LVDS lanes.
86 Control signals are mapped as follows.
|
| /linux/Documentation/devicetree/bindings/soc/bcm/ |
| A D | brcm,bcm2835-pm.txt | 17 - #reset-cells: Should be 1. This property follows the reset controller
19 - #power-domain-cells: Should be 1. This property follows the power domain
26 system power. This node follows the power controller bindings[3].
|
| /linux/Documentation/devicetree/bindings/input/ |
| 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:
565 Specifies the trackpad's ATI mode as follows:
604 sensing as follows:
[all …]
|
| A 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:
|
| /linux/Documentation/devicetree/bindings/scsi/ |
| 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/ |
| 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::
|
| A 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::
|
| 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::
|
| A 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/Documentation/devicetree/bindings/gpio/ |
| 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/drivers/usb/misc/ |
| A D | ftdi-elan.c | 112 int follows; member
376 command->follows = 0; in ftdi_elan_flush_targets()
398 command->follows = 0; in ftdi_elan_flush_targets()
434 command->follows = 0; in ftdi_elan_cancel_targets()
1199 command->follows = 4; in ftdi_elan_write_reg()
1231 command->follows = 4; in ftdi_elan_write_config()
1263 command->follows = 4; in ftdi_elan_write_pcimem()
1309 command->follows = 0; in ftdi_elan_read_reg()
1353 command->follows = 0; in ftdi_elan_read_config()
1397 command->follows = 0; in ftdi_elan_read_pcimem()
[all …]
|
| /linux/tools/perf/Documentation/ |
| 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/ |
| 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/ |
| 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::
|
| 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/ |
| 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/ |
| 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/ |
| 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/ |
| 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/ |
| A D | mux.txt | 15 results in programming the register as follows:
24 "index-starts-at-one" modified the scheme as follows:
|
| /linux/Documentation/hwmon/ |
| A D | hwmon-kernel-api.rst | 116 The hwmon_chip_info structure looks as follows::
156 defined as follows::
233 The remaining declarations are as follows.
247 is defined in include/linux/hwmon.h. Definition prefixes are as follows.
266 and return values for those functions are as follows::
377 variable, which is defined as follows::
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| 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):
|
| A D | open-pic.txt | 40 follows:
44 - <2nd-cell>: The level-sense information, encoded as follows:
|
| /linux/Documentation/devicetree/bindings/power/reset/ |
| A D | mt6323-poweroff.txt | 7 - compatible: Should be one of follows
|