From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "C, Ramalingam" <ramalingam.c@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/i915: Only enabled DRRS if PRS won't be enabled on this pipe.
Date: Wed, 25 Mar 2015 15:41:51 +0000 [thread overview]
Message-ID: <1427298098.4663.154.camel@intel.com> (raw)
In-Reply-To: <5512901F.7040005@intel.com>
On Wed, 2015-03-25 at 16:08 +0530, Ramalingam C wrote:
> On Wednesday 25 March 2015 12:42 AM, Rodrigo Vivi wrote:
> > With PSR enabled being pre computed on pipe_config we can now
> > prevent DRRS to be enabled along with PSR.
> >
> > Cc: Ramalingam C <ramalingam.c@intel.com>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_dp.c | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> > index 637dd53..af28833 100644
> > --- a/drivers/gpu/drm/i915/intel_dp.c
> > +++ b/drivers/gpu/drm/i915/intel_dp.c
> > @@ -4992,11 +4992,6 @@ static void intel_dp_set_drrs_state(struct drm_device *dev, int refresh_rate)
> > return;
> > }
> >
> > - /*
> > - * FIXME: This needs proper synchronization with psr state for some
> > - * platforms that cannot have PSR and DRRS enabled at the same time.
> > - */
> > -
> > dig_port = dp_to_dig_port(intel_dp);
> > encoder = &dig_port->base;
> > intel_crtc = encoder->new_crtc;
> > @@ -5082,6 +5077,11 @@ void intel_edp_drrs_enable(struct intel_dp *intel_dp)
> > return;
> > }
> >
> > + if (intel_crtc->config->psr_enabled) {
> > + DRM_DEBUG_KMS("DRRS: PSR enabled on this crtc\n");
> > + return;
> > + }
> > +
> But you might want to explicitly disable the DRRS when PSR is supported.
> Because incase DRRS is enabled before PSR,
> then blocking the enable call wont help us to stop DRRS.
> In fact I would have suggested to place this in DRRS init path. But a
> feature called media playback DRRS(in RFC stage)
> needs DRRS active even when PSR is enabled/supported. So dont want to
> block the DRRS init path because PSR is supported.
> Disabling alone will be sufficient.
>
> So as soon as PSR support is detected you would like to explicitly
> disable the DRRS(if it is supported)
> along with blocking further drrs_enable calls.
Not actually. Please take a look on the other patch on this series.
If possible please review both.
intel_crtc->config->psr_enabled is pre-computed and comes before DRRS
enabling. So with this pre-computed psr enable flag we don't need to
switch other states because DRRS won't be enabled never.
> > mutex_lock(&dev_priv->drrs.mutex);
> > if (WARN_ON(dev_priv->drrs.dp)) {
> > DRM_ERROR("DRRS already enabled\n");
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-25 15:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 19:12 [PATCH 1/2] drm/i915: Add psr_enabled on pipe_config Rodrigo Vivi
2015-03-24 19:12 ` [PATCH 2/2] drm/i915: Only enabled DRRS if PRS won't be enabled on this pipe Rodrigo Vivi
2015-03-24 23:17 ` shuang.he
2015-03-25 10:38 ` Ramalingam C
2015-03-25 15:41 ` Vivi, Rodrigo [this message]
2015-03-26 14:39 ` Ramalingam C
2015-03-26 19:21 ` Rodrigo Vivi
2015-03-30 9:49 ` Ramalingam C
2015-03-30 15:39 ` Daniel Vetter
2015-03-31 13:34 ` Daniel Vetter
2015-03-25 7:04 ` [PATCH 1/2] drm/i915: Add psr_enabled on pipe_config Sivakumar Thulasimani
2015-03-25 20:21 ` Rodrigo Vivi
2015-03-26 14:50 ` Ramalingam C
2015-03-26 19:20 ` [PATCH 1/2] drm/i915: Add psr_ready " Rodrigo Vivi
2015-03-27 6:07 ` Sivakumar Thulasimani
2015-03-27 8:32 ` Daniel Vetter
2015-03-27 9:00 ` Sivakumar Thulasimani
2015-03-30 9:50 ` Ramalingam C
-- strict thread matches above, loose matches on Subject: below --
2015-04-15 16:38 Rodrigo Vivi
2015-04-15 16:38 ` [PATCH 2/2] drm/i915: Only enabled DRRS if PRS won't be enabled on this pipe Rodrigo Vivi
2015-04-16 11:49 ` shuang.he
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=1427298098.4663.154.camel@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ramalingam.c@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