1. 18 4月, 2020 1 次提交
  2. 04 4月, 2020 1 次提交
  3. 27 2月, 2020 1 次提交
  4. 26 2月, 2020 2 次提交
  5. 19 2月, 2020 1 次提交
  6. 31 1月, 2020 2 次提交
  7. 07 1月, 2020 1 次提交
  8. 29 12月, 2019 2 次提交
  9. 23 12月, 2019 1 次提交
  10. 18 12月, 2019 1 次提交
  11. 11 12月, 2019 1 次提交
  12. 09 12月, 2019 1 次提交
  13. 03 12月, 2019 1 次提交
  14. 11 11月, 2019 1 次提交
  15. 07 11月, 2019 1 次提交
  16. 05 11月, 2019 1 次提交
  17. 04 11月, 2019 1 次提交
  18. 01 11月, 2019 1 次提交
  19. 31 10月, 2019 1 次提交
  20. 25 10月, 2019 1 次提交
  21. 19 10月, 2019 2 次提交
    • M
      drm/i915/display/icl: Enable master-slaves in trans port sync · eadf6f91
      Manasi Navare 提交于
      As per the display enable sequence, we need to follow the enable sequence
      for slaves first with DP_TP_CTL set to Idle and configure the transcoder
      port sync register to select the corersponding master, then follow the
      enable sequence for master leaving DP_TP_CTL to idle.
      At this point the transcoder port sync mode is configured and enabled
      and the Vblanks of both ports are synchronized so then set DP_TP_CTL
      for the slave and master to Normal and do post crtc enable updates.
      
      v11:
      * Rebase (Manasi)
      v10:
      * in trans sync mode, dont stop link train for tgl (Manasi)
      v9:
      Remove update_scanline_offset to rebase on Maarten's patch (Manasi)
      v8:
      * Rebase on Maarten's patches (Manasi)
      v7:
      * Use ffs(slaves) to get slave crtc (Ville)
      v6:
      * Modeset implies active_changed, remove one condition (Maarten)
      v5:
      * Fix checkpatch warning (Manasi)
      v4:
      * Reuse skl_commit_modeset_enables() hook (Maarten)
      * Obtain slave crtc and states from master (Maarten)
      v3:
      * Rebase on drm-tip (Manasi)
      v2:
      * Create a icl_update_crtcs hook (Maarten, Danvet)
      * This sequence only for CRTCs in trans port sync mode (Maarten)
      
      Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
      Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
      Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Cc: Matt Roper <matthew.d.roper@intel.com>
      Signed-off-by: NManasi Navare <manasi.d.navare@intel.com>
      Reviewed-by: NMaarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20191018172725.1338-4-manasi.d.navare@intel.com
      eadf6f91
    • M
      drm/i915/display/icl: Save Master transcoder in slave's crtc_state for Transcoder Port Sync · bfb926e3
      Manasi Navare 提交于
      In case of tiled displays when the two tiles are sent across two CRTCs
      over two separate DP SST connectors, we need a mechanism to synchronize
      the two CRTCs and their corresponding transcoders.
      So use the master-slave mode where there is one master corresponding
      to last horizontal and vertical tile that needs to be genlocked with
      all other slave tiles.
      This patch identifies saves the master transcoder in all the slave
      CRTC states. This is needed to select the master CRTC/transcoder
      while configuring transcoder port sync for the corresponding slaves.
      
      v6:
      Rebase (manasi)
      v5:
      * Address Ville's comments
      * Just pass crtc_state, no need to check GEN (Ville)
      v4:
      * Rebase
      v3:
      * Use master_tramscoder instead of master_crtc for valid
      HW state readouts (Ville)
      v2:
      * Move this to intel_mode_set_pipe_config(Jani N, Ville)
      * Use slave_bitmask to save associated slaves in master crtc state (Ville)
      
      Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
      Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
      Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Cc: Matt Roper <matthew.d.roper@intel.com>
      Signed-off-by: NManasi Navare <manasi.d.navare@intel.com>
      Reviewed-by: NMaarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20191018172725.1338-1-manasi.d.navare@intel.com
      bfb926e3
  22. 17 10月, 2019 1 次提交
  23. 15 10月, 2019 1 次提交
  24. 10 10月, 2019 2 次提交
  25. 03 10月, 2019 1 次提交
    • M
      drm/i915/dp: Fix dsc bpp calculations, v5. · cffb4c3e
      Maarten Lankhorst 提交于
      There was a integer wraparound when mode_clock became too high,
      and we didn't correct for the FEC overhead factor when dividing,
      with the calculations breaking at HBR3.
      
      As a result our calculated bpp was way too high, and the link width
      limitation never came into effect.
      
      Print out the resulting bpp calcululations as a sanity check, just
      in case we ever have to debug it later on again.
      
      We also used the wrong factor for FEC. While bspec mentions 2.4%,
      all the calculations use 1/0.972261, and the same ratio should be
      applied to data M/N as well, so use it there when FEC is enabled.
      
      This fixes the FIFO underrun we are seeing with FEC enabled.
      
      Changes since v2:
      - Handle fec_enable in intel_link_compute_m_n, so only data M/N is adjusted. (Ville)
      - Fix initial hardware readout for FEC. (Ville)
      Changes since v3:
      - Remove bogus fec_to_mode_clock. (Ville)
      Changes since v4:
      - Use the correct register for icl. (Ville)
      - Split hw readout to a separate patch.
      Signed-off-by: NMaarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Fixes: d9218c8f ("drm/i915/dp: Add helpers for Compressed BPP and Slice Count for DSC")
      Cc: <stable@vger.kernel.org> # v5.0+
      Cc: Manasi Navare <manasi.d.navare@intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20190925082110.17439-1-maarten.lankhorst@linux.intel.comReviewed-by: NVille Syrjälä <ville.syrjala@linux.intel.com>
      (cherry picked from commit ed06efb8)
      Signed-off-by: NRodrigo Vivi <rodrigo.vivi@intel.com>
      cffb4c3e
  26. 02 10月, 2019 1 次提交
  27. 25 9月, 2019 1 次提交
    • M
      drm/i915/dp: Fix dsc bpp calculations, v5. · ed06efb8
      Maarten Lankhorst 提交于
      There was a integer wraparound when mode_clock became too high,
      and we didn't correct for the FEC overhead factor when dividing,
      with the calculations breaking at HBR3.
      
      As a result our calculated bpp was way too high, and the link width
      limitation never came into effect.
      
      Print out the resulting bpp calcululations as a sanity check, just
      in case we ever have to debug it later on again.
      
      We also used the wrong factor for FEC. While bspec mentions 2.4%,
      all the calculations use 1/0.972261, and the same ratio should be
      applied to data M/N as well, so use it there when FEC is enabled.
      
      This fixes the FIFO underrun we are seeing with FEC enabled.
      
      Changes since v2:
      - Handle fec_enable in intel_link_compute_m_n, so only data M/N is adjusted. (Ville)
      - Fix initial hardware readout for FEC. (Ville)
      Changes since v3:
      - Remove bogus fec_to_mode_clock. (Ville)
      Changes since v4:
      - Use the correct register for icl. (Ville)
      - Split hw readout to a separate patch.
      Signed-off-by: NMaarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Fixes: d9218c8f ("drm/i915/dp: Add helpers for Compressed BPP and Slice Count for DSC")
      Cc: <stable@vger.kernel.org> # v5.0+
      Cc: Manasi Navare <manasi.d.navare@intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20190925082110.17439-1-maarten.lankhorst@linux.intel.comReviewed-by: NVille Syrjälä <ville.syrjala@linux.intel.com>
      ed06efb8
  28. 23 9月, 2019 2 次提交
  29. 20 9月, 2019 1 次提交
    • V
      drm/i915: Don't advertise modes that exceed the max plane size · 2d20411e
      Ville Syrjälä 提交于
      Modern platforms allow the transcoders hdisplay/vdisplay to exceed the
      planes' max resolution. This has the nasty implication that modes on the
      connectors' mode list may not be usable when the user asks for a
      fullscreen plane. Seeing as that is the most common use case it seems
      prudent to filter out modes that don't allow for fullscreen planes to
      be enabled.
      
      Let's do that in the connetor .mode_valid() hook so that normally
      such modes are kept hidden but the user is still able to forcibly
      specify such a mode if they know they don't need fullscreen planes.
      
      This is in line with ealier policies regarding certain clock limits.
      The idea is to prevent the casual user from encountering a mode that
      would fail under typical conditions, but allow the expert user to
      force things if they so wish.
      
      Maybe in the future we should consider automagically using two
      planes when one can't cover the entire screen? Wouldn't be a
      great match for the current uapi with explicit planes though,
      but I guess no worse than using two pipes (which we apparently
      have to in the future anyway). Either that or we'd have to
      teach userspace to do it for us.
      
      v2: Fix icl+ max plane heigth (Manasi)
      
      Cc: Manasi Navare <manasi.d.navare@intel.com>
      Cc: Leho Kraav <leho@kraav.com>
      Cc: Sean Paul <sean@poorly.run>
      Cc: José Roberto de Souza <jose.souza@intel.com>
      Reviewed-by: NMaarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Reviewed-by: NManasi Navare <manasi.d.navare@intel.com>
      Signed-off-by: NVille Syrjälä <ville.syrjala@linux.intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20190918150707.32420-1-ville.syrjala@linux.intel.com
      2d20411e
  30. 16 9月, 2019 1 次提交
  31. 12 9月, 2019 1 次提交
  32. 30 8月, 2019 1 次提交
  33. 27 8月, 2019 1 次提交
  34. 09 8月, 2019 1 次提交