Searched refs:follows (Results 1 – 25 of 443) sorted by relevance
12345678910>>...18
| /Linux-v4.19/drivers/staging/greybus/ |
| D | Kconfig | 34 Select this option if you have a device that follows the
43 Select this option if you have a device that follows the
53 Select this option if you have a device that follows the
63 Select this option if you have a device that follows the
73 Select this option if you have a device that follows the
83 Select this option if you have a device that follows the
92 Select this option if you have a device that follows the
101 Select this option if you have a device that follows the
111 Select this option if you have a device that follows the
120 Select this option if you have a device that follows the
[all …]
|
| /Linux-v4.19/Documentation/devicetree/bindings/display/panel/ |
| D | panel-lvds.txt | 47 LVDS data mappings are defined as follows.
50 [VESA] specifications. Data are transferred as follows on 3 LVDS lanes.
61 specifications. Data are transferred as follows on 4 LVDS lanes.
73 Data are transferred as follows on 4 LVDS lanes.
84 Control signals are mapped as follows.
|
| /Linux-v4.19/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-v4.19/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:
|
| D | gpio-axp209.txt | 3 This driver follows the usual GPIO bindings found in
6 This driver follows the usual pinctrl bindings found in
|
| /Linux-v4.19/Documentation/RCU/ |
| D | lockdep-splat.txt | 63 Line 2776 of block/cfq-iosched.c in v3.0-rc5 is as follows:
73 which would permit us to invoke rcu_dereference_protected as follows:
88 add rcu_read_lock() and rcu_read_unlock() as follows:
105 by rcu_access_pointer() as follows:
|
| D | rcuref.txt | 45 in this scenario as follows:
80 as follows:
118 delete(), so that el_free() can be subsumed into delete as follows:
|
| D | listRCU.txt | 27 implementation of audit_filter_task() might be as follows:
51 This means that RCU can be easily applied to the read side, as follows:
76 lock might be used as follows for deletion and insertion:
162 follows (presumably, the field_count is only permitted to decrease,
190 RCU ("read-copy update") its name. The RCU code is as follows:
240 as follows:
271 flag under the spinlock as follows:
|
| D | rcubarrier.txt | 35 context might then be as follows:
41 IRQ context. The function p_callback() might be defined as follows:
80 Pseudo-code using rcu_barrier() is as follows:
100 as follows:
204 The original code for rcu_barrier() was as follows:
230 to post an RCU callback, as follows:
252 reaches zero, as follows:
|
| /Linux-v4.19/Documentation/pcmcia/ |
| D | locking.txt | 60 The "main" struct pcmcia_socket is protected as follows (read-only fields
99 The "main" struct pcmcia_device is protected as follows (read-only fields
|
| /Linux-v4.19/Documentation/filesystems/ext4/ondisk/ |
| D | blocks.rst | 15 For 32-bit filesystems, limits are as follows:
77 For 64-bit filesystems, limits are as follows:
|
| D | special_inodes.rst | 6 ext4 reserves some inode for special features, as follows:
|
| /Linux-v4.19/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 specicfication as described in the document at https://refspecs.linuxb…
|
| /Linux-v4.19/Documentation/sound/soc/ |
| 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-v4.19/Documentation/devicetree/bindings/interrupt-controller/ |
| D | img,meta-intc.txt | 30 Interrupt specifiers consists of 2 cells encoded as follows:
35 encoded as follows:
|
| 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):
|
| D | open-pic.txt | 40 follows:
44 - <2nd-cell>: The level-sense information, encoded as follows:
|
| D | faraday,ftintc010.txt | 14 IRQs. The bindings follows the standard binding for controllers
|
| /Linux-v4.19/drivers/usb/misc/ |
| D | ftdi-elan.c | 112 int follows; member
375 command->follows = 0; in ftdi_elan_flush_targets()
397 command->follows = 0; in ftdi_elan_flush_targets()
433 command->follows = 0; in ftdi_elan_cancel_targets()
740 int F = command->follows; in fill_buffer_with_all_queued_commands()
765 total_size += 5 + command->follows; in ftdi_elan_total_command_size()
1223 command->follows = 4; in ftdi_elan_write_reg()
1255 command->follows = 4; in ftdi_elan_write_config()
1287 command->follows = 4; in ftdi_elan_write_pcimem()
1333 command->follows = 0; in ftdi_elan_read_reg()
[all …]
|
| /Linux-v4.19/Documentation/devicetree/bindings/clock/ti/ |
| D | mux.txt | 15 results in programming the register as follows:
24 "index-starts-at-one" modified the scheme as follows:
|
| /Linux-v4.19/Documentation/driver-api/gpio/ |
| D | board.rst | 140 A lookup table can then be defined as follows, with an empty entry defining its
158 And the table can be added by the board code as follows::
162 The driver controlling "foo.0" will then be able to obtain its GPIOs as follows::
190 And the table can be added to the board code as follows::
|
| /Linux-v4.19/Documentation/devicetree/bindings/mtd/ |
| D | ibm,ndfc.txt | 12 - partition(s) - follows the OF MTD standard for partitions
|
| /Linux-v4.19/Documentation/ |
| D | vfio-mediated-device.txt | 137 The structures in the mdev_parent_ops structure are as follows:
143 The functions in the mdev_parent_ops structure are as follows:
153 The callbacks in the mdev_parent_ops structure are as follows:
232 follows::
363 as follows::
382 In the Linux guest VM, dmesg output for the device is as follows:
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-devices-sun | 7 Configuration and Power Interface Specification as follows:
|
| /Linux-v4.19/Documentation/devicetree/bindings/crypto/ |
| D | fsl-sec2.txt | 18 EU_SEL0 field documentation, i.e. as follows:
36 field documentation, i.e. as follows:
|
12345678910>>...18
