All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandru-Cosmin Gheorghe <Alexandru-Cosmin.Gheorghe@arm.com>
To: Stefan Schake <stschake@gmail.com>
Cc: nd@arm.com, liviu.dudau@arm.com,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH hwc v1] [RFC] drm_hwcomposer: Flatten composition using writeback connector
Date: Wed, 14 Mar 2018 09:42:23 +0000	[thread overview]
Message-ID: <20180314094223.GA4619@e114479-lin.cambridge.arm.com> (raw)
In-Reply-To: <CAOZHkRyJ_0hdDN9KBz+47GeTgqXV9AkbOOhBmtOQL_6j7SXYrA@mail.gmail.com>

Hi Stefan,

On Tue, Mar 13, 2018 at 07:20:33PM +0100, Stefan Schake wrote:
> Hey Alexandru,
> 
> On Tue, Mar 13, 2018 at 5:21 PM, Alexandru Gheorghe
> <alexandru-cosmin.gheorghe@arm.com> wrote:
> > This patchset tries to add support for using writeback connector to
> > flatten a scene when it doesn't change for a while. This idea had
> > been floated around on IRC here [1] and here [2].
> >
> > 2. Heuristic for triggering the flattening.
> > I just created a VSyncWorker which will trigger the flattening of the
> > scene if it doesn't change for 60 consecutive vsyncs. The countdown
> > gets reset every time ValidateDisplay is called. This is a relatively
> > basic heuristic, so I'm open to suggestions.
> 
> I think when Android deems that the display is sufficiently idle, it will
> disable VSync through setVsyncEnabled. Presumably we could just trigger the
> flattening on an enabled -> disabled transition?
> 
> Thanks,
> Stefan

I will look into it thanks.

-- 
Cheers,
Alex G
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-03-14  9:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13 16:21 [PATCH hwc v1] [RFC] drm_hwcomposer: Flatten composition using writeback connector Alexandru Gheorghe
2018-03-13 18:20 ` Stefan Schake
2018-03-14  9:42   ` Alexandru-Cosmin Gheorghe [this message]
2018-03-19 18:03 ` Sean Paul
2018-03-20 11:26   ` Alexandru-Cosmin Gheorghe
2018-03-20 13:28     ` Sean Paul
2018-03-20 13:35       ` Alexandru-Cosmin Gheorghe
2018-03-20 13:43         ` Sean Paul
2018-03-20 13:51           ` Alexandru-Cosmin Gheorghe
2018-03-20 14:00 ` Sean Paul
2018-03-20 15:16   ` Alexandru-Cosmin Gheorghe
2018-03-20 19:53     ` Sean Paul
2018-03-21  3:35     ` Rob Clark
2018-03-21 14:01       ` Sean Paul
2018-03-21 15:13         ` Alexandru-Cosmin Gheorghe
2018-03-21 15:39         ` Liviu Dudau
2018-03-21 15:48       ` Eric Anholt

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=20180314094223.GA4619@e114479-lin.cambridge.arm.com \
    --to=alexandru-cosmin.gheorghe@arm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=liviu.dudau@arm.com \
    --cc=nd@arm.com \
    --cc=stschake@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 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.