public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: David Sin <davidsin@ti.com>
Cc: linux-arm-kernel@lists.infradead.org,
	dri-devel@lists.freedesktop.org, Greg KH <greg@kroah.com>,
	Russell King <rmk@arm.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/9] TI DMM-TILER driver
Date: Thu, 16 Dec 2010 18:43:48 +0100	[thread overview]
Message-ID: <201012161843.48262.arnd@arndb.de> (raw)
In-Reply-To: <20101216173737.GA6767@lba0869738>

On Thursday 16 December 2010 18:37:38 David Sin wrote:
> I'm not sure exactly how DRM/GEM works..  What functionality do you think is 
> overlapping?  The main feature, aside from reduced page accesses, of the DMM 
> hw block is to provide physically contiguous 2 dimensional memory blocks for 
> image and video processing.  This hw sits between the interconnect and the 
> ext memory interface in the OMAP, and contains an MMU-like address traslator 
> for "virtually" physically contiguous memory and sdram pages.

As far as I can tell, both DMM and GEM at a high level manage objects
in video memory. The IOMMU that you have on the Omap hardware seems
to resemble the GART that sits between PC-style video cards and main
memory.

I don't know any details, but google quickly finds
http://lwn.net/Articles/283798/ with a description of the
initial GEM design. My main thought when looking over the
DMM code was that this should not be tied too closely to a
specific hardware, and GEM seems to be an existing abstraction
that may fit what you need.

	Arnd

  reply	other threads:[~2010-12-16 17:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06 22:27 [PATCH 0/9] TI DMM-TILER driver David Sin
2010-12-06 22:27 ` [PATCH 1/9] TILER-DMM: DMM-PAT driver for TI TILER David Sin
2010-12-06 22:27 ` [PATCH 2/9] TILER-DMM: Container manager interface and utility definitons David Sin
2010-12-06 22:27 ` [PATCH 3/9] TILER-DMM: Sample TCM implementation: Simple TILER Allocator (SiTA) David Sin
2010-12-06 22:27 ` [PATCH 4/9] TILER-DMM: TILER Memory Manager interface and implementation David Sin
2010-12-06 22:27 ` [PATCH 5/9] TILER-DMM: TILER interface file and documentation David Sin
2010-12-06 22:27 ` [PATCH 6/9] TILER-DMM: Geometry and view manipulation functions David Sin
2010-12-06 22:27 ` [PATCH 7/9] TILER-DMM: Main TILER driver implementation David Sin
2010-12-06 23:21   ` Tony Lindgren
2010-12-13 17:32     ` David Sin
2010-12-06 22:27 ` [PATCH 8/9] TILER-DMM: Linking TILER driver into the Linux kernel build David Sin
2010-12-06 22:27 ` [PATCH 9/9] TILER-DMM: Device support for OMAP David Sin
2010-12-16 13:34 ` [PATCH 0/9] TI DMM-TILER driver Arnd Bergmann
2010-12-16 17:25   ` David Sin
2010-12-16 17:37     ` David Sin
2010-12-16 17:43       ` Arnd Bergmann [this message]
2010-12-16 19:02         ` David Sin
2010-12-16 23:28           ` Dave Airlie
2010-12-22 14:33             ` David Sin

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=201012161843.48262.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=davidsin@ti.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=greg@kroah.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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