public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: davidsin@ti.com (David Sin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/9] TI DMM-TILER driver
Date: Wed, 22 Dec 2010 08:33:52 -0600	[thread overview]
Message-ID: <20101222143350.GA27503@lba0869738> (raw)
In-Reply-To: <AANLkTikZwm45Mkj_A=zzULeGBuYpLyP9N1bSJSFWegWV@mail.gmail.com>

On Fri, Dec 17, 2010 at 09:28:07AM +1000, Dave Airlie wrote:
> On Fri, Dec 17, 2010 at 5:02 AM, David Sin <davidsin@ti.com> wrote:
> I get the impression with the ARM graphics, that you just have a lot
> of separate drivers for separate IP blocks all providing some misc
> random interfaces to userspace where some binary driver binds all the
> functionality together into a useful whole, which seems like a really
> bad design.
> 
> Generally on x86, the tiling hw is part of the GPU and is exposed as
> part of a coherent GPU driver.
> 
> I'm just wonder what the use-cases for this tiler are and what open
> apps can use it for?
> 
> Dave.
Yes -- on the omap4 soc, the dmm-tiler hw block is separate from the 
gpu.  I've had some, but not much, past discusions on hw designs 
where graphics/video related ip blocks are part of the same core.  It's 
a good point that you bring up and it certainly makes sense to me.  
I will bring it up with some omap hw folks that I know, and see if 
something that can be considered in future omap versions.
 
Some of the use-cases are HD video decoding and encoding.  Also, 
hi-res image capture -- I believe 12MP or greater.  OpenMax IL components 
and other multimedia frameworks can allocate video memory 
through a user space tiler library.  Thanks for your comments, Dave.  
-- 
David Sin

      reply	other threads:[~2010-12-22 14:33 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
2010-12-16 19:02         ` David Sin
2010-12-16 23:28           ` Dave Airlie
2010-12-22 14:33             ` David Sin [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=20101222143350.GA27503@lba0869738 \
    --to=davidsin@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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