From: "Saarinen, Jani" <jani.saarinen@intel.com>
To: "Srinivas, Vidya" <vidya.srinivas@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Enable scanline read for gen9 dsi
Date: Fri, 8 Sep 2017 15:25:41 +0000 [thread overview]
Message-ID: <43D4F724E12AB6478FC1572B3FBE89D075AFBBB4@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <20170908145524.GI4914@intel.com>
HI,
> -----Original Message-----
> From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf Of
> Ville Syrjälä
> Sent: perjantai 8. syyskuuta 2017 17.55
> To: Srinivas, Vidya <vidya.srinivas@intel.com>
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH] drm/i915: Enable scanline read for gen9 dsi
>
>
> Another thought that just occurred to me: Maybe we could use these
> timestamps as a workaround for the DDI "scanline reads as 0 at the wrong
> time" problem. What we could do is check of the scanline counter reads as 0,
> and if it does we could switch over to checking the timestamps instead. Not
> sure if we should just do the full timestamp based scanline read like you do
> here, or we could just check that if the timestamps look like they're close to
> vblank_start we just return vblank_start-1. This could then remove the
> obnoxious retry loop from the scanline counter read.
>
Also please use trybot also as dsi system not in pw runs due to known issue.
> --
> Ville Syrjälä
> Intel OTC
Jani Saarinen
Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-09-08 15:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 13:48 [PATCH] drm/i915: Enable scanline read for gen9 dsi Vidya Srinivas
2017-09-08 14:41 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-09-08 14:47 ` [PATCH] " Ville Syrjälä
2017-09-08 14:55 ` Ville Syrjälä
2017-09-08 15:25 ` Saarinen, Jani [this message]
2017-09-08 19:45 ` Daniel Vetter
2017-09-08 19:55 ` Chris Wilson
2017-09-11 8:52 ` Maarten Lankhorst
2017-09-11 12:21 ` Ville Syrjälä
2017-09-11 13:19 ` Shankar, Uma
2017-09-11 18:21 ` Ville Syrjälä
2017-09-12 9:32 ` Shankar, Uma
2017-09-11 13:04 ` Shankar, Uma
2017-09-11 17:50 ` Ville Syrjälä
2017-09-12 9:50 ` Shankar, Uma
2017-09-12 13:23 ` Shankar, Uma
2017-09-12 13:33 ` Ville Syrjälä
2017-09-12 13:40 ` Shankar, Uma
2017-09-12 13:55 ` Vidya Srinivas
2017-09-12 14:12 ` Ville Syrjälä
2017-09-12 14:21 ` Shankar, Uma
2017-09-12 15:06 ` Ville Syrjälä
2017-09-13 8:24 ` Shankar, Uma
2017-09-13 17:36 ` Ville Syrjälä
2017-09-14 11:47 ` Shankar, Uma
2017-09-14 12:12 ` [PATCH 1/2] " Vidya Srinivas
2017-09-14 12:12 ` [PATCH 2/2] drm/i915: Control Vblank through IER instead of IMR Vidya Srinivas
2017-09-14 12:23 ` Ville Syrjälä
2017-09-15 10:25 ` [PATCH 1/2] drm/i915: Enable scanline read for gen9 dsi Chauhan, Madhav
2017-09-12 15:00 ` ✓ Fi.CI.BAT: success for drm/i915: Enable scanline read for gen9 dsi (rev2) Patchwork
2017-09-12 18:40 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-09-18 13:41 [PATCH] drm/i915: Enable scanline read for gen9 dsi Vidya Srinivas
2017-09-19 2:31 ` kbuild test robot
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=43D4F724E12AB6478FC1572B3FBE89D075AFBBB4@IRSMSX106.ger.corp.intel.com \
--to=jani.saarinen@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vidya.srinivas@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.