Lines Matching +full:dsi +full:- +full:to +full:- +full:edp

7 buffer provided directly by the CPU, to its clients via channels. Software,
11 supports the built-in GPU, comprised of the gr2d and gr3d engines. Starting
18   - A host1x driver that provides infrastructure and access to the host1x
21   - A KMS driver that supports the display controllers as well as a number of
22     outputs, such as RGB, HDMI, DSI, and DisplayPort.
24   - A set of custom userspace IOCTLs that can be used to submit jobs to the
30 The various host1x clients need to be bound together into a logical device in
31 order to expose their functionality to users. The infrastructure that supports
35 tree for matching device nodes, adding the required clients to a list. Drivers
37 to the logical host1x device.
40 device using a driver-provided function which will set up the bits specific to
48 -------------------------------
50 .. kernel-doc:: include/linux/host1x.h
52 .. kernel-doc:: drivers/gpu/host1x/bus.c
56 --------------------------
58 .. kernel-doc:: drivers/gpu/host1x/syncpt.c
66 make it difficult to support with a parameterized driver.
69 -------------------
78 On Tegra186, the number of display controllers has been increased to three. A
80 controllers can drive both DSI outputs and both SOR outputs, the third cannot
81 drive any DSI.
86 A display controller controls a set of windows that can be used to composite
87 multiple buffers onto the screen. While it is possible to assign arbitrary Z
88 ordering to individual windows (by programming the corresponding blending
93 from YUV to RGB at scanout time. This makes them useful for displaying video
98 -------
103 longer do and instead provide standard interfaces such as DSI and eDP/DP.
111 the more standard DSI and eDP interfaces.
117 by the versatile SOR output, which supports eDP, DP and HDMI. The SOR is able
118 to support HDMI 2.0, though support for this is currently not merged.
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
128 eDP/DP
131 eDP was first introduced in Tegra124 where it was used to drive the display
138 The userspace interface provided by drm/tegra allows applications to create
140 to host1x.
143 -----------
145 The ``DRM_IOCTL_TEGRA_GEM_CREATE`` IOCTL is used to create a GEM buffer object
146 with Tegra-specific flags. This is useful for buffers that should be tiled, or
147 that are to be scanned out upside down (useful for 3D content).
154 ----------
160 Userspace can also request blocking on a syncpoint. To do so, it needs to
162 the syncpoint to wait for. The kernel will release the application when the
166 -------------------------
168 Before an application can submit command streams to host1x it needs to open a
169 channel to an engine using the ``DRM_IOCTL_TEGRA_OPEN_CHANNEL`` IOCTL. Client
170 IDs are used to identify the target of the channel. When a channel is no
172 IOCTL. To retrieve the syncpoint associated with a channel, an application
177 to the ``DRM_IOCTL_TEGRA_SUBMIT`` IOCTL along with various other parameters,