1. 30 7月, 2009 1 次提交
    • Z
      drm/I915: Fix offset to DVO timings in LVDS data · cdaa052b
      Zhao Yakui 提交于
      Now the DVO timing in LVDS data entry is obtained by using the
      following step:
          a. get the entry size for every LVDS panel data
          b. Get the LVDS fp entry for the preferred panel type
          c. get the DVO timing by using entry->dvo_timing
      
      In our driver the entry->dvo_timing is related with the size of
      lvds_fp_timing. For example: the size is 46.
      
      But it seems that the size of lvds_fp_timing varies on the differnt
      platform. In such case we will get the incorrect DVO timing entry
      because of the incorrect DVO offset in LVDS panel data entry.
      This also removes a hack on new IGDNG to get proper DVO timing.
      
      Calculate the DVO timing offset in LVDS data entry to get the DVO timing
          a. get the DVO timing offset in the LVDS fp data entry by using the
      pointer definition in LVDS data ptr
          b. get the LVDS data entry
          c. get the DVO timing by adding the DVO timing offset to data entry
      
      https://bugs.freedesktop.org/show_bug.cgi?id=22787Signed-off-by: NZhao Yakui <yakui.zhao@intel.com>
      Tested-by: NZhenyu Wang <zhenyuw@linux.intel.com>
      Acked-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      Signed-off-by: NEric Anholt <eric@anholt.net>
      cdaa052b
  2. 23 7月, 2009 1 次提交
  3. 17 7月, 2009 2 次提交
  4. 15 7月, 2009 1 次提交
    • J
      drm/i915: FIFO watermark calculation fixes · dff33cfc
      Jesse Barnes 提交于
      I discovered several bugs in the FIFO code that was recently applied.
      Some of them fell into the "how did this ever work" category, since in
      some cases we were using the wrong FIFO size values, and the
      calculations ended up being way off.
      
      This patch fixes all the bugs I found, and works well on my GM45, 915GM
      and 855GM test machines; but as usual with these sorts of patches
      broader testing is definitely requested (in particular this patch
      affects 830, 845 and 865 for which I don't have test hardware).
      
      Overall, the patch clarifies the watermark calculation function by
      adding some comments and debug info, and making the variable names a
      bit clearer.  The "get FIFO size" portion of the code has also been
      corrected, so we should be able to properly detect the FIFO allocations
      for each pipe, for use in the watermark calculation.
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      Signed-off-by: NEric Anholt <eric@anholt.net>
      dff33cfc
  5. 14 7月, 2009 4 次提交
  6. 13 7月, 2009 5 次提交
  7. 12 7月, 2009 3 次提交
  8. 11 7月, 2009 23 次提交