<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/include/video, branch v3.6</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v3.6</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v3.6'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2012-07-29T01:11:09Z</updated>
<entry>
<title>video: da8xx-fb: configure FIFO threshold to reduce underflow errors</title>
<updated>2012-07-29T01:11:09Z</updated>
<author>
<name>Manjunathappa, Prakash</name>
<email>prakash.pm@ti.com</email>
</author>
<published>2012-07-18T15:33:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=fb8fa9431971b9847aafaf89281570ca41bd0b40'/>
<id>urn:sha1:fb8fa9431971b9847aafaf89281570ca41bd0b40</id>
<content type='text'>
Patch works around the below silicon errata:
During LCDC initialization, there is the potential for a FIFO
underflow condition to occur. A FIFO underflow condition
occurs when the input FIFO is completely empty and the LCDC
raster controller logic that drives data to the output pins
attempts to fetch data from the FIFO. When a FIFO underflow
condition occurs, incorrect data will be driven out on the
LCDC data pins.

Software should poll the FUF bit field in the LCD_STAT register
to check if an error condition has occurred or service the
interrupt if FUF_EN is enabled when FUF occurs. If the FUF bit
field has been set to 1, this will indicate an underflow
condition has occurred and then the software should execute a
reset of the LCDC via the LPSC.

This problem may occur if the LCDC FIFO threshold size
(LCDDMA_CTRL[TH_FIFO_READY]) is left at its default value after
reset. Increasing the FIFO threshold size will reduce or
eliminate underflows. Setting the threshold size to 256 double
words or larger is recommended.

Above issue is described in section 2.1.3 of silicon errata
http://www.ti.com/lit/er/sprz313e/sprz313e.pdf

Signed-off-by: Rajashekhara, Sudhakar &lt;sudhakar.raj@ti.com&gt;
Signed-off-by: Manjunathappa, Prakash &lt;prakash.pm@ti.com&gt;
Signed-off-by: Florian Tobias Schandinat &lt;FlorianSchandinat@gmx.de&gt;
</content>
</entry>
<entry>
<title>Merge branch 'for-florian' of git://gitorious.org/linux-omap-dss2/linux into fbdev-next</title>
<updated>2012-07-25T08:55:46Z</updated>
<author>
<name>Florian Tobias Schandinat</name>
<email>FlorianSchandinat@gmx.de</email>
</author>
<published>2012-07-25T08:55:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d9053b487965042b9c849ce40c7f1fb7a0b84b39'/>
<id>urn:sha1:d9053b487965042b9c849ce40c7f1fb7a0b84b39</id>
<content type='text'>
Conflicts:
	drivers/video/omap2/dss/core.c
	drivers/video/omap2/dss/dispc.c
</content>
</entry>
<entry>
<title>sh_mobile_meram: Add direct MERAM allocation API</title>
<updated>2012-07-19T00:05:22Z</updated>
<author>
<name>Laurent Pinchart</name>
<email>laurent.pinchart@ideasonboard.com</email>
</author>
<published>2012-03-15T12:18:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=239921ec1d969e904676f444a92e6d68a928d98c'/>
<id>urn:sha1:239921ec1d969e904676f444a92e6d68a928d98c</id>
<content type='text'>
The API can be used to allocate and free MERAM blocks directly, without
going through ICBs.

Signed-off-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
</content>
</entry>
<entry>
<title>sh_mobile_meram: Use direct function calls for the public API</title>
<updated>2012-07-19T00:05:21Z</updated>
<author>
<name>Laurent Pinchart</name>
<email>laurent.pinchart@ideasonboard.com</email>
</author>
<published>2012-03-15T11:40:47Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=6e729b416b44296f5ed503b40ac58c2bffb43caf'/>
<id>urn:sha1:6e729b416b44296f5ed503b40ac58c2bffb43caf</id>
<content type='text'>
There's no reason to use abstract operation pointers to implement the
MERAM API. Replace them by direct function calls.

Signed-off-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
</content>
</entry>
<entry>
<title>sh_mobile_meram: Rename operations to cache_[alloc|free|update]</title>
<updated>2012-07-19T00:05:21Z</updated>
<author>
<name>Laurent Pinchart</name>
<email>laurent.pinchart@ideasonboard.com</email>
</author>
<published>2012-03-15T11:40:47Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=4a2371772146b30113c9c837eb32b64f18376c0d'/>
<id>urn:sha1:4a2371772146b30113c9c837eb32b64f18376c0d</id>
<content type='text'>
The MERAM operations meram_register, meram_unregister and meram_update
handle LCDC cache. In preparation for "raw" MERAM allocation, rename
them to more appropriate names.

Signed-off-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
</content>
</entry>
<entry>
<title>OMAPDSS: DSI: Fix HSYNC, VSYNC and DE polarities between DISPC and DSI</title>
<updated>2012-06-29T07:15:54Z</updated>
<author>
<name>Archit Taneja</name>
<email>archit@ti.com</email>
</author>
<published>2012-06-26T07:08:31Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=bd5a7b11a0bfd172b4cd6ef3e01e6beb1753c3f1'/>
<id>urn:sha1:bd5a7b11a0bfd172b4cd6ef3e01e6beb1753c3f1</id>
<content type='text'>
For DSI operation in videomode, DISPC logic levels for the signals HSYNC, VSYNC
and DE need to be specified to DSI via the fields VP_HSYNC_POL, VP_VSYNC_POL and
VP_DE_POL in DSI_CTRL registers.

This information is completely internal to DSS as logic levels for the above
signals hold no meaning on the DSI bus. Hence a DSI panel driver should be
totally oblivious of these fields.

Fix the logic levels/polarities in the DISPC and DSI registers to a default
value. This is done by overriding these fields in omap_video_timings struct
filled by the panel driver for DISPC, and use the equivalent default values
when programming DSI_CTRL registers. Also, remove the redundant polarity related
fields in omap_dss_dsi_videomode_data.

Signed-off-by: Archit Taneja &lt;archit@ti.com&gt;
</content>
</entry>
<entry>
<title>OMAPDSS: Add interlace parameter to omap_video_timings</title>
<updated>2012-06-29T07:15:52Z</updated>
<author>
<name>Archit Taneja</name>
<email>archit@ti.com</email>
</author>
<published>2012-06-28T05:45:51Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=23c8f88e8a140c8435658c369b26c7b60d8fe3c0'/>
<id>urn:sha1:23c8f88e8a140c8435658c369b26c7b60d8fe3c0</id>
<content type='text'>
Add a parameter called interlace which tells whether the timings are in
interlaced or progressive mode. This aligns the omap_video_timings struct with
the Xorg modeline configuration.

It also removes the hack needed to write to divide the manager height by 2 if
the connected interface is VENC.

Signed-off-by: Archit Taneja &lt;archit@ti.com&gt;
</content>
</entry>
<entry>
<title>OMAPDSS: Remove omap_panel_config enum from omap_dss_device</title>
<updated>2012-06-29T07:15:51Z</updated>
<author>
<name>Archit Taneja</name>
<email>archit@ti.com</email>
</author>
<published>2012-06-29T06:43:32Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=07fb51c6bda74210b57a06e6dc901a6b0f04c09a'/>
<id>urn:sha1:07fb51c6bda74210b57a06e6dc901a6b0f04c09a</id>
<content type='text'>
omap_panel_config contains fields which are finally written to DISPC_POL_FREQo
registers. These are now held by omap_video_timings and are set when the manager
timings are applied.

Remove the omap_panel_config enum, and remove all it's references from panel or
interface drivers.

Signed-off-by: Archit Taneja &lt;archit@ti.com&gt;
</content>
</entry>
<entry>
<title>OMAPDSS: Add some new fields to omap_video_timings</title>
<updated>2012-06-29T07:15:49Z</updated>
<author>
<name>Archit Taneja</name>
<email>archit@ti.com</email>
</author>
<published>2012-06-25T06:56:38Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=a8d5e41cef43bd740ca7c56ff316bdee30040a91'/>
<id>urn:sha1:a8d5e41cef43bd740ca7c56ff316bdee30040a91</id>
<content type='text'>
Some panel timing related fields are contained in omap_panel_config in the form
of flags. The fields are:

- Hsync logic level
- Vsync logic level
- Data driven on rising/falling edge of pixel clock
- Output enable/Data enable logic level
- HSYNC/VSYNC driven on rising/falling edge of pixel clock

Out of these parameters, Hsync and Vsync logic levels are a part of the timings
in the Xorg modeline configuration. So it makes sense to move the to
omap_video_timings. The rest aren't a part of modeline, but it still makes
sense to move these since they are related to panel timings.

These fields stored in omap_panel_config in dssdev are configured for LCD
panels, and the corresponding LCD managers in the DISPC_POL_FREQo registers.

Add the above fields in omap_video_timings. Represent their state via new enums.

Add these parameters to the omap_video_timings instances in the panel drivers.
Keep the corresponding IVS, IHS, IPC, IEO, RF and ONOFF flags in
omap_panel_config for now. The struct will be removed later.

Signed-off-by: Archit Taneja &lt;archit@ti.com&gt;
</content>
</entry>
<entry>
<title>OMAPDSS: Remove passive matrix LCD support (part 3)</title>
<updated>2012-06-29T07:15:46Z</updated>
<author>
<name>Archit Taneja</name>
<email>archit@ti.com</email>
</author>
<published>2012-06-21T04:15:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d21f43bc392911acf01b7f2090615df4ca09ac7d'/>
<id>urn:sha1:d21f43bc392911acf01b7f2090615df4ca09ac7d</id>
<content type='text'>
Remove omap_lcd_display_type enum

The enum omap_lcd_display_type is used to configure the lcd display type in
DISPC. Remove this enum and always set display type to TFT by creating function
dss_mgr_set_lcd_type_tft().

Signed-off-by: Archit Taneja &lt;archit@ti.com&gt;
</content>
</entry>
</feed>
