1. 27 11月, 2012 9 次提交
  2. 20 11月, 2012 2 次提交
  3. 12 11月, 2012 3 次提交
    • A
      OMAPDSS: DISPC: Use output width and height to calculate row/pix inc for writeback · 6be0d73e
      Archit Taneja 提交于
      When calculating row and pixel increments for graphics and video pipes, we need
      to consider the dimensions of the input frame to know how to read from the
      buffer. Hence, we need to calculate these parameters from the input to the
      pipeline.
      
      For writeback, the row and pixel increments need to be calculated based on the
      output of the writeback pipeline, i.e, the dimensions of the frame after
      scaling. Ensure that dispc driver uses values of out_width and out_height when
      calling calc_dma/calc_tiler_rotation_offset.
      
      For graphics and video pipes, the original code passed the original height as
      frame_height to calc_dma_rotation_offset, and not the predecimated height. This
      is left as it is for now. We need to figure out why pre decimated height isn't
      needed.
      Signed-off-by: NArchit Taneja <archit@ti.com>
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      6be0d73e
    • A
      OMAPDSS: DISPC: Don't allow predecimation for writeback · 1c031441
      Archit Taneja 提交于
      Since writeback writes to a buffer instead of reading from one, predecimation
      doesn't make sense for it. Configure the width and height predecimation limits
      to 1 if the plane is writeback.
      Signed-off-by: NArchit Taneja <archit@ti.com>
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      1c031441
    • A
      OMAPDSS: DISPC: Fix calc_scaling_44xx() bugs for writeback pipeline · 5d501085
      Archit Taneja 提交于
      dispc_ovl_calc_scaling_44xx() doesn't work correctly for writeback. There are
      two issues with it:
      
      - the function tries to calculate pixel clock for the input plane using
        dispc_plane_pclk_rate(), calling this with writeback as input plane results in
        a BUG(), this function shouldn't be called for writeback at all. Fix this by
        calculating pixel clock only when we are not in mem to mem mode.
      
      - the maximum input_width is the product of the downscale ratio supported and
        the and the given output_width. This was calculated incorrectly by dividing
        output_width with maxdownscale. Fix this.
      Signed-off-by: NArchit Taneja <archit@ti.com>
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      5d501085
  4. 07 11月, 2012 1 次提交
  5. 06 11月, 2012 1 次提交
  6. 05 11月, 2012 1 次提交
  7. 29 10月, 2012 7 次提交
  8. 24 10月, 2012 2 次提交
  9. 18 10月, 2012 6 次提交
  10. 17 10月, 2012 3 次提交
  11. 16 10月, 2012 1 次提交
  12. 12 10月, 2012 2 次提交
  13. 26 9月, 2012 2 次提交
    • A
      OMAPDSS: DISPC: Configure color conversion coefficients for writeback · 6e5264b0
      Archit Taneja 提交于
      Writeback pipeline receives RGB data from one of the overlays or one of the
      overlay managers. If the target color mode is YUV422 or NV12, we need to convert
      the RGB pixels to YUV. The scaler in WB then converts it to the target color
      mode.
      
      Hence, the color conversion coefficients that need to be programmed are the ones
      which convert a RGB24 pixel to YUV444. Program these coefficients for writeback
      pipeline.
      
      Rearrange the code a bit to configure different coefficients for overlays and
      writeback.
      Signed-off-by: NArchit Taneja <archit@ti.com>
      6e5264b0
    • A
      OMAPDSS: DISPC: Add manager like functions for writeback · 0b23e5b8
      Archit Taneja 提交于
      Add functions to enable writeback, and set/check state of GO bit. These bits are
      identical in behaviour with the corresponding overlay manager bits. Configure
      them in a similar way to mgr_enable() and mgr_go_* functions. Add a helper to
      get the FRAMEDONE irq corresponding to writeback.
      Signed-off-by: NArchit Taneja <archit@ti.com>
      0b23e5b8