On Wednesday 09 May 2012 05:08 AM, Russ Dill wrote:
On Mon, May 7, 2012 at 4:21 AM, Archit Taneja<[email protected]>  wrote:

The first patch in this series is a follow up on the previously posted
series
'OMAPDSS: APPLY: Treat overlay manager timings as shadow registers'. It is
required for HDMI and DPI interfaces to work properly, it ensures manager
timings are applied in the set_timing() ops for these interfaces.

The next 3 patches remove some unnecessary usage of omap_dss_device
pointer in
DISPC and APPLY.

The last 2 patches are miscellaneous fixes and are self explanatory.

Reference tree containing this series:

git://gitorious.org/~boddob/linux-omap-dss2/archit-dss2-clone.git
mgr_timing_and_fixes

Tested on OMAP4 SDP.

Archit Taneja (6):
  OMAPDSS: DPI/HDMI: Apply manager timings even if panel is disabled
  OMAPDSS: APPLY: Remove an unnecessary omap_dss_device pointer
  OMAPDSS: DISPC: Remove omap_dss_device pointer usage from
    dispc_mgr_pclk_rate()
  OMAPDSS: DISPC: Remove usage of dispc_mgr_get_device()
  OMAPDSS: Fix DSI_FCLK clock source selection
  OMAPDSS: DISPC: Remove Fake VSYNC support

  drivers/video/omap2/dss/Kconfig |    9 ------
  drivers/video/omap2/dss/apply.c |    3 --
  drivers/video/omap2/dss/dispc.c |   61
+++++++++++++-------------------------
  drivers/video/omap2/dss/dpi.c   |    2 +
  drivers/video/omap2/dss/dsi.c   |    4 --
  drivers/video/omap2/dss/dss.c   |    5 ++-
  drivers/video/omap2/dss/dss.h   |    1 -
  drivers/video/omap2/dss/hdmi.c  |    2 +
  8 files changed, 28 insertions(+), 59 deletions(-)

I did a build and boot of each one of the patches on the
mgr_timing_and_fixes branch including these on:

Beagleboard-xM rev C1
Beagleboard rev B4
Mistral AM37x-EVM
Zoom AM3517 EVM
Zoom AM1808 EVM

Thanks! I'll be posting out a newer version of the series with some minor changes. But the content should be more or less the same.

Thanks,
Archit


Tested-by: [email protected]


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

Reply via email to