public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: David Weinehall <david.weinehall@linux.intel.com>
To: Jim Bride <jim.bride@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v4 RESEND 0/4] Kernel PSR Fix-ups
Date: Tue, 25 Jul 2017 20:13:03 +0300	[thread overview]
Message-ID: <20170725171303.qepeomjus7hmapii@boom> (raw)
In-Reply-To: <1501001291-2708-1-git-send-email-jim.bride@linux.intel.com>

On Tue, Jul 25, 2017 at 09:48:07AM -0700, Jim Bride wrote:
> These patches, along with an upcoming series for IGT, enable our
> PSR IGT tests to run reliably once again on HSW, BDW, and SKL.
> The first change enables us to run the PSR tests on some RVP platforms
> whose panels have too slow of a setup time when running in their
> preferred mode.  The second fixes a minor problem with the way that
> we were initializing SRD_CTL that caused us to clobber a bit that we
> are not supposed to change in that register on SKL and KBL.  The third
> change re-introduces some changes to our link training code to be less
> aggressive about changing link state for eDP, because PSR depends on
> the link state being the same at PSR exit as it was at PSR entry.
> The fourth change greatly increases the reliability of reading the
> sink CRC generated by the eDP panel.
> 
> v2 Highlights:
>    * Rebased to current drm-tip
>    * Greatly reduced looping around trying to read sink CRC (Jani)
>    * Reduce amount of changes in the sink CRC patch (Jani)
>    * Field-wise init of EDP_PSR_MAX_SLEEP_TIME (Rodrigo)
>    * Minor commit message / cover letter tweaks
> 
> v3:
>    * Re-ordered patches to put reviewed patches first.
>    * Rebased to current drm-tip
> 
> v4: 
>    * Addressed review feedback (see patches for details)
>    * Rebase

Is this a pure resend, or does it include any fixes on top of earlier
versions? As mentioned elsewhere I experienced issues with both your
previous patch series and the two before that one.

I'll run a new testrun with this series just in case (it might be that
the issues I noticed were caused by bad interaction with some other
component).


Kind regards, David Weinehall
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2017-07-25 17:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 16:48 [PATCH v4 RESEND 0/4] Kernel PSR Fix-ups Jim Bride
2017-07-25 16:48 ` [PATCH v4 RESEND 1/4] drm/i915/psr: Clean-up intel_enable_source_psr1() Jim Bride
2017-08-03 18:08   ` Rodrigo Vivi
2017-07-25 16:48 ` [PATCH v4 RESEND 2/4] drm/i915/psr: Account for sink CRC raciness on some panels Jim Bride
2017-07-25 16:48 ` [PATCH v4 RESEND 3/4] drm/i915/edp: Be less aggressive about changing link config on eDP Jim Bride
2017-08-03 18:10   ` Rodrigo Vivi
2017-07-25 16:48 ` [PATCH v4 RESEND 4/4] drm/i915/edp: Allow alternate fixed mode for eDP if available Jim Bride
2017-07-28 19:22   ` [PATCH v5] " Jim Bride
2017-08-03  7:30     ` David Weinehall
2017-07-25 17:13 ` David Weinehall [this message]
2017-07-26 17:09   ` [PATCH v4 RESEND 0/4] Kernel PSR Fix-ups Jim Bride
2017-07-25 17:15 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-07-30 10:47 ` ✗ Fi.CI.BAT: warning for Kernel PSR Fix-ups (rev2) Patchwork

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=20170725171303.qepeomjus7hmapii@boom \
    --to=david.weinehall@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jim.bride@linux.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