Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 161
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 25 1月, 2012 4 次提交
    • T
      OMAPDSS: DISPC: print fifo threshold values in bytes · 3cb5d966
      由 Tomi Valkeinen 提交于 
      Fifo thresholds are calculated using bytes, but the debug print prints
values in buffer units. Change the prints to use bytes to be in line
with the calculations, and also to print in the same units on all OMAPs.
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      3cb5d966
    • T
      OMAPDSS: APPLY: add fifo-merge support · 1d71f42b
      由 Tomi Valkeinen 提交于 
      Add fifo-merge support. This is done mainly in four functions:
mgr_enable/disable and ovl_enable/disable. These are the functions where
overlays are taken into and out of active use.

The process to enable and disable fifo-merge is not simple. We need to
do it in steps, waiting in between for certain settings to be taken into
use, and continuing after that. The reason for this is that fifo-merge
is a common thing for all managers/overlays, and its use must be
synchronized.

As an example, when we disable an overlay, we first set the overlay as
disabled, then wait until the overlay is actually disabled in the HW,
and only after that we may re-configure the fifos, possibly taking
fifo-merge into use.
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      1d71f42b
    • T
      OMAPDSS: APPLY: add fifo merge support funcs · fb011974
      由 Tomi Valkeinen 提交于 
      Add mechanism to set/unset the DISPC fifo-merge:

Add new fields to dss_data, fifo_merge and fifo_merge_dirty. These are
similar to the other info/dirty flags in ovl_priv_data and ovl_mgr_data,
but fifo merge is a common attribute to all managers and thus outside
the ovl_mgr_data.

The fifo-merge field is used in the dss_write_regs_common, which handles
writing the register.

dss_apply_fifo_merge() can be used to set/unset the fifo merge field in
the dss_data.
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      fb011974
    • T
      OMAPDSS: FEAT: Add FIFO_MERGE feature · e6b0f884
      由 Tomi Valkeinen 提交于 
      Add feature flag for fifo merge. OMAP2 doesn't contain fifo merge, later
OMAPs do.

dispc_enable_fifomerge() checks for the flag when called, and gives a
WARN if fifo merge is being enabled when it is not supported.
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      e6b0f884
  3. 13 1月, 2012 4 次提交
  5. 12 1月, 2012 1 次提交
  7. 11 1月, 2012 7 次提交
  9. 05 1月, 2012 7 次提交
  11. 04 1月, 2012 7 次提交
  13. 03 1月, 2012 8 次提交
  15. 02 1月, 2012 2 次提交
    • A
      misc latin1 to utf8 conversions · d36b6910
      由 Al Viro 提交于 
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      d36b6910
    • C
      OMAPDSS: DISPC: Update Scaling Clock Logic · 7282f1b7
      由 Chandrabhanu Mahapatra 提交于 
      Clock requirements for scaling in OMAP2, OMAP3 and OMAP4 are different. In
OMAP2 and OMAP3 the required clock rate is a function of pixel clock, vertical
downscale ratio and horizontal downscale ratio whereas in OMAP4 it is a
function of pixel clock and horizontal downscale ratio only. Selection of 3-tap
vs 5-tap coefficients depends on clock rate line buffer width in OMAP3 whereas
in OMAP4 it is independent of clock rate and line buffer width. In OMAP2 3-tap
for vertical and 5-tap for horizontal scaling is used. In OMAP4 5-tap is used
both for horizontal and vertical scaling for better performance. Also, the
number and width of line buffers differs in OMAP3 and OMAP4.

So, clock functions have been fined tuned for OMAP3 and support has been added
added for OMAP4. This code has been tested on OMAP2, OMAP3 and OMAP4, and
scaling issues due to clock errors have been resolved.
Signed-off-by: NChandrabhanu Mahapatra <cmahapatra@ti.com>
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      7282f1b7