All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Vijay Purushothaman <vijay.a.purushothaman@intel.com>
Cc: intel-gfx@lists.freedesktop.org, "Goel, Akash" <akash.goel@intel.com>
Subject: Re: Request for feedback - Sprite flip notification support
Date: Wed, 5 Feb 2014 17:13:33 +0200	[thread overview]
Message-ID: <20140205151333.GM3891@intel.com> (raw)
In-Reply-To: <52F25327.2060806@intel.com>

On Wed, Feb 05, 2014 at 08:35:11PM +0530, Vijay Purushothaman wrote:
> Hello,
> 
> In our current driver implementation we support flip notifications only 
> for primary plane. So, in a full screen video playback scenario where 
> only one sprite plane is active, the user space is forced to rely on 
> primary plane flip notification even though there is no real need for 
> this plane to be active. Ideally we should be able to support flip 
> notifications for any given plane. Switching off the primary plane (when 
> not used) will help in better memory self refresh & decent power savings..
> 
> We do have a hack in android product trees which supports flip 
> notifications for one sprite plane. unfortunately this hack in its 
> current form cannot be considered for up streaming...
> 
> My current thinking is to have an array of unpin_work items to match the 
> number of planes. Is anyone working on this or thought about this 
> scenario in detail? Any pointers / restrictions that needs to considered 
> for a generic implementation of this feature?

The plan is to implement the nuclear page flip which will take care of
all planes in the same way.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-02-05 15:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 15:05 Request for feedback - Sprite flip notification support Vijay Purushothaman
2014-02-05 15:13 ` Ville Syrjälä [this message]
2014-02-05 15:55   ` Vijay Purushothaman
2014-02-05 16:48     ` Ville Syrjälä
2014-02-06  6:58       ` Vijay Purushothaman
2014-02-07  6:36         ` Vijay Purushothaman
2014-02-07  8:40           ` Daniel Vetter

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=20140205151333.GM3891@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=akash.goel@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=vijay.a.purushothaman@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.