From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Kumar, Shobhit" <shobhit.kumar@linux.intel.com>
Cc: Intel Graphics Development <Intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Suspend resume timing optimization.
Date: Wed, 9 Dec 2015 14:12:47 +0200 [thread overview]
Message-ID: <20151209121247.GB4437@intel.com> (raw)
In-Reply-To: <566808AD.4070700@linux.intel.com>
On Wed, Dec 09, 2015 at 04:25:41PM +0530, Kumar, Shobhit wrote:
> On 12/08/2015 02:22 AM, Paulo Zanoni wrote:
> > 2015-12-07 18:28 GMT-02:00 <abhay.kumar@intel.com>:
> >> From: Abhay Kumar <abhay.kumar@intel.com>
> >>
> >> Moving 250ms from T12 timing to suspend path so that
> >> resume path will be faster.
> >
> > Can you please elaborate more on your motivation for this patch? I'm a
> > little confused. You're trying to make resume faster by making suspend
> > slower? What are your main arguments for this?
> >
>
> Actually the display resume time is currently roughly around ~700ms for
> eDP. The panel power sequence as per spec needs to be minimum 510ms . So
> the t11_12 time is 600ms in our code. Question is how to optimize this.
> What Abhay has tried is to move the wait for panel_power_cycle_delay in
> the suspend path rather then in resume path when we check if panel has
> power. Since this is jiffied based we end up waiting while going down
> and by the time we come back jiffies have already expired, giving us
> optimization in resume path. Will this work. Is it violates the spec in
> any way ? Any other suggestions ?
I'm thinking this should work. However, it seems unlikely we would
really need any wait during suspend or resume since the panel will
likely be off for a longer period anyway while the machine is
suspended. So I wonder if we could look at the wall clock instead
during suspend? Eg. sample it during susend and resume,
and adjust last_power_cycle jiffies based on the difference.
>
> >>
> >> Signed-off-by: Abhay Kumar <abhay.kumar@intel.com>
> >> ---
> >> drivers/gpu/drm/i915/intel_ddi.c | 6 ++++++
> >> 1 file changed, 6 insertions(+)
> >>
> >> diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
> >> index 7f618cf..2679c9e 100644
> >> --- a/drivers/gpu/drm/i915/intel_ddi.c
> >> +++ b/drivers/gpu/drm/i915/intel_ddi.c
> >> @@ -2389,6 +2389,12 @@ static void intel_ddi_post_disable(struct intel_encoder *intel_encoder)
> >
> > Funcion intel_ddi_post_disable() doesn't only run on suspend
> > situations, yet your commit message suggests you're optimizing
> > suspend. Maybe this commit makes non-suspend modesets slower because
> > now we need to wait the panel power cycle earlier? Have you measured
> > the possible downsides?
>
> Yes this is a problem. I again looked at the spec and found that t7 can
> be 50, but VBT was default programming 200ms which is overriding our
> driver initialized value. Correcting VBT gives back 150ms here. But yes
> this will impact non-suspend modeset paths. Perhaps we should figure out
> a way to avoid this and do only when relevant. A flag based check would
> work ? I know it sounds hackish.
>
> >
> >> intel_dp_sink_dpms(intel_dp, DRM_MODE_DPMS_OFF);
> >> intel_edp_panel_vdd_on(intel_dp);
> >> intel_edp_panel_off(intel_dp);
> >> +
> >> + /* Give additional delay of 250 ms so that resume time will
> >> + be faster and also meets T12 delay.
> >> + */
> >
> > The comment says 250ms, but the code doesn't. Also, there's a missing
> > '*' char in the comment.
> >
> >> + wait_remaining_ms_from_jiffies(intel_dp->last_power_cycle,
> >> + (intel_dp->panel_power_cycle_delay/2));
> >
> > Why wait half the panel power cycle? Why did you choose exactly this value?
> >
>
> Actually I would want to wait out full panel power cycle delay. Brings
> our resume time down to ~250ms. But ultimately if this is acceptable
> solution, will still depend on suspend KPIs and we might have to
> balance. But as far as I know suspend path has no strict KPI, so we
> might get away with this.
>
> Regards
> Shobhit
>
> > Thanks,
> > Paulo
> >
> >> }
> >>
> >> if (IS_SKYLAKE(dev) || IS_KABYLAKE(dev))
> >> --
> >> 1.9.1
> >>
> >> _______________________________________________
> >> Intel-gfx mailing list
> >> Intel-gfx@lists.freedesktop.org
> >> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> >
> >
> >
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-12-09 12:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 20:28 [PATCH] drm/i915: Suspend resume timing optimization abhay.kumar
2015-12-07 20:52 ` Paulo Zanoni
2015-12-07 22:19 ` Kumar, Abhay
2015-12-09 10:55 ` Kumar, Shobhit
2015-12-09 12:12 ` Ville Syrjälä [this message]
2015-12-09 12:40 ` Kumar, Shobhit
2015-12-09 13:21 ` [PATCH] drm/i915: Wait for PP cycle delay only if panel is in power off sequence Shobhit Kumar
2015-12-09 13:29 ` Kumar, Shobhit
2015-12-09 13:57 ` Ville Syrjälä
2015-12-09 14:37 ` Shobhit Kumar
2015-12-09 15:04 ` Chris Wilson
2015-12-09 15:29 ` Shobhit Kumar
2015-12-09 16:05 ` Ville Syrjälä
2015-12-10 9:31 ` Kumar, Shobhit
2015-12-10 9:50 ` Daniel Vetter
2015-12-10 10:18 ` Kumar, Shobhit
2015-12-10 10:58 ` Thulasimani, Sivakumar
2015-12-10 13:15 ` Ville Syrjälä
2015-12-10 13:38 ` Ville Syrjälä
2015-12-10 14:39 ` Thulasimani, Sivakumar
2015-12-10 15:02 ` Ville Syrjälä
2015-12-11 11:25 ` Thulasimani, Sivakumar
2015-12-11 11:41 ` Kumar, Shobhit
2015-12-11 17:00 ` Daniel Vetter
2015-12-14 3:59 ` Kumar, Shobhit
2015-12-11 6:34 ` Kumar, Shobhit
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=20151209121247.GB4437@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=shobhit.kumar@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