linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Michael Jones <michael.jones@matrix-vision.de>
Cc: linux-media ML <linux-media@vger.kernel.org>
Subject: Re: capture_mem limitations in OMAP ISP
Date: Thu, 05 Jul 2012 18:36:24 +0200	[thread overview]
Message-ID: <2278346.UGGOgjoZYS@avalon> (raw)
In-Reply-To: <4FF2BF79.2020302@matrix-vision.de>

Hi Michael,

On Tuesday 03 July 2012 11:46:33 Michael Jones wrote:
> Hi Laurent & co.,
> 
> I'm looking at the memory limitations in the omap3isp driver. 'struct
> isp_video' contains member 'capture_mem', which is set separately for each
> of our v4l2 video device nodes. The CCDC, for example, has capture_mem =
> 4096 * 4096 * 3 = 48MB, while the previewer and resizer each have twice
> that. Where do these numbers come from?

That's mostly historical. When developing the driver for the N900 we set a 
limit to avoid putting too much pressure on the system memory, and 3x8MP 
buffers was considered to be enough.

We could raise the limit, remove it completely, or implement a policy 
mechanism to let a privileged userspace application specify limits. The later 
might be interesting as a core V4L2 mechanism.

> Is the CCDC incapable of DMA'ing more than 48MB into memory? I know that
> ISP_VIDEO_MAX_BUFFERS also limits the # of buffers, but I assume this is
> basically an arbitrary number so we can have a finite array of
> isp_video_buffer's. The 48MB, on the other hand, looks like it might have a
> good reason.

-- 
Regards,

Laurent Pinchart


      reply	other threads:[~2012-07-05 16:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03  9:46 capture_mem limitations in OMAP ISP Michael Jones
2012-07-05 16:36 ` Laurent Pinchart [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=2278346.UGGOgjoZYS@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=michael.jones@matrix-vision.de \
    /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;
as well as URLs for NNTP newsgroup(s).