Home
last modified time | relevance | path

Searched refs:connected (Results 1 – 25 of 1177) sorted by relevance

12345678910>>...48

/freebsd-14.2/sys/contrib/device-tree/Bindings/power/
H A Drockchip-io-domain.yaml95 description: The supply connected to VCCIO1.
97 description: The supply connected to VCCIO2.
99 description: The supply connected to VCCIO3.
101 description: The supply connected to VCCIO4.
103 description: The supply connected to VCCIO5.
105 description: The supply connected to VCCIO6.
119 description: The supply connected to PMUIO1.
121 description: The supply connected to PMUIO2.
145 description: The supply connected to VCCIO0.
159 description: The supply connected to VCCIO1.
[all …]
H A Drockchip-io-domain.txt57 - vccio6-supply: The supply connected to VCCIO6.
58 - vccio1-supply: The supply connected to VCCIO1.
59 - vccio2-supply: The supply connected to VCCIO2.
60 - vccio3-supply: The supply connected to VCCIO3.
61 - vccio4-supply: The supply connected to VCCIO4.
62 - vccio5-supply: The supply connected to VCCIO5.
66 - pmuio1-supply: The supply connected to PMUIO1.
67 - pmuio2-supply: The supply connected to PMUIO2.
76 - vccio0-supply: The supply connected to VCCIO0.
77 - vccio1-supply: The supply connected to VCCIO1.
[all …]
/freebsd-14.2/sys/contrib/device-tree/Bindings/hwmon/
H A Dntc-thermistor.yaml19 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 …]
H A Dnsa320-mcu.txt6 - 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
/freebsd-14.2/sys/contrib/device-tree/Bindings/input/touchscreen/
H A Dpixcir_i2c_ts.txt6 - interrupts: interrupt to which the chip is connected
7 - attb-gpio: GPIO connected to the ATTB line of the chip
12 - reset-gpios: GPIO connected to the RESET line of the chip
13 - enable-gpios: GPIO connected to the ENABLE line of the chip
14 - wake-gpios: GPIO connected to the WAKE line of the chip
H A Dzforce_ts.txt6 - interrupts: interrupt to which the chip is connected
7 - reset-gpios: reset gpio the chip is connected to
12 - irq-gpios : interrupt gpio the chip is connected to
/freebsd-14.2/sys/contrib/device-tree/Bindings/media/
H A Drenesas,isp.yaml47 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.
H A Dcec-gpio.txt13 - cec-gpios: gpio that the CEC line is connected to. The line should be
24 - hpd-gpios: gpio that the HPD line is connected to.
28 - v5-gpios: gpio that the 5V line is connected to.
30 Example for the Raspberry Pi 3 where the CEC line is connected to
32 connected to pin 11 aka BCM17 and the 5V line is connected to pin
H A Drenesas,vin.yaml19 Depending on the instance the VIN input is connected to external SoC pins, or
165 modules connected the VIN.
170 description: Endpoint connected to CSI20.
174 description: Endpoint connected to CSI21.
178 description: Endpoint connected to CSI40.
182 description: Endpoint connected to CSI41.
198 modules connected the VIN.
203 description: Endpoint connected to ISP0.
207 description: Endpoint connected to ISP1.
211 description: Endpoint connected to ISP2.
[all …]
/freebsd-14.2/sys/contrib/device-tree/Bindings/bus/
H A Dts-nbus.txt11 - 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
/freebsd-14.2/usr.sbin/ppp/
H A Dudp.c71 unsigned connected : 2; /* Have we connect()d ? */ member
88 switch (dev->connected) { in udp_Sendto()
99 if (dev->connected == UDP_MAYBEUNCONNECTED) { in udp_Sendto()
101 dev->connected = UDP_CONNECTED; in udp_Sendto()
104 dev->connected = UDP_UNCONNECTED; in udp_Sendto()
116 if (dev->connected == UDP_CONNECTED) in udp_Recvfrom()
238 dev->connected = UDP_CONNECTED; in udp_CreateDevice()
309 dev->connected = UDP_CONNECTED; in udp_Create()
314 dev->connected = UDP_MAYBEUNCONNECTED; in udp_Create()
/freebsd-14.2/usr.bin/tip/libacu/
H A Dhayes.c95 int connected = 0; in hay_dialer() local
120 connected = 0; in hay_dialer()
125 connected = 1; in hay_dialer()
127 if (connected) in hay_dialer()
131 return (connected); /* lets get out of here.. */ in hay_dialer()
143 return (connected); in hay_dialer()
H A Dventel.c75 int connected = 0; in ven_dialer() local
104 connected = gobble('!', line); in ven_dialer()
115 if (connected || dialtimeout || !boolean(value(VERBOSE))) in ven_dialer()
116 return (connected); in ven_dialer()
135 return (connected); in ven_dialer()
/freebsd-14.2/sys/contrib/device-tree/Bindings/rtc/
H A Disil,isl12057.txt11 (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
/freebsd-14.2/sys/contrib/device-tree/Bindings/iio/accel/
H A Dbma180.txt17 - vdd-supply : regulator phandle connected to the VDD pin
18 - vddio-supply : regulator phandle connected to the VDDIO pin
25 connected to the INT1 pin, the second (optional) interrupt
26 listed must be the one connected to the INT2 pin.
/freebsd-14.2/sys/contrib/device-tree/Bindings/mtd/
H A Dgpmc-onenand.txt1 Device tree bindings for GPMC connected OneNANDs
3 GPMC connected OneNAND (found on OMAP boards) are represented as child nodes of
13 - reg: The CS line the peripheral is connected to
14 - gpmc,device-width: Width of the ONENAND device connected to the GPMC
/freebsd-14.2/sys/contrib/device-tree/Bindings/net/nfc/
H A Dpn532.txt6 where the NFC chip is connected to.
11 Required properties if connected on i2c:
14 - interrupts: GPIO interrupt to which the chip is connected
38 Example (for PN532 connected via uart):
/freebsd-14.2/sys/contrib/device-tree/Bindings/sound/
H A Dmaxim,max9759.txt6 - shutdown-gpios : the gpio connected to the shutdown pin
7 - mute-gpios : the gpio connected to the mute pin
8 - gain-gpios : the 2 gpios connected to the g1 and g2 pins
/freebsd-14.2/sys/contrib/device-tree/Bindings/net/wireless/
H A Dti,wl1251.txt3 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
/freebsd-14.2/sys/contrib/device-tree/Bindings/gpio/
H A Dgpio-consumer-common.yaml23 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
/freebsd-14.2/sys/contrib/device-tree/Bindings/leds/
H A Dmaxim,max77693.yaml17 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:
/freebsd-14.2/sys/contrib/device-tree/src/arm/
H A Dimx6q-kontron-samx6i.dtsi28 /* SPI4_IMX_CS2# - connected to internal flash */
30 /* SPI4_IMX_CS0# - connected to SMARC SPI0_CS0# */
32 /* SPI4_CS3# - connected to SMARC SPI0_CS1# */
/freebsd-14.2/sys/contrib/device-tree/Bindings/input/
H A Dmatrix-keymap.yaml7 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.
H A Dsamsung-keypad.txt22 - samsung,keypad-num-rows: Number of row lines connected to the keypad
25 - samsung,keypad-num-columns: Number of column lines connected to the
28 - Keys represented as child nodes: Each key connected to the keypad
31 - keypad,row: the row number to which the key is connected.
32 - keypad,column: the column number to which the key is connected.
/freebsd-14.2/sys/contrib/device-tree/Bindings/interrupt-controller/
H A Dti,pruss-intc.yaml19 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

12345678910>>...48