From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Subject: Re: [PATCH v2] drm/i915/psr: Execute the default PSR code path when setting i915_edp_psr_debug
Date: Thu, 31 Jan 2019 10:34:11 +0100 [thread overview]
Message-ID: <992008a3-0cc1-9755-ebb2-dded629c28de@linux.intel.com> (raw)
In-Reply-To: <20190131005821.24662-1-jose.souza@intel.com>
Op 31-01-2019 om 01:58 schreef José Roberto de Souza:
> Changing the i915_edp_psr_debug was enabling, disabling or switching
> PSR version by directly calling intel_psr_disable_locked() and
> intel_psr_enable_locked(), what is not the default PSR path that will
> be executed by real users.
>
> So lets force a fastset in the PSR CRTC to trigger a pipe update and
> stress the default code path.
>
> Recently a bug was found when switching from PSR2 to PSR1 while
> enable_psr kernel parameter was set to the default parameter, this
> changes fix it and also fixes the bug linked bellow were DRRS was
> left enabled together with PSR when enabling PSR from debugfs.
>
> v2: Handling missing case: disabled to PSR1
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108341
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> ---
>
> Should I add IGT tests to test every state switch combination?
Should probably be done for DRRS as well. We should be able to stop having to set has_drrs and has_psr unconditionally then. :)
Could be a separate followup patch.
The complete duplication of the whole atomic state is overkill and should be avoided, just use
if (!intel_crtc_has_type(to_intel_crtc_state(crtc->state), INTEL_OUTPUT_EDP)
continue;
crtc_state = drm_atomic_get_old_crtc_state(...)
....
And then do a normal commit. We will add all planes and connectors as needed.
With that fixed:
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-01-31 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 0:58 [PATCH v2] drm/i915/psr: Execute the default PSR code path when setting i915_edp_psr_debug José Roberto de Souza
2019-01-31 1:50 ` ✓ Fi.CI.BAT: success for drm/i915/psr: Execute the default PSR code path when setting i915_edp_psr_debug (rev2) Patchwork
2019-01-31 9:34 ` Maarten Lankhorst [this message]
2019-02-01 2:03 ` [PATCH v2] drm/i915/psr: Execute the default PSR code path when setting i915_edp_psr_debug Souza, Jose
2019-01-31 12:46 ` ✓ Fi.CI.IGT: success for drm/i915/psr: Execute the default PSR code path when setting i915_edp_psr_debug (rev2) Patchwork
2019-01-31 23:10 ` [PATCH v2] drm/i915/psr: Execute the default PSR code path when setting i915_edp_psr_debug Dhinakaran Pandiyan
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=992008a3-0cc1-9755-ebb2-dded629c28de@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@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