From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "daniel@fooishbar.org" <daniel@fooishbar.org>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] drm/i915: Also delay first activation for SKL+
Date: Thu, 19 Nov 2015 18:45:17 +0000 [thread overview]
Message-ID: <1447958760.10142.11.camel@intel.com> (raw)
In-Reply-To: <CAPj87rPEzw6Phxo7AxsE92_enQ3Ld=1=8drqxhLp2ez1HpNyxQ@mail.gmail.com>
On Thu, 2015-11-19 at 08:44 +0000, Daniel Stone wrote:
> Hi Rodrigo,
>
> On 19 November 2015 at 00:39, Rodrigo Vivi <rodrigo.vivi@intel.com>
> wrote:
> > @@ -441,15 +438,14 @@ void intel_psr_enable(struct intel_dp
> > *intel_dp)
> > /*
> > * FIXME: Activation should happen immediately since this
> > function
> > * is just called after pipe is fully trained and enabled.
> > - * However on every platform we face issues when first
> > activation
> > + * However on some platforms we face issues when first
> > activation
> > * follows a modeset so quickly.
> > * - On VLV/CHV we get bank screen on first activation
> > * - On HSW/BDW we get a recoverable frozen screen
> > until next
> > * exit-activate sequence.
> > */
> > - if (INTEL_INFO(dev)->gen < 9)
> > - schedule_delayed_work(&dev_priv->psr.work,
> > - msecs_to_jiffies(intel_dp
> > ->panel_power_cycle_delay * 5));
> > + schedule_delayed_work(&dev_priv->psr.work,
> > + msecs_to_jiffies(intel_dp
> > ->panel_power_cycle_delay * 5));
>
> The comment change here seems to be the exact opposite of the code
> change:
Indeed, this is why I'll keep the fixme on the comment.
> aren't we now seeing these issues on every platform? If not,
> it would be good to elaborate on the issues seen in SKL/BSW.
So far no known issue on SKL/KBL. (BSW is CHV)
But since we have no idea why these issues are happening and separated
handling was causing confusion I preferred to handle all with the
protection.
Regarding the issue itself, the Hardware needs to communicate with the
Sink using AUX channels. I believe there is just kind of strange
conflict going on there because the failures are exactly when we are
also using aux channels for our modeset/link-trainings.
This is also why I used panel_power_cycle_delay * 5 there because it is
the same value we use to force VDD on while we are doing the aux
transactions.
Please let me know if you have further questions, concerns or
suggestions here.
Thanks
>
> Cheers,
> Daniel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-11-19 18:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 0:39 [PATCH 0/3] More PSR improvements Rodrigo Vivi
2015-11-19 0:39 ` [PATCH 1/3] drm/i915: Also delay first activation for SKL+ Rodrigo Vivi
2015-11-19 6:07 ` R, Durgadoss
2015-11-19 8:44 ` Daniel Stone
2015-11-19 18:45 ` Vivi, Rodrigo [this message]
2015-11-19 0:39 ` [PATCH 2/3] drm/i915: Remove PSR Perf Counter " Rodrigo Vivi
2015-11-19 6:09 ` R, Durgadoss
2015-11-19 7:45 ` Jindal, Sonika
2015-11-19 18:31 ` Rodrigo Vivi
2015-11-20 6:01 ` Jindal, Sonika
2015-11-20 19:14 ` Vivi, Rodrigo
2015-11-23 22:16 ` [PATCH] " Rodrigo Vivi
2015-11-24 12:33 ` Daniel Vetter
2015-11-19 0:39 ` [PATCH 3/3] drm/i915: Also disable PSR on Sink when disabling it on Source Rodrigo Vivi
2015-11-19 4:26 ` Jindal, Sonika
2015-11-23 22:19 ` [PATCH] " Rodrigo Vivi
2015-11-24 4:40 ` Jindal, Sonika
2015-11-24 12:34 ` Daniel Vetter
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=1447958760.10142.11.camel@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=daniel@fooishbar.org \
--cc=intel-gfx@lists.freedesktop.org \
/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