Searched full:follows (Results 1 – 25 of 429) sorted by relevance
12345678910>>...18
| /Documentation/devicetree/bindings/display/panel/ |
| 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.
|
| /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].
|
| /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
|
| /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 | 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:
|
| 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:
|
| /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:
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | mt6323-poweroff.txt | 7 - compatible: Should be one of follows
|
| /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
|
| /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 | 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
|
| 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):
|
| /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
|
| /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:
|
| /Documentation/devicetree/bindings/sound/ |
| D | everest,es8316.txt | 13 - clock-names : should include as follows:
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-sun | 7 Configuration and Power Interface Specification as follows:
|
| D | sysfs-driver-intel-rapid-start | 5 Description: An integer representing a set of wakeup events as follows:
|
| /Documentation/devicetree/bindings/crypto/ |
| D | fsl-sec2.txt | 18 EU_SEL0 field documentation, i.e. as follows:
36 field documentation, i.e. as follows:
|
| /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:
|
| /Documentation/kbuild/ |
| 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
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | jc42.txt | 6 chip names follows.
|
| /Documentation/filesystems/ext4/ |
| D | special_inodes.rst | 6 ext4 reserves some inode for special features, as follows:
|
12345678910>>...18