1. 30 9月, 2011 4 次提交
    • T
      OMAP: DSS2: Add GLOBAL_ALPHA & PRE_MULT_ALPHA to ovl caps · f6dc8150
      Tomi Valkeinen 提交于
      Add OMAP_DSS_OVL_CAP_GLOBAL_ALPHA and OMAP_DSS_OVL_CAP_PRE_MULT_ALPHA to
      overlay capabilities. Use these instead of FEAT_GLOBAL_ALPHA,
      FEAT_GLOBAL_ALPHA_VID1 and FEAT_PRE_MULT_ALPHA in code.
      
      Remove FEAT_GLOBAL_ALPHA_VID1 and FEAT_PRE_MULT_ALPHA which are no
      longer used. FEAT_GLOBAL_ALPHA is still used to decide if the HW has
      global alpha register.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Acked-by: NArchit Taneja <archit@ti.com>
      f6dc8150
    • T
      OMAP: DSS2: Remove support for non-DISPC overlays · 4a9e78ab
      Tomi Valkeinen 提交于
      Remove support for non-DISPC overlays and overlay managers.
      
      The support to possibly have non-DISPC overlays and managers was made to
      make it possible to use CPU and/or sDMA to update RFBI or DSI command
      mode displays. It is ok to remove the support, because:
      
      - No one has used the feature.
      - Display update without DISPC is very slow, so it is debatable if the
        update would even be usable.
      - Removal cleans up code.
      - If such a feature is needed later, it is better implemented outside
        omapdss driver.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Acked-by: NArchit Taneja <archit@ti.com>
      4a9e78ab
    • T
      OMAP: DSS2: Handle manager change in apply · 8fa8031c
      Tomi Valkeinen 提交于
      Currently when changing the manager of an overlay, set_manager() directly
      calls dispc to set the overlay's destination.
      
      Change this to be more in line with other overlay configurations, and
      this will also remove the need to have dispc clocks enabled when calling
      set_manager().
      
      A new field is added to overlay struct, "manager_changed". This is
      similar to "display_changed" field in manager struct, and is used to
      inform apply that the manager has changed and thus write to the
      registers is needed.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      8fa8031c
    • T
      OMAP: DSS2: DSI: Improve dsi_mux_pads parameters · 5bc416cb
      Tomi Valkeinen 提交于
      dsi_mux_pads() needs to know about the DSI HW module and the DSI lanes
      used. Split the function into two, enable and disable, which take
      necessary arguments, and add empty implementations for both.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      5bc416cb
  2. 14 9月, 2011 1 次提交
  3. 25 7月, 2011 2 次提交
  4. 01 7月, 2011 3 次提交
  5. 23 5月, 2011 4 次提交
  6. 16 5月, 2011 1 次提交
    • A
      OMAP: DSS2: DSI: Get number of DSI data lanes using DSI_GNQ register · 75d7247c
      Archit Taneja 提交于
      On OMAP3, the DSI module has 2 data lanes. On OMAP4, DSI1 has 4 data lanes
      and DSI2 has 2 data lanes. Introduce function dsi_get_num_data_lanes() which
      returns the number of data lanes on the dsi interface, introduce function
      dsi_get_num_data_lanes_dssdev() which returns the number of data lanes used by
      the omap_dss_device connected to the lanes.
      
      Use the DSI_GNQ register on OMAP4 to get the number of data lanes, modify
      dsi.c to use the number of lanes and the extra data lanes on DSI1.
      Signed-off-by: NArchit Taneja <archit@ti.com>
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      75d7247c
  7. 13 5月, 2011 5 次提交
  8. 11 5月, 2011 14 次提交
  9. 06 4月, 2011 1 次提交
  10. 31 3月, 2011 1 次提交
  11. 22 3月, 2011 1 次提交
  12. 16 3月, 2011 1 次提交
    • D
      fbdev: sh_mobile_lcdc: Add YUV framebuffer support · 53b50314
      Damian Hobson-Garcia 提交于
      Supports YCbCr420sp, YCbCr422sp, and YCbCr44sp, formats
      (bpp = 12, 16, and 24) respectively.
      
      When double-buffering both Y planes appear before the C planes (Y-Y-C-C),
      as opposed to  Y-C-Y-C.
      
      Set .nonstd in struct sh_mobile_lcdc_chan_cfg to enable YUV mode, and use
      .bpp to distiguish between the 3 modes.
      The value of .nonstd is copied to bits 16-31 of LDDFR in the LCDC and
      should be set accordingly.
      .nonstd must be set to 0 for RGB mode.
      
      Due to the encoding of YUV data, the framebuffer will clear to green
      instead of black.
      
      In YUV 420 mode, panning is only possible in 2 line increments.
      Additionally in YUV 420 mode the vertical resolution of the framebuffer
      must be an even number.
      Signed-off-by: NDamian Hobson-Garcia <dhobsong@igel.co.jp>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      53b50314
  13. 10 3月, 2011 1 次提交
  14. 06 1月, 2011 1 次提交