dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 00/16] omapdrm: Implement dma_buf import
Date: Wed, 16 Dec 2015 18:18:18 +0200	[thread overview]
Message-ID: <56718ECA.9070806@ti.com> (raw)
In-Reply-To: <1450125584-31701-1-git-send-email-laurent.pinchart@ideasonboard.com>


[-- Attachment #1.1: Type: text/plain, Size: 2508 bytes --]

Hi Laurent,

On 14/12/15 22:39, Laurent Pinchart wrote:
> Hello,
> 
> This patch series implements support for dma_buf import in the omapdrm driver.
> The patches are based on top of the latest drm-next branch and can be found in
> my git tree at
> 
>         git://linuxtv.org/pinchartl/fbdev.git omapdrm/dmabuf-import
> 
> The first two patches are unrelated fixes and enhancements, but I've included
> them in the series to avoid merge conflicts.
> 
> The next 13 patches are miscellaneous fixes, cleanups and refactoring to
> prepare for patch 16/16 that implements dma_buf import.
> 
> The code has been successfully tested with the vivid driver as an exporter,
> using a hacked version that uses uncached CPU mappings in vivid when filling
> the buffers. vivid is a test driver that generates a test pattern using the
> CPU with cached mappings by default, resulting in corruption on the screen due
> to missing cache handling. As the problem doesn't occur when sharing buffers
> not touched by the CPU or touched through uncached mappings only, it will be
> addressed separately.

I've picked up these patches to my omapdrm-4.5 branch:

drm: omapdrm: move omap_plane_reset()
drm: omapdrm: Fix plane state free in plane reset handler
drm: omapdrm: Make fbdev emulation optional
drm: omapdrm: gem: Remove unused function prototypes
drm: omapdrm: gem: Remove forward declarations
drm: omapdrm: gem: Group functions by purpose
drm: omapdrm: gem: Move global usergart variable to omap_drm_private
drm: omapdrm: gem: Mask out private flags passed from userspace
drm: omapdrm: gem: Free the correct memory object
drm: omapdrm: gem: Fix GEM object destroy in error path
drm: omapdrm: gem: Don't free mmap offset twice
drm: omapdrm: gem: Simplify error handling when creating GEM object
drm: omapdrm: gem: Remove check for impossible condition

I did split the "Fix plane state free in plane reset handler" into two,
moving the function first. And as I dropped few patches from between the
others, they're not exactly as they were in your series.

The remaining patches are:

drm: omapdrm: gem: Remove omap_drm_private has_dmm field
drm: omapdrm: gem: Clean up GEM objects memory flags
drm: omapdrm: gem: Refactor GEM object allocation
drm: omapdrm: gem: Implement dma_buf import

Those are more complex, and I haven't fully reviewed them yet. I wanted
to get the bulk of the patches already, so that I can ensure we get at
least those to 4.5.

 Tomi


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2015-12-16 16:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 20:39 [PATCH v2 00/16] omapdrm: Implement dma_buf import Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 01/16] drm: omapdrm: Fix plane state free in plane reset handler Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 02/16] drm: omapdrm: Make fbdev emulation optional Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 03/16] drm: omapdrm: gem: Remove unused function prototypes Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 04/16] drm: omapdrm: gem: Remove forward declarations Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 05/16] drm: omapdrm: gem: Group functions by purpose Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 06/16] drm: omapdrm: gem: Move global usergart variable to omap_drm_private Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 07/16] drm: omapdrm: gem: Remove omap_drm_private has_dmm field Laurent Pinchart
2016-01-13 17:13   ` Tomi Valkeinen
2015-12-14 20:39 ` [PATCH v2 08/16] drm: omapdrm: gem: Mask out private flags passed from userspace Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 09/16] drm: omapdrm: gem: Clean up GEM objects memory flags Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 10/16] drm: omapdrm: gem: Free the correct memory object Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 11/16] drm: omapdrm: gem: Fix GEM object destroy in error path Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 12/16] drm: omapdrm: gem: Don't free mmap offset twice Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 13/16] drm: omapdrm: gem: Simplify error handling when creating GEM object Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 14/16] drm: omapdrm: gem: Remove check for impossible condition Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 15/16] drm: omapdrm: gem: Refactor GEM object allocation Laurent Pinchart
2015-12-14 20:39 ` [PATCH v2 16/16] drm: omapdrm: gem: Implement dma_buf import Laurent Pinchart
2015-12-16 16:18 ` Tomi Valkeinen [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=56718ECA.9070806@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.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