Skip to contentSkip to conversation

ARM: DaVinci: DM646x Video: DM646x display driver

PATCH Superseded Chaithrika U S 2 participants 2 messages Apr 8, 2009 – Apr 13, 2009 Media (V4L/DVB)

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

v2 cover ARM: DaVinci: DM646x Video: DM646x display driver

Display driver for TI DM646x EVM

These patches add the display driver support for TI DM646x EVM. This patch set has been tested for basic display functionality for Composite and Component outputs.

In this version of the patches, the review comments got for the earlier version have been incorporated. The standard information(timings) has been moved to the display driver. The display driver has been modified accordingly. Also simplified the code by removing the redundant vpif_stdinfo data structure.

Patch 1: Display device platform and board setup Patch 2: VPIF driver
Patch 3: DM646x display driver
Patch 4: Makefile and config files modifications for Display

Some of the features like the HBI/VBI support are not yet implemented. Also there are some known issues in the code implementation like fine tuning to be done to TRY_FMT ioctl.The USERPTR usage has not been tested extensively.

-Chaithrika

#1 lore raw
Quoted 21 lines · On Wednesday 08 April 2009 13:17:56 Chaithrika U S wrote:

Display driver for TI DM646x EVM

These patches add the display driver support for TI DM646x EVM. This patch set has been tested for basic display functionality for Composite and Component outputs.

In this version of the patches, the review comments got for the earlier version have been incorporated. The standard information(timings) has been moved to the display driver. The display driver has been modified accordingly. Also simplified the code by removing the redundant vpif_stdinfo data structure.

Patch 1: Display device platform and board setup Patch 2: VPIF driver
Patch 3: DM646x display driver
Patch 4: Makefile and config files modifications for Display

Quoted 4 lines

Some of the features like the HBI/VBI support are not yet implemented. Also there are some known issues in the code implementation like fine tuning to be done to TRY_FMT ioctl.The USERPTR usage has not been tested extensively.

Time permitting I'll review this during the weekend. During a very superficial scan I saw a few things that could be improved, but I think it only needs one more cycle before it can be merged. It looks much, much better now!

Regards,

Hans

Quoted 8 lines

-Chaithrika

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 1 line
Hans Verkuil - video4linux developer - sponsored by TANDBERG