| /freebsd-src/sys/contrib/device-tree/Bindings/power/ |
| H A 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 t
[all...] |
| H A D | rockchip-io-domain.txt | 57 - 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.
63 - vccio-oscgpi-supply: The supply connected to VCCIO_OSCGPI.
66 - pmuio1-supply: The supply connected to PMUIO1.
67 - pmuio2-supply: The supply connected to PMUIO2.
70 - ap0-supply: The supply connected to AP0_VCC.
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/hwmon/ |
| H A 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 …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/usb/ |
| H A 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
|
| /freebsd-src/sys/contrib/device-tree/Bindings/media/ |
| H A 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.
|
| H A D | cec-gpio.txt | 13 - 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 D | renesas,vin.yaml | 19 Depending on the instance the VIN input is connected to external SoC pins, or
169 modules connected the VIN.
174 description: Endpoint connected to CSI20.
178 description: Endpoint connected to CSI21.
182 description: Endpoint connected to CSI40.
186 description: Endpoint connected to CSI41.
202 modules connected the VIN.
207 description: Endpoint connected to ISP0.
211 description: Endpoint connected to ISP1.
215 description: Endpoint connected t
[all...] |
| /freebsd-src/sys/contrib/device-tree/Bindings/bus/ |
| H A 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
|
| /freebsd-src/sys/contrib/device-tree/Bindings/input/touchscreen/ |
| H A D | pixcir_i2c_ts.txt | 6 - 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
|
| /freebsd-src/sys/contrib/device-tree/Bindings/rtc/ |
| H A 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
|
| /freebsd-src/sys/contrib/device-tree/Bindings/interrupt-controller/ |
| H A 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
|
| /freebsd-src/crypto/openssl/doc/man3/ |
| H A D | BIO_s_datagram.pod | 46 This BIO can be used with either a connected or unconnected network socket. A
47 connected socket is a network socket which has had L<BIO_connect(3)> or a
56 to become connected. These controls are provided to indicate to the BIO how
68 BIO_s_dgram() only with a connected socket. An exception is where
84 connected.
89 connected, and therefore how the BIO_s_datagram() should attempt to use the
93 underlying socket has been connected and will attempt to use the socket using OS
96 is connected.
99 socket is not connected and will attempt to use the socket using an OS APIs
164 can only be used with a connected socket.
|
| /freebsd-src/contrib/llvm-project/llvm/include/llvm/Support/ |
| H A D | Process.h | 132 /// This function determines if the standard input is connected directly
137 /// This function determines if the standard output is connected to a
142 /// This function determines if the standard error is connected to a
147 /// This function determines if the given file descriptor is connected to
157 /// if standard output is connected to a "tty" or "console"
158 /// window. If standard output is not connected to a tty or
164 /// if standard error is connected to a "tty" or "console"
165 /// window. If standard error is not connected to a tty or
170 /// This function determines whether the terminal connected to standard
171 /// output supports colors. If standard output is not connected to a
[all …]
|
| /freebsd-src/sys/contrib/device-tree/src/arm/aspeed/ |
| H A D | aspeed-bmc-tyan-s7106.dts | 125 /* BMC "debug" (console) UART; connected to RS-232 connector
258 /* Also connected to:
266 /* Directly connected to PCH SMBUS #0 */
279 /* Also connected to:
315 /* Also connected to:
323 /* Connected to:
327 /* Connected via switch to:
345 /* Connected via switch (PCH_BMC_SMB_SW_P) to:
358 /* Connected via switch (BMC_PE_SMB_EN_1_N) to
366 /* Connected via switch (BMC_PE_SMB_EN_2_N) to
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/leds/ |
| H A 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:
|
| /freebsd-src/sys/contrib/device-tree/Bindings/iio/resolver/ |
| H A 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).
|
| /freebsd-src/sys/contrib/device-tree/Bindings/input/ |
| H A D | samsung-keypad.txt | 22 - 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-src/sys/contrib/device-tree/Bindings/iio/accel/ |
| H A D | bma180.txt | 17 - 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-src/usr.sbin/ppp/ |
| H A D | udp.c | 71 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()
282 /* See if we're a connected udp socket */ in udp_Create()
307 log_Printf(LogPHASE, "%s: Link is a connected udp socket\n", in udp_Create()
309 dev->connected = UDP_CONNECTED; in udp_Create()
[all …]
|
| /freebsd-src/share/man/man4/ |
| H A D | ng_bridge.4 | 48 Each link (represented by a connected hook) is used to transmit
60 A loop is when two ports are connected to the same physical medium.
78 Each connected hook represents a bridged link.
83 Typically these hooks are connected to the
126 available hook, unless the first connected hook is an
134 If the first connected hook is an
139 hooks are connected later.
191 which must be currently connected:
|
| H A D | ng_ether.4 | 71 When connected, all incoming packets are forwarded to this hook,
77 being connected.
82 When connected, all outgoing packets are forwarded to this hook,
88 being connected.
100 if connected.
105 When no hooks are connected,
109 are in effect connected together,
|
| /freebsd-src/sys/contrib/device-tree/Bindings/net/nfc/ |
| H A D | pn532.txt | 6 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-src/secure/lib/libcrypto/man/man3/ |
| H A D | BIO_s_datagram.3 | 177 This \s-1BIO\s0 can be used with either a connected or unconnected network socket. A
178 connected socket is a network socket which has had \fBBIO_connect\fR\|(3) or a
185 to become connected. These controls are provided to indicate to the \s-1BIO\s0 how
195 \&\fBBIO_s_dgram()\fR only with a connected socket. An exception is where
206 connected.
210 connected, and therefore how the \fBBIO_s_datagram()\fR should attempt to use the
214 underlying socket has been connected and will attempt to use the socket using \s-1OS\s0
217 is connected.
220 socket is not connected and will attempt to use the socket using an \s-1OS\s0 APIs
274 can only be used with a connected socket.
|
| /freebsd-src/share/doc/psd/18.gprof/ |
| H A D | postp.me | 88 In these cases, we discover strongly-connected
92 We use a variation of Tarjan's strongly-connected
94 that discovers strongly-connected components as it is assigning
97 Time propagation within strongly connected
108 does not work within strongly connected components.
116 It is for these reasons that we collapse connected components.
182 Since they may complete strongly connected components,
|
| /freebsd-src/sys/contrib/device-tree/Bindings/gpio/ |
| H A 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
|