Lines Matching refs:to
11 currently side by side, you can choose which one to use.
24 - Use DISPC to update any of the outputs
25 - Use CPU to update RFBI or DSI output
30 - Adjusting DSS FCK to find a good pixel clock
31 - Use DSI DPLL to create DSS FCK
46 flexible way to enable non-common multi-display configuration. In addition to
53 well. Hence, it is relevant to update the DSS device driver to provide an audio
57 The audio_enable function is intended to prepare the relevant
59 some IP, enabling companion chips, etc). It is intended to be called before
61 intended to be called after audio_stop.
65 VESA video timing). The audio_supported function is intended to query whether
68 The audio_config function is intended to configure all the relevant audio
69 parameters of the display. In order to make the function independent of any
71 is to contain all the required parameters for audio configuration. At the
72 moment, such structure contains pointers to IEC-60958 channel status word
73 and CEA-861 audio infoframe structures. This should be enough to support
80 The audio_start/audio_stop function is intended to effectively start/stop audio
82 to be used in an atomic context. Hence, audio_start should return quickly and be
84 DMA channels, companion chips, etc) have been enabled to begin data transfers.
85 audio_stop is designed to only stop the audio transfers. The resources used
88 The enum omap_dss_audio_state may be used to help the implementations of
89 the interface to keep track of the audio state. The initial state is _DISABLED;
90 then, the state transitions to _CONFIGURED, and then, when it is ready to
91 play audio, to _ENABLED. The state _PLAYING is used when the audio is being
99 usually visible to users except through omapfb driver. They register
100 themselves to the DSS driver.
106 These framebuffers can be routed flexibly to any overlays, thus allowing very
120 From omapdss point of view the V4L2 drivers should be similar to framebuffer
135 - Overlay manager combines the overlays in to one image and feeds them to
139 A framebuffer can be connected to multiple overlays to show the same pixel data
142 framebuffer can be connected to any overlay.
144 An overlay can be connected to one overlay manager. Also DISPC overlays can be
145 connected only to DISPC overlay managers, and virtual overlays can be only
146 connected to virtual overlays.
148 An overlay manager can be connected to one display. There are certain
151 - DISPC TV overlay manager can be only connected to TV display.
152 - Virtual overlay managers can only be connected to DBI or DSI displays.
153 - DISPC LCD overlay manager can be connected to all displays, except TV
162 The sysfs interface is divided to two parts: DSS and FB.
168 overlays List of overlay numbers to which framebuffer pixels go
232 Here's the default setup on OMAP3 SDP board. All planes go to LCD. DVI
233 and TV-out are not in use. The columns from left to right are:
241 Example: Switch from LCD to DVI
250 # at this point you have to switch the dvi/lcd dip-switch from the omap board
260 Example: Clone GFX overlay to LCD and TV
289 can enable Contiguous Memory Allocator (CONFIG_CMA) to improve the dma
290 allocator, and if CMA is enabled, you use "cma=" kernel parameter to increase
293 Using DSI DPLL to generate pixel clock it is possible produce the pixel clock
300 probably need to increase your vram setting before using VRFB rotation. Also,
301 many applications may not work with VRFB if they do not pay attention to all
311 can be used to tv out.
317 "1:4M" to allocate 4M for fb1.
320 - Enable debug printing. You have to have OMAPFB debug support enabled
324 - Draw test pattern to framebuffer whenever framebuffer settings change.
325 You need to have OMAPFB debug support enabled in kernel config.
331 - Default rotation applied to all framebuffers.
341 - Name of default display, to which all overlays will be connected.
345 - Enable debug printing. You have to have DSS debug support enabled in
358 to skip the empty byte?)