From: Daniel Vetter <daniel@ffwll.ch>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: intel-gfx@lists.freedesktop.org, paulo.r.zanoni@intel.com,
rodrigo.vivi@intel.com
Subject: Re: [PATCH 0/3] Hack to test DRRS, independent of front buffer tracking
Date: Tue, 24 Mar 2015 11:53:07 +0100 [thread overview]
Message-ID: <20150324105306.GI1349@phenom.ffwll.local> (raw)
In-Reply-To: <551132B7.2080707@intel.com>
On Tue, Mar 24, 2015 at 03:17:35PM +0530, Ramalingam C wrote:
>
> On Tuesday 24 March 2015 03:05 PM, Daniel Vetter wrote:
> >On Mon, Mar 23, 2015 at 11:14:41PM +0530, Ramalingam C wrote:
> >>These patches removes the dependancy of DRRS with front buffer tracking.
> >>This will help us to test the DRRS and the IGT app for DRRS.
> >>
> >>As we have some functional issues with front buffer tracking, We are
> >>adding a debugfs, so that IGT can notify the content change to DRRS.
> >>Once the front buffer tracking is fully functional these patches are not
> >>required.
> >Nope, we need to track down the bugs in frontbuffer tracking and use the
> >existing interface to kick updates to the kernel. Yes I know this is hard,
> >but we've been struggling with frontbuffer tracking issues with fbc, psr
> >and drrs for years, adding more hacks will not magically resolve them.
> >-Daniel
> Daniel, I completely I agree with you. These patch series is not meant to
> be reviewed or merged.
> Intention of these patch creation is to enable the DRRS so that we develop
> the DRRS test cases.
> With these test cases it will be easy to narrow down on the missing fb
> status update call.
Ah, sounds excellent and makes sense. Usually I mention this in the cover
letter to avoid ppl reviewing something that I don't intend to get merged.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-03-24 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 17:44 [PATCH 0/3] Hack to test DRRS, independent of front buffer tracking Ramalingam C
2015-03-23 17:44 ` [PATCH 1/2] drm/i915: Removing the drrs from front buffer tracker Ramalingam C
2015-03-23 17:44 ` [PATCH 2/2] drm/i915/drrs: debugfs for notifying the fb status change Ramalingam C
2015-03-25 1:24 ` shuang.he
2015-03-23 17:44 ` [PATCH] tests/kms_drrs: fb change notification through debugfs Ramalingam C
2015-03-24 9:35 ` [PATCH 0/3] Hack to test DRRS, independent of front buffer tracking Daniel Vetter
2015-03-24 9:47 ` Ramalingam C
2015-03-24 10:53 ` Daniel Vetter [this message]
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=20150324105306.GI1349@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=ramalingam.c@intel.com \
--cc=rodrigo.vivi@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.