Home
last modified time | relevance | path

Searched refs:DSI (Results 1 – 25 of 64) sorted by relevance

123

/Linux-v5.10/Documentation/devicetree/bindings/display/
Dmipi-dsi-bus.txt1 MIPI DSI (Display Serial Interface) busses
6 define the syntax used to represent a DSI bus in a device tree.
8 This document describes DSI bus-specific properties only or defines existing
9 standard properties in the context of the DSI bus.
11 Each DSI host provides a DSI bus. The DSI host controller's node contains a
15 The following assumes that only a single peripheral is connected to a DSI
18 DSI host
22 a DSI host, the following properties apply to a node representing a DSI host.
26 bus. DSI peripherals are addressed using a 2-bit virtual channel number, so
34 conjunction with another DSI host to drive the same peripheral. Hardware
[all …]
Dtruly,nt35597.txt1 Truly model NT35597 DSI display driver
18 for single DSI or Dual DSI
19 This should be low for dual DSI and high for single DSI mode
23 - port@0: DSI input port driven by master DSI
24 - port@1: DSI input port driven by secondary DSI
Dste,mcde.txt4 and displaying several channels memory resident graphics data on DSI or
24 - #address-cells: should be <1> (for the DSI hosts that will be children)
25 - #size-cells: should be <1> (for the DSI hosts that will be children)
30 The devicetree must specify subnodes for the DSI host adapters.
35 - reg: must specify the register range for the DSI host
45 Display panels and bridges will appear as children on the DSI hosts, and
46 the displays are connected to the DSI hosts using the common binding
50 If a DSI host is unused (not connected) it will have no children defined.
98 /* This DSI port only has the Low Power / Energy Save clock */
/Linux-v5.10/Documentation/devicetree/bindings/display/bridge/
Dcdns,dsi.txt1 Cadence DSI bridge
4 The Cadence DSI bridge is a DPI to DSI bridge supporting up to 4 DSI lanes.
9 - interrupts: interrupt line connected to the DSI bridge.
10 - clocks: DSI bridge clocks.
18 - resets: DSI reset lines.
24 * port 0: this port is only needed if some of your DSI devices are
27 DSI virtual channel used by this device.
31 - one subnode per DSI device connected on the DSI bus. Each DSI device should
Dtoshiba,tc358764.txt1 TC358764 MIPI-DSI to LVDS panel bridge
5 - reg: the virtual channel number of a DSI peripheral
13 0: DSI Input, not required, if the bridge is DSI controlled
Dadi,adv7511.txt6 conversion, S/PDIF, CEC and HDCP. ADV7533/5 supports the DSI interface for input
58 - adi,dsi-lanes: Number of DSI data lanes connected to the DSI host. It should
77 DSI data lanes, rather than generate its own timings for HDMI output.
89 - Video port 0 for the RGB, YUV or DSI input. In the case of ADV7533/5, the
Dtoshiba,tc358767.txt17 to a DPI/DSI source and to an eDP/DP sink according to [1][2]:
18 - port@0: DSI input port
/Linux-v5.10/drivers/gpu/drm/msm/
DKconfig70 bool "Enable DSI support in MSM DRM driver"
76 Choose this option if you have a need for MIPI DSI connector
80 bool "Enable DSI PLL driver in MSM DRM"
84 Choose this option to enable DSI PLL driver which provides DSI
88 bool "Enable DSI 28nm PHY driver in MSM DRM"
92 Choose this option if the 28nm DSI PHY is used on the platform.
95 bool "Enable DSI 20nm PHY driver in MSM DRM"
99 Choose this option if the 20nm DSI PHY is used on the platform.
102 bool "Enable DSI 28nm 8960 PHY driver in MSM DRM"
106 Choose this option if the 28nm DSI PHY 8960 variant is used on the
[all …]
DNOTES12 Plus a handful of blocks around them for HDMI/DSI/etc output.
18 But, HDMI/DSI/etc blocks seem like they can be shared across multiple
40 encoder -> DTV/LCDC/DSI (within MDP4) /
41 connector -> HDMI/DSI/etc --> other device(s)
54 connector -> HDMI/DSI/eDP/etc --> other device(s)
57 than needing a different implementation for DTV, DSI, etc. (Ie. the
60 Also unlike MDP4, with MDP5 all the IRQs for other blocks (HDMI, DSI,
/Linux-v5.10/drivers/gpu/drm/bridge/
DKconfig20 tristate "Cadence DPI/DSI bridge"
27 Support Cadence DPI to DSI bridge. This is an internal
52 tristate "Lontium LT9611 DSI/HDMI bridge"
59 Driver for Lontium LT9611 DSI to HDMI bridge
60 chip driver that converts dual DSI and I2S to
85 tristate "Northwest Logic MIPI DSI Host controller"
97 This enables the Northwest Logic MIPI DSI Host controller as
118 tristate "Parade PS8640 MIPI DSI to eDP Converter"
126 MIPI DSI to eDP converter
170 tristate "TC358762 DSI/DPI bridge"
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/display/exynos/
Dexynos_dsim.txt1 Exynos MIPI DSI Master
11 - interrupts: should contain DSI interrupt
23 according to DSI host bindings (see MIPI DSI bindings [1])
24 - samsung,burst-clock-frequency: specifies DSI frequency in high-speed burst
26 - samsung,esc-clock-frequency: specifies DSI frequency in escape mode
32 Should contain DSI peripheral nodes (see MIPI DSI bindings [1]).
37 1: DSI output
/Linux-v5.10/Documentation/devicetree/bindings/display/msm/
Ddsi.txt1 Qualcomm Technologies Inc. adreno/snapdragon DSI output
3 DSI Controller:
10 - interrupts: The interrupt signal from the DSI block.
27 by a DSI PHY block. See [1] for details on clock bindings.
31 - phys: phandle to DSI PHY device node
34 - ports: Contains 2 DSI controller ports as child nodes. Each port contains
38 - panel@0: Node of panel connected to this DSI controller.
40 - qcom,dual-dsi-mode: Boolean value indicating if the DSI controller is
41 driving a panel which needs 2 DSI links.
42 - qcom,master-dsi: Boolean value indicating if the DSI controller is driving
[all …]
/Linux-v5.10/drivers/gpu/drm/panel/
DKconfig39 24 bit RGB per pixel. It provides a MIPI DSI interface to
49 45NA WUXGA PANEL DSI Video Mode panel
79 KD35T133 controller for 320x480 LCD panels with MIPI-DSI
89 4-lane 800x1280 MIPI DSI panel.
92 tristate "Feiyang FY07024DI26A30-D MIPI-DSI LCD panel"
98 Feiyang FY07024DI26A30-D MIPI-DSI interface.
125 24 bit RGB per pixel. It provides a MIPI DSI interface to
129 tristate "JDI LT070ME05000 WUXGA DSI panel"
134 Say Y here if you want to enable support for JDI DSI video mode
147 24 bit RGB per pixel. It provides a MIPI DSI interface to
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/display/ti/
Dti,omap5-dss.txt21 - DSS Submodules: RFBI, DSI, HDMI
59 DSI
66 - interrupts: the DSI interrupt line
68 - vdd-supply: power supply for DSI
73 - Video port for DSI output
74 - DSI controlled peripherals
76 DSI Endpoint required properties:
77 - lanes: list of pin numbers for the DSI lanes: CLK+, CLK-, DATA0+, DATA0-,
Dti,omap4-dss.txt21 - DSS Submodules: RFBI, VENC, DSI, HDMI
78 DSI
85 - interrupts: the DSI interrupt line
87 - vdd-supply: power supply for DSI
92 - Video port for DSI output
93 - DSI controlled peripherals
95 DSI Endpoint required properties:
96 - lanes: list of pin numbers for the DSI lanes: CLK+, CLK-, DATA0+, DATA0-,
Dti,omap3-dss.txt72 DSI
79 - interrupts: the DSI interrupt line
81 - vdd-supply: power supply for DSI
85 DSI Endpoint required properties:
86 - lanes: list of pin numbers for the DSI lanes: CLK+, CLK-, DATA0+, DATA0-,
/Linux-v5.10/Documentation/devicetree/bindings/display/mediatek/
Dmediatek,dsi.txt1 Mediatek DSI Device
4 The Mediatek DSI function block is a sink of the display subsystem and can
5 drive up to 4-lane MIPI DSI output. Two DSIs can be synchronized for dual-
20 to the input port of an attached DSI panel or DSI-to-eDP encoder chip.
32 - clock-output-names: name of the output clock line to the DSI encoder
/Linux-v5.10/Documentation/devicetree/bindings/phy/
Dmixel,mipi-dsi-phy.txt1 Mixel DSI PHY for i.MX8
3 The Mixel MIPI-DSI PHY IP block is e.g. found on i.MX8 platforms (along the
4 MIPI-DSI IP from Northwest Logic). It represents the physical layer for the
5 electrical signals for DSI.
/Linux-v5.10/drivers/gpu/drm/omapdrm/displays/
DKconfig5 tristate "Generic DSI Command Mode Panel"
8 Driver for generic DSI command mode panels.
/Linux-v5.10/drivers/video/fbdev/omap2/omapfb/dss/
DKconfig34 <debugfs>/omapdss/dsi_irq for DSI interrupts.
75 bool "DSI support"
77 MIPI DSI (Display Serial Interface) support.
79 DSI is a high speed half-duplex serial interface between the host
82 See https://www.mipi.org/ for DSI specifications.
/Linux-v5.10/Documentation/devicetree/bindings/display/hisilicon/
Ddw-dsi.txt1 Device-Tree bindings for DesignWare DSI Host Controller v1.20a driver
3 A DSI Host Controller resides in the middle of display controller and external
11 - ports: contains DSI controller input and output sub port.
/Linux-v5.10/drivers/gpu/drm/omapdrm/dss/
DKconfig45 <debugfs>/omapdss/dsi_irq for DSI interrupts.
96 bool "DSI support"
99 MIPI DSI (Display Serial Interface) support.
101 DSI is a high speed half-duplex serial interface between the host
104 See http://www.mipi.org/ for DSI specifications.
/Linux-v5.10/drivers/phy/freescale/
DKconfig9 tristate "Mixel MIPI DSI PHY support"
15 Enable this to add support for the Mixel DSI PHY as found
/Linux-v5.10/drivers/gpu/drm/stm/
DKconfig19 tristate "STMicroelectronics specific extensions for Synopsys MIPI DSI"
23 Choose this option for MIPI DSI support on STMicroelectronics SoC.
/Linux-v5.10/Documentation/gpu/
Dtegra.rst22 outputs, such as RGB, HDMI, DSI, and DisplayPort.
80 controllers can drive both DSI outputs and both SOR outputs, the third cannot
81 drive any DSI.
103 longer do and instead provide standard interfaces such as DSI and eDP/DP.
111 the more standard DSI and eDP interfaces.
120 DSI subsection
123 Although Tegra has supported DSI since Tegra30, the controller has changed in
125 boards prior to Dalmore (Tegra114) have made use of DSI, only Tegra114 and

123