intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Manasi Navare <manasi.d.navare@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/6] Remaining patches to enable Transcoder Port Sync for tiled displays
Date: Tue, 10 Sep 2019 12:29:19 +0300	[thread overview]
Message-ID: <87pnk81ouo.fsf@intel.com> (raw)
In-Reply-To: <20190909034325.20006-1-manasi.d.navare@intel.com>

On Sun, 08 Sep 2019, Manasi Navare <manasi.d.navare@intel.com> wrote:
> This patch series addresses all review comments and now the enable and
> disable paths follow the method of obtaining slave states from master
> and updating master-slaves in correct order during master modeset.

Main high level question: what does it take to enable this on gen9+?

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-09-10  9:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09  3:43 [PATCH 0/6] Remaining patches to enable Transcoder Port Sync for tiled displays Manasi Navare
2019-09-09  3:43 ` [PATCH 1/6] drm/i915/display/icl: Save Master transcoder in slave's crtc_state for Transcoder Port Sync Manasi Navare
2019-09-17 14:51   ` Maarten Lankhorst
2019-09-09  3:43 ` [PATCH 2/6] drm/i915/display/icl: Enable TRANSCODER PORT SYNC for tiled displays across separate ports Manasi Navare
2019-09-17 14:52   ` Maarten Lankhorst
2019-09-17 14:52   ` Maarten Lankhorst
2019-09-17 16:55     ` Manasi Navare
2019-09-09  3:43 ` [PATCH 3/6] drm/i915/display/icl: HW state readout for transcoder port sync config Manasi Navare
2019-09-17 14:53   ` Maarten Lankhorst
2019-09-09  3:43 ` [PATCH 4/6] drm/i915/display/icl: Enable master-slaves in trans port sync Manasi Navare
2019-09-09 15:52   ` [PATCH v2 " Manasi Navare
2019-09-17 15:01     ` Maarten Lankhorst
2019-09-09  3:43 ` [PATCH 5/6] drm/i915/display/icl: Disable transcoder port sync as part of crtc_disable() sequence Manasi Navare
2019-09-17 15:04   ` Maarten Lankhorst
2019-09-17 16:37     ` Manasi Navare
2019-09-18  8:51       ` Maarten Lankhorst
2019-09-18 15:16         ` Manasi Navare
2019-09-09  3:43 ` [PATCH 6/6] drm/i915/display/icl: In port sync mode disable slaves first then master Manasi Navare
2019-09-09 15:52   ` [PATCH v2 " Manasi Navare
2019-09-17 15:05     ` Maarten Lankhorst
2019-09-09  4:10 ` ✗ Fi.CI.CHECKPATCH: warning for Remaining patches to enable Transcoder Port Sync for tiled displays Patchwork
2019-09-09  4:11 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-09-09 19:44 ` ✗ Fi.CI.SPARSE: warning for Remaining patches to enable Transcoder Port Sync for tiled displays (rev3) Patchwork
2019-09-09 20:06 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-09-10  9:29 ` Jani Nikula [this message]
2019-09-10 18:07   ` [PATCH 0/6] Remaining patches to enable Transcoder Port Sync for tiled displays Manasi Navare
2019-09-10 21:19     ` Manasi Navare
2019-09-11  9:08       ` Jani Nikula
2019-09-11 16:27         ` Manasi Navare
2019-09-12  6:42           ` Jani Nikula
2019-09-12 18:35             ` Manasi Navare

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pnk81ouo.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=manasi.d.navare@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).