Hi all,
after obsessing over these for another month after xds 2010,
this is the first version of my vblank timestamping patches that
i'm not totally ashamed off.
1st patch modifies the drm vblank handling to maintain precise
timestamps of when vblanks happen. It timestamps the end of
each vblank
rent 5 seconds and should allow longer vblank off
periods for better power savings.
Followup patches will use these new functions to
implement precise timestamping for the intel and radeon
kms drivers.
Signed-off-by: Mario Kleiner
---
drivers/gpu/drm/drm_crtc_helper.c | 13 +-
drivers/gpu/drm/drm_i
oked up to
.get_scanout_position().
This code has been tested on AVIVO hardware, a RV530
(ATI Mobility Radeon X1600) in a Intel Core-2 Duo MacBookPro
and some R600 variant (FireGL V7600) in a single cpu
AMD Athlon 64 PC.
Signed-off-by: Mario Kleiner
---
drivers/gpu/drm/radeon/radeon_displa
's
has not been tested so far due to lack of hardware.
Signed-off-by: Mario Kleiner
---
drivers/gpu/drm/i915/i915_drv.c |2 +
drivers/gpu/drm/i915/i915_drv.h |7 +++
drivers/gpu/drm/i915/i915_irq.c | 92 ++
drivers/gpu/drm/i915/intel_d
Oh btw., the patches are against the current drm-radeon-testing tree,
applied after commit...
21c74a8ea8b47eb6c3c621e36578f6e27f65c5c7
"drm, kdb, kms: Change mode_set_base_atomic() enter argument to be an enum"
... and should apply cleanly.
thanks,
-mario
--
the wrong moment, but kernel code
inside the irq handler should be more robust. Also it would allow a
more precise implementation of the UST timestamp according to the
OML_sync_control spec, as that spec asks for UST being the time of
start of scanout of the first scanline of a new video frame, instead
of star
Hello everybody
My name is Mario Kleiner and i'm new to this list, so i apologize
beforehand should i violate some rules of netiquette, state the
totally obvious, or if this post is somehow considered off-topic or
way too long. Please tell me if so, and how to do better next time.
