Lines Matching +full:display +full:- +full:interface
2 OMAP2/3 Display Subsystem
7 TV-out and multiple display support, but there are lots of small improvements
10 The DSS2 driver (omapdss module) is in arch/arm/plat-omap/dss/, and the FB,
15 --------
19 - MIPI DPI (parallel) output
20 - MIPI DSI output in command mode
21 - MIPI DBI (RFBI) output
22 - SDI output
23 - TV output
24 - All pieces can be compiled as a module or inside kernel
25 - Use DISPC to update any of the outputs
26 - Use CPU to update RFBI or DSI output
27 - OMAP DISPC planes
28 - RGB16, RGB24 packed, RGB24 unpacked
29 - YUV2, UYVY
30 - Scaling
31 - Adjusting DSS FCK to find a good pixel clock
32 - Use DSI DPLL to create DSS FCK
35 - OMAP3 SDP board
36 - Beagle board
37 - N810
40 --------------
47 flexible way to enable non-common multi-display configuration. In addition to
49 managers. These can be used when updating a display with CPU or system DMA.
52 --------------------------------
53 There exist several display technologies and standards that support audio as
55 interface that may be used by an audio driver or any other driver interested in
65 certain configurations audio is not supported (e.g., an HDMI display using a
67 the current configuration of the display supports audio.
70 parameters of the display. In order to make the function independent of any
73 moment, such structure contains pointers to IEC-60958 channel status word
74 and CEA-861 audio infoframe structures. This should be enough to support
75 HDMI and DisplayPort, as both are based on CEA-861 and IEC-60958.
90 the interface to keep track of the audio state. The initial state is _DISABLED;
97 ----------------------------
104 -------------
108 dynamic display architecture.
117 ------------
125 --------------------
129 - Framebuffer is a memory area inside OMAP's SRAM/SDRAM that contains the
132 - Overlay defines where the pixels are read from and where they go on the
135 the overlay is smaller than the display.
136 - Overlay manager combines the overlays in to one image and feeds them to
137 display.
138 - Display is the actual physical display device.
149 An overlay manager can be connected to one display. There are certain
152 - DISPC TV overlay manager can be only connected to TV display.
153 - Virtual overlay managers can only be connected to DBI or DSI displays.
154 - DISPC LCD overlay manager can be connected to all displays, except TV
155 display.
158 -----
159 The sysfs interface is mainly used for testing. I don't think sysfs
160 interface is the best for this in the final version, but I don't quite know
163 The sysfs interface is divided to two parts: DSS and FB.
167 rotate Rotation 0-3 for 0, 90, 180, 270 degrees
182 global_alpha global alpha 0-255 0=transparent 255=opaque
185 display Destination display
189 trans_key_type gfx-destination, video-source
193 /sys/devices/platform/omapdss/display? directory:
201 rotate Rotation 0-3 for 0, 90, 180, 270 degrees
202 timings Display timings (pixclock,xres/hfp/hbp/hsw,yres/vfp/vbp/vsw)
203 When writing, two special timings are accepted for tv-out:
214 --------
234 --------------------------
237 and TV-out are not in use. The columns from left to right are:
241 FB0 --- GFX -\ DVI
242 FB1 --- VID1 --+- LCD ---- LCD
243 FB2 --- VID2 -/ TV ----- TV
246 -------------------------------
250 w=`cat $dvi/timings | cut -d "," -f 2 | cut -d "/" -f 1`
251 h=`cat $dvi/timings | cut -d "," -f 3 | cut -d "/" -f 1`
254 echo "" > $mgr0/display
255 fbset -fb /dev/fb0 -xres $w -yres $h -vxres $w -vyres $h
256 # at this point you have to switch the dvi/lcd dip-switch from the omap board
257 echo "dvi" > $mgr0/display
262 FB0 --- GFX -\ -- DVI
263 FB1 --- VID1 --+- LCD -/ LCD
264 FB2 --- VID2 -/ TV ----- TV
267 ----------------------------------------
271 w=`cat $tv/timings | cut -d "," -f 2 | cut -d "/" -f 1`
272 h=`cat $tv/timings | cut -d "," -f 3 | cut -d "/" -f 1`
290 FB0 +-- GFX ---- LCD ---- LCD
291 \- VID1 ---- TV ---- TV
294 ----------
307 VRFB rotation requires much more memory than non-rotated framebuffer, so you
313 ---------------------
315 omapfb.mode=<display>:<mode>[,...]
316 - Default video mode for specified displays. For example,
317 "dvi:800x400MR-24@60". See drivers/video/modedb.c.
322 - VRAM allocated for a framebuffer. Normally omapfb allocates vram
323 depending on the display size. With this you can manually allocate
328 - Enable debug printing. You have to have OMAPFB debug support enabled
332 - Draw test pattern to framebuffer whenever framebuffer settings change.
336 - Use VRFB rotation for all framebuffers.
339 - Default rotation applied to all framebuffers.
340 0 - 0 degree rotation
341 1 - 90 degree rotation
342 2 - 180 degree rotation
343 3 - 270 degree rotation
346 - Default mirror for all framebuffers. Only works with DMA rotation.
348 omapdss.def_disp=<display>
349 - Name of default display, to which all overlays will be connected.
353 - Enable debug printing. You have to have DSS debug support enabled in
357 ----
363 - Lots of checks are missing or implemented just as BUG()
367 - Can be used for RGB16 and RGB24P modes. Probably not for RGB24U (how
372 - Not sure if needed