From: Sakari Ailus <sakari.ailus@nokia.com>
To: ext Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: v4l <video4linux-list@redhat.com>,
"linux-omap@vger.kernel.org Mailing List"
<linux-omap@vger.kernel.org>,
hiroshi DOYU <Hiroshi.DOYU@nokia.com>
Subject: Re: [PATCH] Add OMAP2 camera driver
Date: Tue, 09 Dec 2008 10:53:43 +0200 [thread overview]
Message-ID: <493E3217.8050503@nokia.com> (raw)
In-Reply-To: <20081208194235.4991873d@pedra.chehab.org>
ext Mauro Carvalho Chehab wrote:
> On Thu, 27 Nov 2008 00:14:51 +0530
> "Trilok Soni" <soni.trilok@gmail.com> wrote:
>
>> +
>> +/*
>> + *
>> + * DMA hardware.
>> + *
>> + */
>> +
>> +/* Ack all interrupt on CSR and IRQSTATUS_L0 */
>> +static void omap24xxcam_dmahw_ack_all(unsigned long base)
>
> Oh, no! yet another dma video buffers handling...
>
> Soni, couldn't this be converted to use videobuf?
Yes, it could be.
The DMA part is definitely the ugliest part of omap24xxcam.
This is actually also a DMA controller driver. The system DMA driver
could not be used as such as it was limited to just one controller ---
the OMAP 2 camera block has its own DMA controller with four transfers
in queue (maximum).
There's also an MMU, not the system MMU but the camera block MMU. This
MMU is not being used now by omap24xxcam at all since when omap24xxcam
driver was written, there was not too much time available and no generic
MMU framework. So the MMU support was left out. Instead, there's a hack
to allocate as large as possible continuous memory areas and avoid
overruns that way. DMA transfer overruns happen on large proportion of
frames without this hack.
Hiroshi Doyu is working on a generic IOMMU framework for OMAPs that
could be used here. With that framework available, converting the OMAP 2
camera driver to use videobuf would be a lot easier. The performance
would be better, too. A generic DMA controller driver would be also good
to have but not mandatory.
Cheers,
--
Sakari Ailus
sakari.ailus@nokia.com
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-12-09 8:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 18:44 [PATCH] Add OMAP2 camera driver Trilok Soni
2008-11-26 20:16 ` Hans Verkuil
2008-11-27 7:23 ` Trilok Soni
2008-11-27 9:35 ` Sakari Ailus
2008-11-27 17:42 ` Trilok Soni
2008-11-28 10:07 ` Trilok Soni
2008-12-01 12:57 ` Hans Verkuil
2008-12-01 13:32 ` Trilok Soni
2008-12-01 13:34 ` Sakari Ailus
2008-12-03 4:41 ` Hiremath, Vaibhav
2008-12-03 6:48 ` Trilok Soni
2008-12-03 7:05 ` Hiremath, Vaibhav
2008-12-03 7:32 ` Hans Verkuil
2008-12-03 9:41 ` Trilok Soni
2008-12-03 12:47 ` Sakari Ailus
2008-12-04 18:28 ` Aguirre Rodriguez, Sergio Alberto
2008-12-08 12:05 ` Sakari Ailus
2008-12-08 21:37 ` Mauro Carvalho Chehab
2008-12-08 21:42 ` Mauro Carvalho Chehab
2008-12-08 21:58 ` Mauro Carvalho Chehab
2008-12-09 8:53 ` Sakari Ailus [this message]
2008-12-10 11:43 ` Trilok Soni
[not found] <C8A6D84C-B0DE-4169-B9B0-744285908E42@student.utwente.nl>
2008-12-03 9:37 ` Hiremath, Vaibhav
[not found] <20081204234534.GJ7054@atomide.com>
2008-12-05 18:57 ` Hiremath, Vaibhav
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=493E3217.8050503@nokia.com \
--to=sakari.ailus@nokia.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=video4linux-list@redhat.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