Searched refs:follows (Results 1 – 25 of 465) sorted by relevance
12345678910>>...19
| /Linux-v5.4/drivers/staging/greybus/ |
| D | Kconfig | 8 Select this option if you have a device that follows the
17 Select this option if you have a device that follows the
27 Select this option if you have a device that follows the
37 Select this option if you have a device that follows the
47 Select this option if you have a device that follows the
57 Select this option if you have a device that follows the
66 Select this option if you have a device that follows the
75 Select this option if you have a device that follows the
85 Select this option if you have a device that follows the
94 Select this option if you have a device that follows the
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/soc/bcm/ |
| 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-v5.4/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-v5.4/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-v5.4/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 | listRCU.rst | 29 implementation of audit_filter_task() might be as follows::
53 This means that RCU can be easily applied to the read side, as follows::
78 lock might be used as follows for deletion and insertion::
164 follows (presumably, the field_count is only permitted to decrease,
192 RCU ("read-copy update") its name. The RCU code is as follows::
245 as follows::
276 flag under the spinlock as follows::
|
| D | rcuref.txt | 47 in this scenario as follows:
83 as follows:
133 delete(), so that el_free() can be subsumed into delete 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:
99 as follows:
203 The original code for rcu_barrier() was as follows:
229 to post an RCU callback, as follows:
251 reaches zero, as follows:
|
| /Linux-v5.4/Documentation/pcmcia/ |
| 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-v5.4/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()
1197 command->follows = 4; in ftdi_elan_write_reg()
1229 command->follows = 4; in ftdi_elan_write_config()
1261 command->follows = 4; in ftdi_elan_write_pcimem()
1307 command->follows = 0; in ftdi_elan_read_reg()
[all …]
|
| /Linux-v5.4/Documentation/filesystems/ext4/ |
| D | blocks.rst | 17 For 32-bit filesystems, limits are as follows:
79 For 64-bit filesystems, limits are as follows:
|
| D | special_inodes.rst | 6 ext4 reserves some inode for special features, as follows:
|
| /Linux-v5.4/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-v5.4/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):
|
| /Linux-v5.4/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-v5.4/Documentation/devicetree/bindings/power/reset/ |
| D | mt6323-poweroff.txt | 7 - compatible: Should be one of follows
|
| /Linux-v5.4/Documentation/bpf/ |
| 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-v5.4/Documentation/devicetree/bindings/sound/ |
| D | everest,es8316.txt | 13 - clock-names : should include as follows:
|
| /Linux-v5.4/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-v5.4/drivers/staging/media/meson/vdec/ |
| D | TODO | 5 stack that follows the latest version of the specification, especially
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | vfio-mediated-device.rst | 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-v5.4/Documentation/devicetree/bindings/mtd/ |
| D | ibm,ndfc.txt | 12 - partition(s) - follows the OF MTD standard for partitions
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-devices-sun | 7 Configuration and Power Interface Specification as follows:
|
12345678910>>...19
