| /linux-6.8/Documentation/devicetree/bindings/power/ |
| D | rockchip-io-domain.yaml | 95 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.
107 description: The supply connected to VCCIO_OSCGPI.
119 description: The supply connected to PMUIO1.
121 description: The supply connected to PMUIO2.
133 description: The supply connected to AP0_VCC.
[all …]
|
| /linux-6.8/drivers/auxdisplay/ |
| D | Kconfig | 74 hex "Parallel port where the LCD is connected"
78 The address of the parallel port where the LCD is connected.
205 Say Y here if you have an HD44780 or KS-0074 LCD connected to your
219 This is the index of the parallel port the panel is connected to. One
221 and LCD are connected to two separate ports, you have to start two
252 This enables and configures a keypad connected to the parallel port.
269 This enables and configures an LCD connected to the parallel port.
365 int "Parallel port pin number & polarity connected to the LCD E signal (-17...17) "
370 signal has been connected. It can be :
372 0 : no connection (eg: connected to ground)
[all …]
|
| /linux-6.8/fs/overlayfs/ |
| D | export.c | 39 * "layer N connected" ancestor and verifying that all parents along the way are
42 * making that ancestor "layer N connected". For example:
50 * in ovl_lookup_real_ancestor() will not be able to lookup a connected overlay
51 * dentry from the connected lower dentry /a/b/c.
55 * /a/b. After copy up (and index) of /a/b, it will become "layer 2 connected"
58 * a connected overlay dentry will be accomplished.
62 * layer 1. If that improvement is made, then the check for "layer N connected"
93 * @dentry is "connected" if all ancestors up to root or a "connected" ancestor
95 * copy up a "connectable" ancestor to make it "connected". A "connected" dentry
96 * cannot become non "connected", so cache positive result in dentry flags.
[all …]
|
| /linux-6.8/sound/aoa/fabrics/ |
| D | layout.c | 31 * we think is connected. This information is hard-
48 int connected; member
49 /* codec dependent bit to be set in the aoa_codec.connected field.
118 /* onyx with all but microphone connected */
121 .connected = CC_SPEAKERS | CC_HEADPHONE | CC_LINEOUT,
125 .connected = CC_DIGITALOUT,
129 .connected = CC_LINEIN,
132 {} /* terminate array by .connected == 0 */
138 .connected = CC_SPEAKERS | CC_LINEOUT |
143 .connected = CC_DIGITALOUT,
[all …]
|
| /linux-6.8/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 …]
|
| /linux-6.8/Documentation/devicetree/bindings/usb/ |
| D | fcs,fsa4480.yaml | 54 Specifies how the AUX+/- lines are connected to SBU1/2.
61 - AUX+ connected to SBU2
62 - AUX- connected to SBU1
64 - AUX+ connected to SBU1
65 - AUX- connected to SBU2
71 - AUX+ connected to SBU1
72 - AUX- connected to SBU2
74 - AUX+ connected to SBU2
75 - AUX- connected to SBU1
|
| /linux-6.8/include/linux/platform_data/ |
| D | ad7793.h | 27 * @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-6.8/drivers/input/mouse/ |
| D | Kconfig | 24 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-6.8/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
|
| /linux-6.8/drivers/input/touchscreen/ |
| D | Kconfig | 124 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.
332 Say Y here if you have a Dynapro serial touchscreen connected to
344 Say Y here if you have a Hampshire serial touchscreen connected to
[all …]
|
| /linux-6.8/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)
|
| /linux-6.8/include/net/ |
| D | llc_c_st.h | 24 #define LLC_CONN_STATE_NORMAL 3 /* connected state */
25 #define LLC_CONN_STATE_BUSY 4 /* connected state */
26 #define LLC_CONN_STATE_REJ 5 /* connected state */
27 #define LLC_CONN_STATE_AWAIT 6 /* connected state */
28 #define LLC_CONN_STATE_AWAIT_BUSY 7 /* connected state */
29 #define LLC_CONN_STATE_AWAIT_REJ 8 /* connected state */
|
| /linux-6.8/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.
|
| D | renesas,vin.yaml | 19 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 …]
|
| /linux-6.8/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
|
| /linux-6.8/drivers/iio/temperature/ |
| D | Kconfig | 35 thermocouple sensors connected via SPI.
62 MLX90614 contact-less infrared sensor connected with I2C.
74 connected with I2C.
86 connected with I2C.
148 digital temperature sensor connected via I2C.
158 thermocouple sensor chip connected via SPI.
168 thermocouple sensor chip connected via SPI.
178 thermocouple EMF converter connected via I2C.
|
| /linux-6.8/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
|
| /linux-6.8/drivers/phy/ |
| D | phy-lgm-usb.c | 48 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-6.8/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
|
| /linux-6.8/sound/virtio/ |
| D | virtio_jack.c | 29 * @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-6.8/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:
|
| /linux-6.8/arch/arm/boot/dts/aspeed/ |
| 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 …]
|
| /linux-6.8/Documentation/admin-guide/ |
| D | thunderbolt.rst | 45 (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-6.8/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" ]
|