Home
last modified time | relevance | path

Searched full:connected (Results 1 – 25 of 3067) sorted by relevance

12345678910>>...123

/Linux-v5.15/Documentation/devicetree/bindings/power/
Drockchip-io-domain.yaml93 description: The supply connected to VCCIO1.
95 description: The supply connected to VCCIO2.
97 description: The supply connected to VCCIO3.
99 description: The supply connected to VCCIO4.
101 description: The supply connected to VCCIO5.
103 description: The supply connected to VCCIO6.
105 description: The supply connected to VCCIO_OSCGPI.
117 description: The supply connected to PMUIO1.
119 description: The supply connected to PMUIO2.
131 description: The supply connected to AP0_VCC.
[all …]
/Linux-v5.15/arch/arm/mach-pxa/
Dh5000.h29 /* 6 not connected */
30 #define H5000_GPIO_RESET_BUTTON_AGAIN_N (7) /* connected to gpio 1 as well */
31 /* 8 not connected */
35 /*(12) not connected */
39 /*(16) not connected */
40 /*(17) not connected */
45 /*(22) is not connected */
50 /*(27) not connected */
51 #define H5000_GPIO_I2S_BITCLK (28) /* connected to AC97 codec */
52 #define H5000_GPIO_I2S_DATAOUT (29) /* connected to AC97 codec */
[all …]
/Linux-v5.15/drivers/auxdisplay/
DKconfig68 hex "Parallel port where the LCD is connected"
72 The address of the parallel port where the LCD is connected.
201 Say Y here if you have an HD44780 or KS-0074 LCD connected to your
215 This is the index of the parallel port the panel is connected to. One
217 and LCD are connected to two separate ports, you have to start two
248 This enables and configures a keypad connected to the parallel port.
265 This enables and configures an LCD connected to the parallel port.
361 int "Parallel port pin number & polarity connected to the LCD E signal (-17...17) "
366 signal has been connected. It can be :
368 0 : no connection (eg: connected to ground)
[all …]
/Linux-v5.15/fs/overlayfs/
Dexport.c44 * "layer N connected" ancestor and verifying that all parents along the way are
47 * making that ancestor "layer N connected". For example:
55 * in ovl_lookup_real_ancestor() will not be able to lookup a connected overlay
56 * dentry from the connected lower dentry /a/b/c.
60 * /a/b. After copy up (and index) of /a/b, it will become "layer 2 connected"
63 * a connected overlay dentry will be accomplished.
67 * layer 1. If that improvement is made, then the check for "layer N connected"
98 * @dentry is "connected" if all ancestors up to root or a "connected" ancestor
100 * copy up a "connectable" ancestor to make it "connected". A "connected" dentry
101 * cannot become non "connected", so cache positive result in dentry flags.
[all …]
/Linux-v5.15/sound/aoa/fabrics/
Dlayout.c30 * we think is connected. This information is hard-
47 int connected; member
48 /* codec dependent bit to be set in the aoa_codec.connected field.
117 /* onyx with all but microphone connected */
120 .connected = CC_SPEAKERS | CC_HEADPHONE | CC_LINEOUT,
124 .connected = CC_DIGITALOUT,
128 .connected = CC_LINEIN,
131 {} /* terminate array by .connected == 0 */
137 .connected = CC_SPEAKERS | CC_LINEOUT |
142 .connected = CC_DIGITALOUT,
[all …]
/Linux-v5.15/include/linux/platform_data/
Dad7793.h27 * @AD7793_BIAS_VOLTAGE_AIN1: Bias voltage connected to AIN1(-).
28 * @AD7793_BIAS_VOLTAGE_AIN2: Bias voltage connected to AIN2(-).
29 * @AD7793_BIAS_VOLTAGE_AIN3: Bias voltage connected to AIN3(-).
55 * @AD7793_IEXEC1_IOUT1_IEXEC2_IOUT2: Current source IEXC1 connected to pin
56 * IOUT1, current source IEXC2 connected to pin IOUT2.
57 * @AD7793_IEXEC1_IOUT2_IEXEC2_IOUT1: Current source IEXC2 connected to pin
58 * IOUT1, current source IEXC1 connected to pin IOUT2.
59 * @AD7793_IEXEC1_IEXEC2_IOUT1: Both current sources connected to pin IOUT1.
61 * @AD7793_IEXEC1_IEXEC2_IOUT2: Both current sources connected to Pin IOUT2.
/Linux-v5.15/drivers/input/mouse/
DKconfig24 Say Y here if you have a PS/2 mouse connected to your system. This
47 Say Y here if you have an ALPS PS/2 touchpad connected to
57 Say Y here if you have a BYD PS/2 touchpad connected to
67 Say Y here if you have a Logitech PS/2++ mouse connected to
77 Say Y here if you have a Synaptics PS/2 TouchPad connected to
89 Say Y here if you have a Synaptics RMI4 touchpad connected to
99 Say Y here if you have a Cypress PS/2 Trackpad connected to
110 TouchScreen connected to your system.
119 Say Y here if you have an IBM Trackpoint PS/2 mouse connected
128 Say Y here if you have an Elantech PS/2 touchpad connected
[all …]
/Linux-v5.15/Documentation/ABI/testing/
Dsysfs-c2port30 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.
Dsysfs-bus-fsi6 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
/Linux-v5.15/drivers/input/touchscreen/
DKconfig124 such as AT42QT602240/ATMXT224, connected to your system.
157 Say Y here if you have a bu21013 touchscreen connected to
170 connected to your system.
230 the Cypress TrueTouch(tm) Standard Product family connected
243 Say Y here if the touchscreen is connected via I2C bus.
252 Say Y here if the touchscreen is connected via SPI bus.
273 Say Y here if the touchscreen is connected via I2C bus.
282 Say Y here if the touchscreen is connected via SPI bus.
316 Say Y here if you have a Dynapro serial touchscreen connected to
328 Say Y here if you have a Hampshire serial touchscreen connected to
[all …]
/Linux-v5.15/include/net/
Dllc_c_st.h20 #define LLC_CONN_STATE_NORMAL 3 /* connected state */
21 #define LLC_CONN_STATE_BUSY 4 /* connected state */
22 #define LLC_CONN_STATE_REJ 5 /* connected state */
23 #define LLC_CONN_STATE_AWAIT 6 /* connected state */
24 #define LLC_CONN_STATE_AWAIT_BUSY 7 /* connected state */
25 #define LLC_CONN_STATE_AWAIT_REJ 8 /* connected state */
/Linux-v5.15/Documentation/infiniband/
Dipoib.rst33 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)
/Linux-v5.15/Documentation/devicetree/bindings/bus/
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
/Linux-v5.15/Documentation/devicetree/bindings/media/
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
Drenesas,isp.yaml46 Input port node, multiple endpoints describing the connected R-Car
52 Single endpoint describing the R-Car VIN connected to output port 0.
57 Single endpoint describing the R-Car VIN connected to output port 1.
62 Single endpoint describing the R-Car VIN connected to output port 2.
67 Single endpoint describing the R-Car VIN connected to output port 3.
72 Single endpoint describing the R-Car VIN connected to output port 4.
77 Single endpoint describing the R-Car VIN connected to output port 5.
82 Single endpoint describing the R-Car VIN connected to output port 6.
87 Single endpoint describing the R-Car VIN connected to output port 7.
Drenesas,vin.yaml19 Depending on the instance the VIN input is connected to external SoC pins, or
164 modules connected the VIN.
169 description: Endpoint connected to CSI20.
173 description: Endpoint connected to CSI21.
177 description: Endpoint connected to CSI40.
181 description: Endpoint connected to CSI41.
197 modules connected the VIN.
202 description: Endpoint connected to ISP0.
206 description: Endpoint connected to ISP1.
210 description: Endpoint connected to ISP2.
[all …]
/Linux-v5.15/Documentation/devicetree/bindings/rtc/
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
/Linux-v5.15/drivers/phy/
Dphy-lgm-usb.c48 bool connected; member
111 ta->connected = false; in phy_shutdown()
141 bool connected; in tca_work() local
150 connected = extcon_get_state(ta->phy.edev, EXTCON_USB_HOST); in tca_work()
151 if (connected == ta->connected) in tca_work()
154 ta->connected = connected; in tca_work()
155 if (connected) { in tca_work()
159 dev_dbg(ta->phy.dev, "connected%s\n", flipped ? " flipped" : ""); in tca_work()
167 ret = ta->phy.set_vbus(&ta->phy, connected); in tca_work()
/Linux-v5.15/Documentation/devicetree/bindings/interrupt-controller/
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
/Linux-v5.15/drivers/input/joystick/
DKconfig47 tristate "Simple joystick connected over ADC"
51 Say Y here if you have a simple joystick connected over ADC.
152 Say Y here if you have a Logitech WingMan Warrior joystick connected
163 connected to your computer's serial port.
173 controller connected to your computer's serial port.
183 controller connected to your computer's serial port. For the
193 Say Y here if you have a Gravis Stinger connected to one of your
203 Say Y here if you have a Handykey Twiddler connected to your
228 Commodore, Amstrad CPC joystick connected to your parallel port.
243 Commodore, Amstrad CPC joystick connected to your parallel port.
[all …]
/Linux-v5.15/sound/soc/samsung/
Ds3c24xx_simtec_hermes.c21 /* Headphone connected to HP{L,R}OUT and HP{L,R}COM */
28 /* ZV connected to Line1 */
33 /* Line In connected to Line2 */
38 /* Microphone connected to MIC3R and MIC_BIAS */
42 /* GSM connected to MONO_LOUT and MIC3L (in) */
47 /* Speaker is connected to LINEOUT{LN,LP,RN,RP}, however we are
/Linux-v5.15/sound/virtio/
Dvirtio_jack.c29 * @connected: Current jack connection status.
38 bool connected; member
163 vjack->connected = info[i].connected; in virtsnd_jack_parse_cfg()
198 vjack->connected ? vjack->type : 0); in virtsnd_jack_build_devs()
223 vjack->connected = true; in virtsnd_jack_event()
226 vjack->connected = false; in virtsnd_jack_event()
232 snd_jack_report(vjack->jack, vjack->connected ? vjack->type : 0); in virtsnd_jack_event()
/Linux-v5.15/Documentation/admin-guide/blockdev/drbd/
Dconn-states-8.dot6 WFReportParams -> Connected [ label = "in receive_param()" ]
11 SyncSource -> Connected
12 SyncTarget -> Connected
17 Connected -> WFConnection [ label = "* on network error" ]
/Linux-v5.15/Documentation/admin-guide/
Dthunderbolt.rst45 (usbonly). The reason for these is the fact that the connected devices can
56 All devices are automatically connected by the firmware. No user
61 User is asked whether the device is allowed to be connected.
67 User is asked whether the device is allowed to be connected. In
92 If the security level reads as ``user`` or ``secure`` the connected
117 This will create the PCIe tunnels and the device is now connected.
145 Now the device is connected (PCIe tunnels are created) and in addition
155 on the key, the device is connected and the PCIe tunnels are created.
183 so connected devices cannot access memory regions outside of what is
220 matter which device is connected (unless you are upgrading NVM on a
[all …]
/Linux-v5.15/drivers/net/dsa/microchip/
DKconfig14 tristate "KSZ9477 series I2C connected switch driver"
21 tristate "KSZ9477 series SPI connected switch driver"
35 tristate "KSZ8795 series SPI connected switch driver"
45 tristate "KSZ series SMI connected switch driver"

12345678910>>...123