| /linux/Documentation/devicetree/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 to AP0_VCC.
[all …]
|
| /linux/drivers/gpu/drm/ci/xfails/ |
| H A D | virtio_gpu-none-fails.txt | 6 kms_bw@connected-linear-tiling-1-displays-1920x1080p,Fail
7 kms_bw@connected-linear-tiling-1-displays-2160x1440p,Fail
8 kms_bw@connected-linear-tiling-1-displays-2560x1440p,Fail
9 kms_bw@connected-linear-tiling-1-displays-3840x2160p,Fail
10 kms_bw@connected-linear-tiling-10-displays-1920x1080p,Fail
11 kms_bw@connected-linear-tiling-10-displays-2160x1440p,Fail
12 kms_bw@connected-linear-tiling-10-displays-2560x1440p,Fail
13 kms_bw@connected-linear-tiling-10-displays-3840x2160p,Fail
14 kms_bw@connected-linear-tiling-11-displays-1920x1080p,Fail
15 kms_bw@connected-linear-tiling-11-displays-2160x1440p,Fail
[all …]
|
| H A D | mediatek-mt8173-fails.txt | 2 kms_bw@connected-linear-tiling-1-displays-1920x1080p,Fail
3 kms_bw@connected-linear-tiling-1-displays-2560x1440p,Fail
4 kms_bw@connected-linear-tiling-1-displays-3840x2160p,Fail
5 kms_bw@connected-linear-tiling-2-displays-1920x1080p,Fail
6 kms_bw@connected-linear-tiling-2-displays-2160x1440p,Fail
7 kms_bw@connected-linear-tiling-2-displays-2560x1440p,Fail
8 kms_bw@connected-linear-tiling-2-displays-3840x2160p,Fail
|
| /linux/drivers/auxdisplay/ |
| H A D | Kconfig | 67 Say Y here if you have an HD44780 or KS-0074 LCD connected to your
81 This is the index of the parallel port the panel is connected to. One
83 and LCD are connected to two separate ports, you have to start two
114 This enables and configures a keypad connected to the parallel port.
131 This enables and configures an LCD connected to the parallel port.
227 int "Parallel port pin number & polarity connected to the LCD E signal (-17...17) "
232 signal has been connected. It can be :
234 0 : no connection (eg: connected to ground)
235 1..17 : directly connected to any of these pins on the DB25 plug
236 -1..-17 : connected to the same pin through an inverter (eg: transistor).
[all …]
|
| /linux/fs/overlayfs/ |
| H A 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/sound/aoa/fabrics/ |
| H A 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/arch/arm/boot/dts/renesas/ |
| H A D | r9a06g032.dtsi | 530 /* GPIO0a[0] connected to pin GPIO0 */
531 /* GPIO0a[1..2] connected to pins GPIO3..4 */
532 /* GPIO0a[3..4] connected to pins GPIO9..10 */
533 /* GPIO0a[5] connected to pin GPIO12 */
534 /* GPIO0a[6..7] connected to pins GPIO15..16 */
535 /* GPIO0a[8..9] connected to pins GPIO21..22 */
536 /* GPIO0a[10] connected to pin GPIO24 */
537 /* GPIO0a[11..12] connected to pins GPIO27..28 */
538 /* GPIO0a[13..14] connected to pins GPIO33..34 */
539 /* GPIO0a[15] connected to pin GPIO36 */
[all …]
|
| /linux/Documentation/devicetree/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.
110 connected-positive:
112 description: Indicates how the thermistor is connected in series with
[all …]
|
| /linux/drivers/input/mouse/ |
| H A 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/Documentation/devicetree/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
|
| /linux/include/linux/platform_data/ |
| H A 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/Documentation/ABI/testing/ |
| H A 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.
|
| H A D | sysfs-bus-pci-drivers-xhci_hcd | 25 initialized, connected, configured and stalled.
36 connected to a USB host.
49 connected to a USB host.
61 connected to a USB host.
74 connected to a USB host.
100 connected to a USB host.
114 connected to a USB host.
127 connected to a USB host.
|
| /linux/drivers/input/touchscreen/ |
| H A D | Kconfig | 136 such as AT42QT602240/ATMXT224, connected to your system.
169 Say Y here if you have a bu21013 touchscreen connected to
182 connected to your system.
242 the Cypress TrueTouch(tm) Standard Product family connected
255 Say Y here if the touchscreen is connected via I2C bus.
264 Say Y here if the touchscreen is connected via SPI bus.
314 Say Y here if you have a Dynapro serial touchscreen connected to
326 Say Y here if you have a Hampshire serial touchscreen connected to
338 Say Y here to enable support for I2C connected EETI touch panels.
347 Say Y here to enable support for I2C connected EETI
[all …]
|
| /linux/Documentation/infiniband/ |
| H A 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/Documentation/admin-guide/perf/ |
| H A D | nvidia-pmu.rst | 52 The NVLink-C2C0 PMU monitors incoming traffic from a GPU/CPU connected with
56 * NVIDIA Grace Hopper Superchip: Hopper GPU is connected with Grace SoC.
60 * NVIDIA Grace CPU Superchip: two Grace CPU SoCs are connected.
73 * Count event id 0x0 from the GPU/CPU connected with socket 0::
77 * Count event id 0x0 from the GPU/CPU connected with socket 1::
81 * Count event id 0x0 from the GPU/CPU connected with socket 2::
85 * Count event id 0x0 from the GPU/CPU connected with socket 3::
89 The NVLink-C2C has two ports that can be connected to one GPU (occupying both
97 * Count event id 0x0 from the GPU connected with socket 0 on port 0::
101 * Count event id 0x0 from the GPUs connected with socket 0 on port 0 and port 1::
[all …]
|
| /linux/include/net/ |
| H A 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/Documentation/devicetree/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
|
| /linux/drivers/iio/temperature/ |
| H A 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.
150 digital temperature sensor connected via I2C.
160 thermocouple sensor chip connected via SPI.
170 thermocouple sensor chip connected via SPI.
182 ...thermocouple EMF converters connected via I2C.
|
| /linux/drivers/phy/ |
| H A 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/Documentation/devicetree/bindings/media/ |
| H A D | renesas,isp.yaml | 85 Input port node, multiple endpoints describing the connected R-Car
91 Single endpoint describing the R-Car VIN connected to output port 0.
96 Single endpoint describing the R-Car VIN connected to output port 1.
101 Single endpoint describing the R-Car VIN connected to output port 2.
106 Single endpoint describing the R-Car VIN connected to output port 3.
111 Single endpoint describing the R-Car VIN connected to output port 4.
116 Single endpoint describing the R-Car VIN connected to output port 5.
121 Single endpoint describing the R-Car VIN connected to output port 6.
126 Single endpoint describing the R-Car VIN connected to output port 7.
|
| /linux/drivers/usb/dwc3/ |
| H A D | dwc3-apple.c | 41 * After both the PHY and dwc3 are initialized we will only ever see a single "new device connected"
45 * connected on the other end.
46 * This can be partially explained because the USB2 D+/D- lines are connected through a stateful
48 * resets the repeater out-of-band everytime the CC lines are (dis)connected. This then requires a
59 * it was until the next cable is connected we'd need to tear it all down and bring it back up again
64 * During initial probe we don't have any information about the connected cable and can't bring up
66 * and defer the first dwc3 probe until we get the first cable connected event. Until then we stay
68 * Once a cable is connected we then keep track of the controller mode here by transitioning to
73 DWC3_APPLE_NO_CABLE, /* No cable connected, dwc3 suspended after dwc3_core_exit */
74 DWC3_APPLE_HOST, /* Cable connected, dwc3 in host mode */
[all …]
|
| /linux/Documentation/devicetree/bindings/iio/adc/ |
| H A 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
|
| /linux/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3588-friendlyelec-cm3588-nas.dts | 384 /* Connected to MIPI-DSI0 */
442 /* Connected to MIPI-CSI1 */
445 /* GPIO Connector, connected to 40-pin GPIO header */
572 /* Connected to 5V Fan */
579 /* Connected to MIPI-DSI0 */
585 /* Connected to IR Receiver */
592 /* GPIO Connector, connected to 40-pin GPIO header */
600 /* GPIO Connector, connected to 40-pin GPIO header */
607 /* Connected to Buzzer */
614 /* GPIO Connector, connected to 40-pin GPIO header */
[all …]
|
| /linux/Documentation/devicetree/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
|