dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Rob Clark <robdclark@gmail.com>
Cc: dri-devel@lists.freedesktop.org, patches@linaro.org,
	linux-omap@vger.kernel.org,
	Tomi Valkeinen <tomi.valkeinen@ti.com>
Subject: Re: [PATCH] drm/omap: use omapdss low level API
Date: Fri, 16 Nov 2012 04:19:28 -0800	[thread overview]
Message-ID: <20121116121928.GA20226@kroah.com> (raw)
In-Reply-To: <1353024058-11504-1-git-send-email-robdclark@gmail.com>

On Thu, Nov 15, 2012 at 06:00:58PM -0600, Rob Clark wrote:
> This patch changes the omapdrm KMS to bypass the omapdss "compat"
> layer and use the core omapdss API directly.  This solves some layering
> issues that would cause unpin confusion vs GO bit status, because we
> would not know whether a particular pageflip or overlay update has hit
> the screen or not.  Now instead we explicitly manage the GO bits in
> dispc and handle the vblank/framedone interrupts ourself so that we
> always know which buffers are being scanned out at any given time, and
> so on.
> 
> As an added bonus, we no longer leave the last overlay buffer pinned
> when the display is disabled, and have been able to add the previously
> missing vblank event handling.
> 
> Signed-off-by: Rob Clark <robdclark@gmail.com>
> ---
> Note: this patch applies on top of staging-next plus the "OMAPDSS:
> create compat layer" patch series:
> 
> http://comments.gmane.org/gmane.linux.ports.arm.omap/89435

Hm, I can't take that patch set in staging-next, so how should this go
in?

thanks,

greg k-h

  parent reply	other threads:[~2012-11-16 12:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16  0:00 [PATCH] drm/omap: use omapdss low level API Rob Clark
2012-11-16  6:44 ` Archit Taneja
2012-11-16  6:53   ` Archit Taneja
2012-11-16 13:59   ` Rob Clark
2012-11-16 12:19 ` Greg KH [this message]
2012-11-19  8:10   ` Tomi Valkeinen
  -- strict thread matches above, loose matches on Subject: below --
2012-12-04 19:59 Rob Clark
2012-12-07 10:45 ` Archit Taneja
2012-12-10  8:35   ` Sumit Semwal

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=20121116121928.GA20226@kroah.com \
    --to=greg@kroah.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=robdclark@gmail.com \
    --cc=tomi.valkeinen@ti.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