Searched full:attached (Results 1 – 25 of 296) sorted by relevance
12345678910>>...12
| /Documentation/ABI/testing/ |
| D | sysfs-bus-i2c-devices-fsa9480 | 5 show what device is attached
7 USB - USB device is attached
8 UART - UART is attached
10 JIG - JIG is attached
|
| D | sysfs-class-extcon | 12 attached simultaneously. Many of docks, cradles, and
15 may have both HDMI and Charger attached, or analog audio,
16 video, and USB cables attached simultaneously.
50 cables attached and HDMI and EAR_JACK cables detached.
79 (attached).
|
| D | sysfs-bus-pci-drivers-ehci_hcd | 23 For example: To force the high-speed device attached to
37 may be attached directly to a "rate-matching hub". This
|
| /Documentation/devicetree/bindings/serial/ |
| D | slave-device.txt | 4 attached devices. Common examples include Bluetooth, WiFi, NFC and GPS
7 Serial attached devices shall be a child node of the host UART device the
8 slave device is attached to. It is expected that the attached device is
|
| /Documentation/vm/ |
| D | swap_numa.rst | 18 swapB, with swapA attached to node 0 and swapB attached to node 1, are going
29 be swapped on: swapA and swapB are attached to node 0, swapC is attached to
30 node 1, swapD and swapE are attached to node 2 and swapF is attached to node3.
78 as the promoted value. So if multiple swap devices are attached to the same
|
| D | numa.rst | 29 to and accessible from any CPU attached to any cell and cache coherency
35 attached to the same cell will experience faster access times and higher
58 physical cell that has no memory attached, and reassign any CPUs attached to
135 node to which the "current CPU" is attached using one of the kernel's
144 attached to memoryless nodes would always incur the fallback path overhead
|
| /Documentation/devicetree/ |
| D | of_unittest.txt | 9 is attached to the live tree dynamically, independent of the machine's
116 in Figure 2 is attached to the live tree described in Figure 1.
127 Figure 2: Example test data tree to be attached to live tree.
130 required to attach the root('/') node. All other nodes are attached by calling
133 In the function of_attach_node(), the new node is attached as the child of the
136 data node is attached to the live tree above (Figure 1), the final structure is
177 test-child0 the test-sibling1 is attached that pushes the child node
182 already present in the live tree), then the node isn't attached rather its
190 order to remove the device nodes attached initially (first the leaf nodes are
|
| /Documentation/devicetree/bindings/net/ |
| D | broadcom-bluetooth.txt | 5 attached Broadcom devices.
7 Serial attached Broadcom devices shall be a child node of the host UART
8 device the slave device is attached to.
|
| D | qualcomm-bluetooth.txt | 5 attached Qualcomm devices.
7 Serial attached Qualcomm devices shall be a child node of the host UART
8 device the slave device is attached to.
|
| D | marvell-bluetooth.txt | 5 attached Marvell Bluetooth devices. The following chips are included in
|
| /Documentation/devicetree/bindings/mfd/ |
| D | allwinner,sun4i-a10-ts.yaml | 29 allwinner,ts-attached:
31 description: A touchscreen is attached to the controller
69 allwinner,ts-attached;
|
| /Documentation/devicetree/bindings/net/ieee802154/ |
| D | ca8210.txt | 9 - reset-gpio: GPIO attached to reset
10 - irq-gpio: GPIO attached to IRQ
|
| /Documentation/driver-api/ |
| D | s390-drivers.rst | 11 drive s390 based channel attached I/O devices. This includes interfaces
53 so-called channel attached devices. They are addressed via I/O
55 channel-attached devices, however, will never interact with the
59 I/O functions for channel-attached devices
95 attached device.
|
| D | scsi.rst | 28 are the default protocol for storage devices attached to USB, SATA, SAS,
183 Scan a host to determine which (if any) devices are attached. The
187 via an INQUIRY command; if the LUN has a device attached, a scsi_device
190 all to a scan of LUN 0. Otherwise, if LUN 0 has a device attached,
194 is seen that cannot have a device attached to it.
254 Serial Attached SCSI (SAS) transport class
258 attributes for Serial Attached SCSI, a variant of SATA aimed at large
323 variable number of disks (or disk like devices) attached, sharing a
|
| /Documentation/networking/ |
| D | ppp_generic.txt | 150 queue of transmit packets for each attached channel. Normally the
166 If multilink is not in use, this packet is then passed to the attached
252 /dev/ppp acts independently and can be attached either to a PPP unit
260 unattached. Using an ioctl call, it can then be attached to an
261 existing unit, attached to a newly-created unit, or attached to an
262 existing channel. An instance attached to a unit can be used to send
265 attached to a channel can be used to send and receive PPP frames on
270 write to the unit (i.e., to an instance of /dev/ppp attached to the
276 A channel is not initially attached to any unit. In this state it can
282 on whether it is unattached, attached to a PPP interface, or attached
[all …]
|
| D | kcm.txt | 57 Each multiplexor assumes that all attached TCP connections are to the same
86 When a TCP socket is attached to a KCM multiplexor data ready (POLLIN) and
96 socket buffer on the attached TCP socket (the socket buffer size can be set by
103 value is taken from the receive timeout of the attached TCP socket (this is set
163 fd: file descriptor for TCP socket being attached
269 TCP socket attached to a KCM multiplexor in epoll set for POLLERR
270 event. If an error occurs on an attached TCP socket, KCM sets an EPIPE
282 only one attached TCP socket). However, the application does retain
|
| /Documentation/devicetree/bindings/memory-controllers/ti/ |
| D | emif.txt | 6 of the EMIF IP and memory parts attached to it. Certain revisions
40 instance has a memory part attached to it. If there is a memory
41 part attached to CS1, it should be the same type as the one on CS0,
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb251xb.txt | 51 attached peripheral (range: 0 - 100000 uA, default 1000 uA)
55 attached peripheral (range: 0 - 510000 uA, default 100000 uA)
59 attached peripheral (range: 0 - 100000 uA, default 1000 uA)
63 attached peripheral (range: 0 - 510000 uA, default 100000 uA)
|
| /Documentation/bpf/ |
| D | prog_cgroup_sockopt.rst | 7 ``BPF_PROG_TYPE_CGROUP_SOCKOPT`` program type can be attached to two
68 has ``BPF_CGROUP_GETSOCKOPT`` attached at each level with
82 Same for ``BPF_CGROUP_SETSOCKOPT``: if the program is attached to
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | ortustech,com37h3m99dtc.txt | 8 - backlight: phandle of the backlight device attached to the panel
|
| D | ortustech,com37h3m05dtc.txt | 8 - backlight: phandle of the backlight device attached to the panel
|
| D | sharp,lq035q7db03.txt | 9 - backlight: phandle of the backlight device attached to the panel
|
| D | sharp,lq070y3dg3b.txt | 8 - backlight: phandle of the backlight device attached to the panel
|
| D | panasonic,vvx10f034n00.txt | 9 - backlight: phandle of the backlight device attached to the panel
|
| /Documentation/devicetree/bindings/display/msm/ |
| D | gpu.txt | 20 For GMU attached devices the GPU clocks are not used and are not required. The
27 - qcom,gmu: For GMU attached devices a phandle to the GMU device that will
|
12345678910>>...12