- 12 1月, 2010 2 次提交
-
-
由 Tomi Valkeinen 提交于
If the panel's probe had failed, omapfb would still go on, eventually crashing. A better fix would be to handle each display properly, and leaving just the failed display out. But that is a bigger change. Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Ville Syrjälä 提交于
If the scaling ratio is below 0.5 video output width can't be identical to the display width. Reject such settings. Signed-off-by: NVille Syrjälä <ville.syrjala@nokia.com> Acked-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
- 11 1月, 2010 4 次提交
-
-
由 Tomi Valkeinen 提交于
Loops checking for certain condition were rather inconsistent. Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com> Reported-by: NJuha Leppanen <juha_motorsportcom@luukku.com>
-
由 Tomi Valkeinen 提交于
Fixes bug causing VRFB memory area to be released twice. Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com> Reported-by: NEino-Ville Talvala <talvala@stanford.edu>
-
由 Vaibhav Hiremath 提交于
Signed-off-by: NVaibhav Hiremath <hvaibhav@ti.com> Acked-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Tomi Valkeinen 提交于
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
- 08 1月, 2010 4 次提交
-
-
由 Tomi Valkeinen 提交于
DSI driver didn't check if the panel driver actually implements enable_te(). Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Tomi Valkeinen 提交于
Collect interrupt statistics, printable via debugfs: debugfs/omapdss/dispc_irq debugfs/omapdss/dsi_irq The counters are reset when printed. Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Tomi Valkeinen 提交于
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Tomi Valkeinen 提交于
- dsi_vc_send_short() needs to use dest_per for the peripheral id - dsi_vc_send_null() was always using channel id 0 Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
- 10 12月, 2009 2 次提交
-
-
由 Tomi Valkeinen 提交于
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Tomi Valkeinen 提交于
Add Generic panel (user for DVI output) and Sharp LS037V7DW01 LCD panel. Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
- 09 12月, 2009 11 次提交
-
-
由 Tomi Valkeinen 提交于
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Tomi Valkeinen 提交于
DSI (Display Serial Interface) driver implements MIPI DSI interface. Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Tomi Valkeinen 提交于
SDI (Serial Display Interface) implements TI Flatlink 3G display interface. Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Tomi Valkeinen 提交于
RFBI (Remote FrameBuffer Interface) implements MIPI DBI interface. Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Tomi Valkeinen 提交于
VENC (video encoder) driver implements OMAP's analog S-Video/Composite TV-out. Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com> Acked-by: NTony Lindgren <tony@atomide.com>
-
由 Tomi Valkeinen 提交于
This implements MIPI DPI interface. Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Tomi Valkeinen 提交于
This file implements DISPC (display controller) block of the OMAP DSS. Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Tomi Valkeinen 提交于
Add more core files to DSS2. Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Tomi Valkeinen 提交于
The core files of DSS2. DSS2 commits are split a bit artificially to make the individual commits smaller, and DSS2 doesn't compile properly without the rest of the core commits. This shouldn't be a problem, as no configuration uses DSS2 yet. Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Tomi Valkeinen 提交于
VRFB rotation engine is a block in OMAP2/3 that offers 12 independent contexts that can be used for framebuffer rotation. Each context has a backend area of real memory, where it stores the pixels in undisclosed format. This memory is offered to users via 4 virtual memory areas, which see the same memory area in different rotation angles (0, 90, 180 and 270 degrees). Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-
由 Tomi Valkeinen 提交于
Add a Video RAM manager for OMAP 2 and 3 platforms. VRAM manager is used to allocate large continuous blocks of SDRAM or SRAM. The features VRAM manager has that are missing from dma_alloc_* functions are: - Support for OMAP2's SRAM - Allocate without ioremapping - Allocate at defined physical addresses - Allows larger VRAM area and larger allocations The upcoming DSS2 uses VRAM manager. VRAM area size can be defined in kernel config, board file or with kernel boot parameters. Board file definition overrides kernel config, and boot parameter overrides kernel config and board file. Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
-