Searched full:both (Results 1 – 25 of 1206) sorted by relevance
12345678910>>...49
| /Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 9 space, or visible in both. (One example of that situation would be a
32 secure- bindings only need to be used where both the Secure and Normal
43 both default to "okay". This means the following combinations are
46 /* Neither specified: default to visible in both S and NS */
47 secure-status = "okay"; /* visible in both */
48 status = "okay"; /* visible in both */
49 status = "okay"; secure-status = "okay"; /* visible in both */
53 status = "disabled"; /* disabled in both */
54 status = "disabled"; secure-status = "disabled"; /* disabled in both */
|
| /Documentation/power/ |
| D | apm-acpi.rst | 13 build a kernel with both ACPI and APM enabled (as of 2.3.x ACPI is
18 No, sorry, you cannot have both ACPI and APM enabled and running at
20 would like to use both to get a full set of working features, but you
26 Both APM and ACPI rely on user-space daemons, apmd and acpid
27 respectively, to be completely functional. Obtain both of these
30 Go ahead and start both. If ACPI or APM is not available on your
|
| /Documentation/ABI/testing/ |
| D | debugfs-hisi-sec | 54 Available for both PF and VF, and take no other effect on SEC.
60 Available for both PF and VF, and take no other effect on SEC.
66 Available for both PF and VF, and take no other effect on SEC.
72 Available for both PF and VF, and take no other effect on SEC.
78 Available for both PF and VF, and take no other effect on SEC.
85 Available for both PF and VF, and take no other effect on SEC.
105 Available for both PF and VF, and take no other effect on SEC.
111 Available for both PF and VF, and take no other effect on SEC.
117 Available for both PF and VF, and take no other effect on SEC.
124 Available for both PF and VF, and take no other effect on SEC.
[all …]
|
| D | debugfs-hisi-hpre | 74 Available for both PF and VF, and take no other effect on HPRE.
80 Available for both PF and VF, and take no other effect on HPRE.
86 Available for both PF and VF, and take no other effect on HPRE.
92 Available for both PF and VF, and take no other effect on HPRE.
98 Available for both PF and VF, and take no other effect on HPRE.
105 Available for both PF and VF, and take no other effect on HPRE.
125 Available for both PF and VF, and take no other effect on HPRE.
131 Available for both PF and VF, and take no other effect on HPRE.
138 Available for both PF and VF, and take no other effect on HPRE.
144 Available for both PF and VF, and take no other effect on HPRE.
[all …]
|
| D | debugfs-hisi-zip | 67 Available for both PF and VF, and take no other effect on ZIP.
73 Available for both PF and VF, and take no other effect on ZIP.
79 Available for both PF and VF, and take no other effect on ZIP.
85 Available for both PF and VF, and take no other effect on ZIP.
91 Available for both PF and VF, and take no other effect on ZIP.
98 Available for both PF and VF, and take no other effect on ZIP.
118 Available for both PF and VF, and take no other effect on ZIP.
124 Available for both PF and VF, and take no other effect on ZIP.
131 Available for both PF and VF, and take no other effect on ZIP.
138 Available for both PF and VF, and take no other effect on ZIP.
|
| D | sysfs-bus-event_source-devices-uncore | 7 The 'perf(1)' tool should treat both names the same.
8 They both can be used to access the uncore PMU.
|
| D | sysfs-devices-platform-docg3 | 10 writes or both.
27 writes or both.
|
| /Documentation/devicetree/bindings/regmap/ |
| D | regmap.txt | 16 On SoCs that can be operated in both big-endian and little-endian
17 modes, with a single hardware switch controlling both the endianness
20 blob in both cases.
|
| /Documentation/userspace-api/media/v4l/ |
| D | tuner.rst | 35 determined by the current video input. Drivers must support both ioctls
57 A video or radio device cannot support both a tuner and a modulator. Two
69 current video output. Drivers must support both ioctls and set the
81 :ref:`VIDIOC_S_FREQUENCY <VIDIOC_G_FREQUENCY>` ioctl which both take
84 both ioctls when the tuner or modulator ioctls are supported, or when
|
| D | dev-mem2mem.rst | 17 supports both output (sending frames from memory to the hardware)
20 both sides and finally call :ref:`VIDIOC_STREAMON <VIDIOC_STREAMON>`
21 for both capture and output to start the hardware.
|
| D | field-order.rst | 101 - Images contain both fields, interleaved line by line. The temporal
108 - Images contain both fields, the top field lines are stored first
114 - Images contain both fields, the bottom field lines are stored
135 - Images contain both fields, interleaved line by line, top field
139 - Images contain both fields, interleaved line by line, top field
|
| /Documentation/driver-api/hte/ |
| D | tegra-hte.rst | 10 (Legacy Interrupt Controller) IRQ GTE. Both GTE instances get the timestamp
21 below. The GPIO GTE code supports both kernel and userspace consumers. The
44 The provider source code of both IRQ and GPIO GTE instances is located at
46 ``drivers/hte/hte-tegra194-test.c`` demonstrates HTE API usage for both IRQ
|
| /Documentation/devicetree/bindings/regulator/ |
| D | richtek,rt4801-regulator.yaml | 33 Else if both are specified, DSVP/DSVN could be controlled individually.
34 If this property not specified, treat both as always-on regulators.
53 for controlling both regulators. If this property not specified for
54 any regulator, treat both as always-on regulators.
|
| /Documentation/bpf/ |
| D | graph_ds_impl.rst | 36 details in common. Because both have "root"s ("head" for linked_list) and
40 Unless otherwise stated, examples and semantics below apply to both graph data
73 The "root" type for both linked_list and rbtree expects to be in a map_value
74 which also contains a ``bpf_spin_lock`` - in the above example both global
76 spin_lock to be associated with the ``bpf_rb_root`` by virtue of both being in
133 Both the read from and write to ``n->data`` would be rejected. The verifier
139 * Both graph data structures have pointer stability
155 Both terms currently only have meaning in the context of graph nodes and API.
159 Let's enumerate the properties of both types of references.
237 3) n and m are non-owning references, they both point to the same node
[all …]
|
| /Documentation/networking/dsa/ |
| D | lan9303.rst | 18 The LAN9303 can be managed both via MDIO and I2C, both supported by this driver.
24 When both user ports are joined to the same bridge, the normal HW MAC learning
|
| /Documentation/devicetree/bindings/phy/ |
| D | keystone-usb-phy.txt | 10 gate on the Keystone SOC for both the USB2 and USB3 PHY. Otherwise it is just
11 an NOP PHY driver. Hence this node is referenced as both the usb2 and usb3
|
| /Documentation/devicetree/bindings/leds/ |
| D | maxim,max77693.yaml | 30 In boost mode the device can produce up to 1.2A of total current on both
33 case both current sources are used.
77 Valid values for a LED connected to both FLED outputs:
85 Valid values for a single LED connected to both FLED outputs:
|
| /Documentation/trace/ |
| D | fprobe.rst | 83 Also, the unregister_fprobe() will guarantee that the both enter and exit
107 This is the ftrace address of the traced function (both entry and exit).
113 somewhere in the caller. This can be used at both entry and exit.
126 allocated and passed to both `entry_handler` and `exit_handler`.
171 The `fprobe::nmissed` field counts up in both cases. Therefore, the former
172 skips both of entry and exit callback and the latter skips the exit
173 callback, but in both case the counter will increase by 1.
|
| /Documentation/devicetree/bindings/cpufreq/ |
| D | cpufreq-spear.txt | 5 It supports both uniprocessor (UP) and symmetric multiprocessor (SMP) systems
16 Both required and optional properties listed above must be defined under node
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_build.rst | 14 To build both static libbpf.a and shared libbpf.so:
30 To build both static libbpf.a and shared libbpf.so against a custom libelf
|
| /Documentation/admin-guide/media/ |
| D | dvb_references.rst | 17 There, you'll find lots of information, from both development and usage
22 in both html and pdf formats, together with other useful documentation at:
|
| /Documentation/devicetree/bindings/sound/ |
| D | adi,axi-i2s.txt | 4 (capture) or both directions enabled.
15 the core. The core expects two dma channels if both transmit and receive are
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | thine,thc63lvd1024.yaml | 35 port@1, and both port@0 and port@1 shall contain endpoints.
39 mode pixels are output from both CMOS/TTL ports and both port@2 and
|
| /Documentation/w1/masters/ |
| D | omap-hdq.rst | 24 The controller supports operation in both HDQ and 1-wire mode. The essential
41 Please note to load both the modules with a different ID if required, but note
42 that the ID used should be same for both master and slave driver loading.
|
| /Documentation/litmus-tests/ |
| D | README | 17 stronger than a normal acquire: both the read and write parts of
34 Both the above litmus tests demonstrate the RCU grace period guarantee
|
12345678910>>...49