From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Mario Kleiner <mario.kleiner.de@gmail.com>
Cc: alexdeucher@gmail.com, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: Vblank timestamping improvements/fixes for Linux drm.
Date: Mon, 28 Oct 2013 13:08:20 +0200 [thread overview]
Message-ID: <20131028110820.GP13047@intel.com> (raw)
In-Reply-To: <1382776062-3770-1-git-send-email-mario.kleiner.de@gmail.com>
On Sat, Oct 26, 2013 at 10:27:38AM +0200, Mario Kleiner wrote:
> Hi all,
>
> this patch set for the kernel pushes the latency sensitive bits of
> vblank scanoutpos timestamping from the drm core into the kms drivers.
>
> A change in the locking of the intel-kms driver for Linux 3.11 made
> the old approach too inaccurate and also incompatible with the
> PREEMPT_RT realtime kernel patch set. These patches fix that problem
> and restore the old level of precision and reliability.
>
> The patch set changes the prototype of driver->get_scanout_position()
> to require/allow kms drivers to perform the ktime_get() system time
> queries which go along with actual scanout position readout in a way
> that provides maximum precision and to return those timestamps to
> the drm. It also converts the only two kms drivers which use this api
> so far (intel-kms and radeon-kms) to the new api and improves precision
> and reliability of the intel-kms a lot.
>
> Patches have been tested on Intel and AMD Radeon hardware and the Intel
> bits have received some review and feedback by Ville Syrjälä.
>
> Please review and apply if possible.
I only have a minor nit about the formatting of multiline comments.
They should look like:
/*
* foo
* bar
*/
instead of:
/* foo
* bar
*/
But other than that I didn't spot any issues, so for the series:
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-10-28 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 8:27 Vblank timestamping improvements/fixes for Linux drm Mario Kleiner
2013-10-26 8:27 ` [PATCH 1/4] drm: Remove preempt_disable() from vblank timestamping code Mario Kleiner
2013-10-26 8:27 ` [PATCH 2/4] drm: Push latency sensitive bits of vblank scanoutpos timestamping into kms drivers Mario Kleiner
2013-10-26 8:27 ` [PATCH 3/4] drm/radeon: Push get_scanout_position() timestamping into kms driver Mario Kleiner
2013-10-26 8:27 ` [PATCH 4/4] drm/intel: " Mario Kleiner
2013-10-28 11:08 ` Ville Syrjälä [this message]
2013-10-28 15:54 ` Vblank timestamping improvements/fixes for Linux drm Alex Deucher
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=20131028110820.GP13047@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mario.kleiner.de@gmail.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;
as well as URLs for NNTP newsgroup(s).