Searched full:connected (Results 1 – 25 of 1005) sorted by relevance
12345678910>>...41
| /Documentation/devicetree/bindings/power/ |
| D | rockchip-io-domain.yaml | 97 description: The supply connected to VCCIO1.
99 description: The supply connected to VCCIO2.
101 description: The supply connected to VCCIO3.
103 description: The supply connected to VCCIO4.
105 description: The supply connected to VCCIO5.
107 description: The supply connected to VCCIO6.
109 description: The supply connected to VCCIO_OSCGPI.
121 description: The supply connected to PMUIO1.
123 description: The supply connected to PMUIO2.
135 description: The supply connected to AP0_VCC.
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | fcs,fsa4480.yaml | 49 Specifies how the AUX+/- lines are connected to SBU1/2.
56 - AUX+ connected to SBU2
57 - AUX- connected to SBU1
59 - AUX+ connected to SBU1
60 - AUX- connected to SBU2
66 - AUX+ connected to SBU1
67 - AUX- connected to SBU2
69 - AUX+ connected to SBU2
70 - AUX- connected to SBU1
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ntc-thermistor.yaml | 19 When used in practice, a thermistor is often connected between ground, a
34 / | | "connected ground"
41 | | (pdo) | "connected positive"
48 called "connected ground" and "connected positive" and shall be understood as
51 If the pull-up resistance is 0 one end of the thermistor is connected to the
56 connected to ground and we get the thermistor under the pull-up resistor
60 the figure illustrates where the voltage will be measured for the "connected
61 ground" and "connected positive" cases.
109 connected-positive:
111 description: Indicates how the thermistor is connected in series with
[all …]
|
| D | nsa320-mcu.txt | 6 - data-gpios : The GPIO pin connected to the data line on the MCU
7 - clk-gpios : The GPIO pin connected to the clock line on the MCU
8 - act-gpios : The GPIO pin connected to the active line on the MCU
|
| /Documentation/devicetree/bindings/bus/ |
| D | ts-nbus.txt | 11 - ts,data-gpios : The 8 GPIO pins connected to the data lines on the FPGA
12 - ts,csn-gpios : The GPIO pin connected to the csn line on the FPGA
13 - ts,txrx-gpios : The GPIO pin connected to the txrx line on the FPGA
14 - ts,strobe-gpios : The GPIO pin connected to the stobe line on the FPGA
15 - ts,ale-gpios : The GPIO pin connected to the ale line on the FPGA
16 - ts,rdy-gpios : The GPIO pin connected to the rdy line on the FPGA
|
| /Documentation/ABI/testing/ |
| D | sysfs-c2port | 30 of the connected micro.
37 access to the on-board flash of the connected micro.
45 the on-board flash block size of the connected micro.
52 the on-board flash blocks number of the connected micro.
59 the content of the on-board flash of the connected micro.
66 the "erase" command on the on-board flash of the connected
74 command on the connected micro.
81 of the connected micro.
|
| D | sysfs-bus-fsi | 6 Initiates a FSI master scan for all connected slave devices
15 link to any connected slaves. A BREAK resets connected
25 connected slave. A terminate resets the slave's state machines
26 that control access to the internally connected engines. In
|
| D | sysfs-devices-mapping | 41 value that means UPI link number X on die Y is connected to UPI
59 UPI link 0 on die 0 is connected to UPI link 1 on die 1
60 UPI link 0 on die 1 is connected to UPI link 0 on die 3
61 UPI link 0 on die 2 is connected to UPI link 1 on die 3
62 UPI link 0 on die 3 is connected to UPI link 0 on die 1
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | conn-states-8.dot | 6 WFReportParams -> Connected [ label = "in receive_param()" ]
11 SyncSource -> Connected
12 SyncTarget -> Connected
17 Connected -> WFConnection [ label = "* on network error" ]
|
| D | drbd-connection-state-overview.dot | 29 Connected [ label=Connected,style=filled,fillcolor=green,fontcolor=black ]
66 WFReportParams -> Connected [ label="data identical\lno sync needed",color=green,fontcolor=green ]
76 cluster_resync:any -> Connected [ label="resnyc done",fontcolor=green ]
80 Connected -> CommTrouble
|
| /Documentation/devicetree/bindings/rtc/ |
| D | isil,isl12057.txt | 11 (associated with the alarm supported by the driver) is not connected
15 be set when the IRQ#2 pin of the chip is not connected to the SoC but
26 the availability of an IRQ line connected to the SoC.
29 Example isl12057 node without IRQ#2 pin connected (no alarm support):
37 Example isl12057 node with IRQ#2 pin connected to main SoC via MPP6 (note
67 Example isl12057 node without IRQ#2 pin connected to the SoC but to a
|
| /Documentation/infiniband/ |
| D | ipoib.rst | 33 Datagram vs Connected modes
37 connected. The mode is set and read through an interface's
45 In connected mode, the IB RC (Reliable Connected) transport is used.
46 Connected mode takes advantage of the connected nature of the IB
52 In connected mode, the interface's UD QP is still used for multicast
53 and communication with peers that don't support connected mode. In
114 IP over InfiniBand: Connected Mode (RFC 4755)
|
| /Documentation/devicetree/bindings/media/ |
| D | renesas,isp.yaml | 47 Input port node, multiple endpoints describing the connected R-Car
53 Single endpoint describing the R-Car VIN connected to output port 0.
58 Single endpoint describing the R-Car VIN connected to output port 1.
63 Single endpoint describing the R-Car VIN connected to output port 2.
68 Single endpoint describing the R-Car VIN connected to output port 3.
73 Single endpoint describing the R-Car VIN connected to output port 4.
78 Single endpoint describing the R-Car VIN connected to output port 5.
83 Single endpoint describing the R-Car VIN connected to output port 6.
88 Single endpoint describing the R-Car VIN connected to output port 7.
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-consumer-common.yaml | 23 GPIO connected to the enable control pin.
27 GPIO (or GPIOs for power sequence) connected to the device reset pin
33 GPIO connected to the power down pin (hardware power down or power cut,
44 GPIO connected to the pin waking up the device from suspend or other
|
| /Documentation/devicetree/bindings/leds/ |
| D | maxim,max77693.yaml | 17 control a separate LED or they can be connected together to double the
18 maximum current for a single connected LED. One LED is represented by one
75 Valid values for a LED connected to one FLED output:
77 Valid values for a LED connected to both FLED outputs:
82 Valid values for a single LED connected to one FLED output
85 Valid values for a single LED connected to both FLED outputs:
|
| /Documentation/devicetree/bindings/input/ |
| D | matrix-keymap.yaml | 7 title: Common Key Matrices on Matrix-connected Key Boards
13 A simple common binding for matrix-connected key boards. Currently targeted at
32 description: Number of row lines connected to the keypad controller.
36 description: Number of column lines connected to the keypad controller.
|
| D | samsung,s3c6410-keypad.yaml | 52 Number of column lines connected to the keypad controller.
57 Number of row lines connected to the keypad controller.
65 Each key connected to the keypad controller is represented as a child
71 description: The column number to which the key is connected.
75 description: The row number to which the key is connected.
|
| /Documentation/devicetree/bindings/net/wireless/ |
| D | ti,wl1251.txt | 3 The wl1251 chip can be connected via SPI or via SDIO. This
4 document describes the binding for the SPI connected chip.
14 - ti,wl1251-has-eeprom : boolean, the wl1251 has an eeprom connected, which
16 - ti,power-gpio : GPIO connected to chip's PMEN pin if operated in
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | ti,pruss-intc.yaml | 19 remaining 8 (2 through 9) connected to external interrupt controllers
25 (host_intr0 through host_intr7) are connected exclusively to the Arm interrupt
30 through 19) are connected to new sub-modules within the ICSSG instances.
69 connected to Arm interrupt controller, the name should match the
89 output interrupts 2 through 9) that are not connected to the Arm interrupt
94 connected to MPU
96 "host_intr7" interrupts connected to MPU, and other ICSSG
98 - AM64x SoCs have all the 8 host interrupts connected to various
|
| /Documentation/devicetree/bindings/iio/amplifiers/ |
| D | adi,hmc425a.yaml | 40 connected to the control pins.
41 ADRF5740 - 4 GPIO connected to D2-D5
42 HMC540S - 4 GPIO connected to V1-V4
43 HMC425A - 6 GPIO connected to V1-V6
44 LTC6373 - 3 GPIO connected to A0-A2
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | adi,ad7944.yaml | 48 line is used to initiate the conversion and the SDI line is connected to
58 can be connected to the CS line of the SPI controller or to a GPIO, in
64 chain is connected to the SPI bus. The CNV line of all chips are tied
84 connected to the same supply as ref-supply. Otherwise, when using an
86 is connected to a 5V supply.
96 external buffer with internal reference, this should be connected to a
104 'single' mode, this property is omitted if the CNV pin is connected to the
110 GPIO connected to the TURBO line. If omitted, it is assumed that the TURBO
126 connected to an interrupt that is triggered when the SDO line goes low
|
| /Documentation/devicetree/bindings/sound/ |
| D | maxim,max9759.yaml | 18 description: the gpio connected to the shutdown pin
22 description: the gpio connected to the mute pin
26 description: the 2 gpios connected to the g1 and g2 pins
|
| /Documentation/w1/slaves/ |
| D | w1_ds28e17.rst | 23 come and go as the DS28E17 devices come and go. I2C slave devices connected to
25 connected to a "native" I2C bus master.
41 it is connected. The power-on default of the DS28E17 is 400kBaud, but
43 as soon the "w1_ds28e17" driver notices a freshly connected, or
51 This sets up the default stretch value used for freshly connected
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | ltc2952-poweroff.txt | 10 - watchdog-gpios: phandle + gpio-specifier for the GPIO connected to the
12 - kill-gpios: phandle + gpio-specifier for the GPIO connected to the
16 - trigger-gpios: phandle + gpio-specifier for the GPIO connected to the
|
| /Documentation/devicetree/bindings/iio/resolver/ |
| D | adi,ad2s1210.yaml | 45 logic low and the WR/FSYNC line on the AD2S1210 should be connected to the
84 GPIO connected to the /RESET pin. As the line needs to be low for the
90 GPIO connected to the /SAMPLE pin. As the line needs to be low to trigger
96 GPIO lines connected to the A0 and A1 pins. These pins select the data
103 GPIO lines connected to the RES0 and RES1 pins. These pins select the
112 GPIO lines connected to the LOT and DOS pins. These pins combined indicate
121 instead of connected to GPIOS (i.e. mode-gpios is omitted).
|
12345678910>>...41