Searched full:connect (Results 1 – 25 of 218) sorted by relevance
123456789
| /Documentation/admin-guide/media/ |
| D | dvb-usb-ttusb2-cardlist.rst | 19 * - Technotrend TT-connect CT-3650
21 * - Technotrend TT-connect S-2400
23 * - Technotrend TT-connect S-2400 (8kB EEPROM)
|
| D | dvb-usb-dvbsky-cardlist.rst | 31 * - TechnoTrend TT-connect CT2-4650 CI
33 * - TechnoTrend TT-connect CT2-4650 CI v1.1
35 * - TechnoTrend TT-connect S2-4650 CI
|
| D | dvb-usb-pctv452e-cardlist.rst | 17 * - Technotrend TT Connect S2-3600
19 * - Technotrend TT Connect S2-3650-CI
|
| /Documentation/devicetree/bindings/usb/ |
| D | smsc,usb3503.yaml | 22 connect-gpios:
25 GPIO for connect
116 connect-gpios = <&gpx3 0 1>;
134 connect-gpios = <&gpx3 0 1>;
155 connect-gpios = <&pio 4 17 GPIO_ACTIVE_HIGH>; /* PE17 */
|
| /Documentation/devicetree/bindings/phy/ |
| D | starfive,jh7110-pcie-phy.yaml | 27 - description: PHY connect offset of SYS_SYSCONSAIF__SYSCFG register for USB PHY.
29 The phandle to System Register Controller syscon node and the PHY connect offset
30 of SYS_SYSCONSAIF__SYSCFG register. Connect PHY to USB3 controller.
|
| /Documentation/hwmon/ |
| D | ntc_thermistor.rst | 46 1. connect = NTC_CONNECTED_POSITIVE, pullup_ohm > 0::
58 2. connect = NTC_CONNECTED_POSITIVE, pullup_ohm = 0 (not-connected)::
70 3. connect = NTC_CONNECTED_GROUND, pulldown_ohm > 0::
82 4. connect = NTC_CONNECTED_GROUND, pulldown_ohm = 0 (not-connected)::
95 pulldown_ohm, and connect should be provided. When none of the four models
|
| /Documentation/devicetree/bindings/arm/ |
| D | qcom,coresight-tpda.yaml | 18 TPDMs connect to it. But There must be only one TPDA in the path from the
19 TPDM source to TMC sink. TPDM can directly connect to TPDA's inport or
20 connect to funnel which will connect to TPDA's inport.
|
| /Documentation/devicetree/bindings/sound/ |
| D | mt8173-rt5650.txt | 13 <&rt5650 0> : Default setting. Connect rt5650 I2S1 for capture. (dai_name = rt5645-aif1)
14 <&rt5650 1> : Connect rt5650 I2S2 for capture. (dai_name = rt5645-aif2)
|
| D | ti,pcm512x.yaml | 46 description: GPIO pin used to connect the pll using <1> through <6>. The
53 description: GPIO pin used to connect the pll using <1> through <6>. The
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | drbd-connection-state-overview.dot | 21 label="try to connect, handshake"
52 // drbdadm [label="drbdadm connect"]
60 StandAlone -> Unconnected [ label="drbdadm connect" ]
|
| D | conn-states-8.dot | 4 WFConnection -> WFReportParams [ label = "in connect() after accept" ]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | hisilicon,mbigen-v2.txt | 12 Non-pci devices can connect to mbigen and generate the
15 The mbigen chip and devices connect to mbigen have the following properties:
69 Devices connect to mbigen required properties:
|
| /Documentation/driver-api/gpio/ |
| D | drivers-on-gpio.rst | 26 mouse cable and connect the wires to GPIO lines or solder a mouse connector
55 appear as any other I2C bus to the system and makes it possible to connect
61 and makes it possible to connect drivers for SPI devices on the bus like
83 - gpio-nand: drivers/mtd/nand/raw/gpio.c is used to connect a NAND flash chip
90 any other serio bus to the system and makes it possible to connect drivers
|
| /Documentation/devicetree/bindings/net/ |
| D | hisilicon-hns-nic.txt | 11 connect to 8 PHYs. Port 0 to 1 are both used for administration purpose. They
26 In Switch mode of DSAF, all 6 PHYs are taken as physical ports connect to a
27 LAN Switch while the CPU side assume itself have one single NIC connect to
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-pci-drivers-ehci_hcd | 15 Sometimes you want to force a high-speed device to connect
40 connect at full speed.
|
| D | sysfs-class-stm_source | 10 connect that device. If a device is already connected to this
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | renesas,rcar-gyroadc.yaml | 73 of the MB88101A connect directly to two CHS lines of the GyroADC,
81 A 3:8 chipselect demuxer is required to connect the nCS line
89 A 3:8 chipselect demuxer is required to connect the nCS line
|
| D | maxim,max34408.yaml | 53 SHTDN Enable Input. CMOS digital input. Connect to GND to clear the latch and
55 delay. Connect to VDD to enable normal latch operation of the SHTDN output.
|
| /Documentation/admin-guide/ |
| D | thunderbolt.rst | 33 Those users who just want to connect any device without any sort of
68 addition to UUID the device (if it supports secure connect) is sent
119 If the device supports secure connect, and the domain security level is
134 If the user does not want to use secure connect they can just ``echo 1``
138 If the user wants to use secure connect, the first time the device is
159 If the user still wants to connect the device they can either approve
221 device - then you need to connect that particular device).
308 do is to connect a Thunderbolt cable between the two hosts; the
|
| /Documentation/devicetree/bindings/media/ |
| D | allwinner,sun8i-a83t-mipi-csi2.yaml | 45 description: Input port, connect to a MIPI CSI-2 sensor
67 description: Output port, connect to a CSI controller
|
| D | allwinner,sun6i-a31-mipi-csi2.yaml | 53 description: Input port, connect to a MIPI CSI-2 sensor
75 description: Output port, connect to a CSI controller
|
| /Documentation/arch/powerpc/ |
| D | hvcs.rst | 200 Attempting to connect an application to /dev/hvcs* prior to insertion of
238 kermit to connect to /dev/hvcs0 when the console prompt becomes available
245 node. If this is not done, the next user to connect to the console will
250 is used to connect to each vty-server adapter. In order to determine which
254 /dev/hvcs* entry to use to connect to that device. For instance cating the
260 This index of '2' means that in order to connect to vty-server adapter
427 suggested that the user connect to the console hosting partition
439 A: You can use "screen" to directly connect to the /dev/hvcs* device and
464 Q: When I try to CONNECT kermit to an hvcs device I get:
480 outlined in the section on "Disconnection" in order for others to connect
[all …]
|
| /Documentation/trace/coresight/ |
| D | coresight-tpda.rst | 50 and these hw components will connect to the coresight funnel. When
51 there is only tpdm trace hw in the HW block, tpdm will connect to
|
| /Documentation/networking/ |
| D | phonet.rst | 118 However, connect() and getpeername() are not supported, as they did
170 As of Linux kernel version 2.6.39, it is also possible to connect
171 two endpoints directly, using connect() on the active side. This is
184 connect(fd, (struct sockaddr *)&spn, sizeof(spn));
|
| D | plip.rst | 35 The PLIP cable is all that's needed to connect two Linux boxes, and it
51 Can only be used to connect three (?) Linux boxes. Doesn't connect to
154 * Do not connect these pins on either end
188 * Do not connect these pins on either end
|
123456789