From: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Fix PSR2 selective update corruption after PSR1 setup
Date: Fri, 15 Mar 2019 14:56:12 -0700 [thread overview]
Message-ID: <3c74174e4895fc059e4d56fff31dee587db04b2f.camel@intel.com> (raw)
In-Reply-To: <20190314230113.6571-1-jose.souza@intel.com>
On Thu, 2019-03-14 at 16:01 -0700, José Roberto de Souza wrote:
> There is probably a issue in DMC firmwares(icl_dmc_ver1_07.bin and
> kbl_dmc_ver1_04.bin at least) that causes PSR2 SU to fail
nit: instead of "fail", it is better to document what you see visually
- freeze, flicker, corruption etc.
> after
> exiting DC6 if EDP_PSR_TP1_TP3_SEL is kept in PSR_CTL, so for now
> lets workaround the issue by cleaning PSR_CTL before enable PSR2.
>
> v2:
> - Updated commit description and comment to state that it may be
> a DMC firmware issue (Rodrigo)
> - No need to RMW, let's write 0 to PSR_CTL(Dhinakaran)
Based on the discussion with José offline, this work around sounds
reasonable to have until we have answers to whether this is a DMC
issue.
Reviewed-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@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>
> ---
> drivers/gpu/drm/i915/intel_psr.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_psr.c
> b/drivers/gpu/drm/i915/intel_psr.c
> index 7d570a45fc17..10bf70e521b6 100644
> --- a/drivers/gpu/drm/i915/intel_psr.c
> +++ b/drivers/gpu/drm/i915/intel_psr.c
> @@ -531,6 +531,14 @@ static void hsw_activate_psr2(struct intel_dp
> *intel_dp)
> else
> val |= EDP_PSR2_TP2_TIME_2500us;
>
> + /*
> + * FIXME: There is probably a issue in DMC
> firmwares(icl_dmc_ver1_07.bin
> + * and kbl_dmc_ver1_04.bin at least) that causes PSR2 SU to
nit: Expand SU to selective update, I am not sure how familiar others
with these acronyms.
> fail after
> + * exiting DC6 if EDP_PSR_TP1_TP3_SEL is kept in PSR_CTL, so
> for now
> + * lets workaround the issue by cleaning PSR_CTL before enable
clearing*
> PSR2.
> + */
> + I915_WRITE(EDP_PSR_CTL, 0);
> +
> I915_WRITE(EDP_PSR2_CTL, val);
> }
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-03-15 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 23:01 [PATCH v2] drm/i915: Fix PSR2 selective update corruption after PSR1 setup José Roberto de Souza
2019-03-15 0:26 ` ✓ Fi.CI.BAT: success for drm/i915: Fix PSR2 selective update corruption after PSR1 setup (rev3) Patchwork
2019-03-15 16:37 ` [PATCH v2] drm/i915: Fix PSR2 selective update corruption after PSR1 setup Rodrigo Vivi
2019-03-15 21:56 ` Dhinakaran Pandiyan [this message]
2019-03-15 22:28 ` ✗ Fi.CI.BAT: failure for drm/i915: Fix PSR2 selective update corruption after PSR1 setup (rev4) Patchwork
2019-03-19 0:07 ` ✓ Fi.CI.BAT: success for drm/i915: Fix PSR2 selective update corruption after PSR1 setup (rev5) Patchwork
2019-03-19 14:06 ` ✓ Fi.CI.IGT: " Patchwork
2019-03-19 19:55 ` Souza, Jose
2019-03-19 20:50 ` 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=3c74174e4895fc059e4d56fff31dee587db04b2f.camel@intel.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.