From: Sakari Ailus <sakari.ailus@nokia.com>
To: "ext Syed Mohammed, Khasim" <x0khasim@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP2: Camera: Add OMAP2 24xx camera driver.
Date: Mon, 05 Mar 2007 11:25:04 +0200 [thread overview]
Message-ID: <45EBE1F0.4070108@nokia.com> (raw)
In-Reply-To: <9C23CDD79DA20A479D4615857B2E2C47622854@dlee13.ent.ti.com>
ext Syed Mohammed, Khasim wrote:
> I am yet to review this patch completely. One immediate topic that I
> want to bring up is about DMA files. In Jian's code to David and Komal
> he had DMA driver integrated into camera driver and David moved the DMA
> part to new file. Which according to me was an OK one, but in your patch
> set I see around 3 DMA related files. I really don't see a necessity for
> this split.
>
> If you really want to clean up the DMA part of it then its better to
> upgrade the dma.c file for OMAP2, the CAM_DMA and system_DMA are same.
> Why not add this functionality there? Or use the existing DMA
> functionality instead of duplicating the code.
>
> Also, looking at the future Camera work for 3430 I feel this DMA
> framework is definitely going totally different (FYI there is no
> integrated CAM DMA in ISP). We have to use MMU here and we are looking
> at adopting Trilok's and DOYU-san's MMU framework.
I haven't looked at the 3430 spec yet, but the MMU should be used on
2420 as well. Is it different on 3430? The current allocation of
memory-mapped buffers is a hack...
> Can you please give some insight into this DMA split?
I did the DMA split to reduce the mess. I also think the new interface
offered by the DMA code is better. DMA is split to scatter-gather DMA,
individual DMA channels and DMA hardware handling. Accesses to different
logical parts are fairly clearly visible (e.g. container_of stuff). And
it's out of the main driver. The splitting into files could be of course
different, but I have to say like some things in Java. ;)
But indeed if there's a general DMA framework that could be used, then I
suppose that's the way to go eventually.
--
Sakari Ailus
sakari.ailus@nokia.com
next prev parent reply other threads:[~2007-03-05 9:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 15:49 [PATCH] OMAP2 camera and TCM825x sensor drivers Sakari Ailus
2007-02-28 15:59 ` [PATCH] ARM: OMAP2: Camera: Add OMAP2 24xx camera driver Sakari Ailus
2007-02-28 15:59 ` [PATCH] ARM: OMAP2: Camera: Add a driver for TCM825x sensor Sakari Ailus
2007-02-28 15:59 ` [PATCH] ARM: OMAP2: Camera: Modify sensor interface Sakari Ailus
2007-02-28 15:59 ` [PATCH] ARM: OMAP2: Camera: Adapt to 2.6.20 Sakari Ailus
2007-03-01 5:28 ` Trilok Soni
2007-03-02 11:49 ` Sakari Ailus
2007-03-01 7:26 ` [PATCH] ARM: OMAP2: Camera: Add OMAP2 24xx camera driver Trilok Soni
2007-03-02 17:50 ` Sakari Ailus
2007-03-02 15:18 ` Syed Mohammed, Khasim
2007-03-05 9:25 ` Sakari Ailus [this message]
2007-03-05 10:26 ` Trilok Soni
2007-03-02 19:12 ` Syed Mohammed, Khasim
[not found] ` <b8bf37780702280821wb17104chf75b973b420895ef@mail.gmail.com>
[not found] ` <200703010848.32757.andre.rosa@indt.org.br>
2007-03-14 9:29 ` Fwd: " Sakari Ailus
2007-02-28 16:39 ` [PATCH] OMAP2 camera and TCM825x sensor drivers Syed Mohammed, Khasim
2007-03-01 5:48 ` Trilok Soni
2007-03-01 8:06 ` tony
2007-03-01 23:03 ` Syed Mohammed, Khasim
2007-03-02 4:39 ` sahlot arvind
2007-03-02 11:15 ` André Goddard Rosa
2007-03-07 12:08 ` Sakari Ailus
2007-03-02 9:42 ` Sakari Ailus
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=45EBE1F0.4070108@nokia.com \
--to=sakari.ailus@nokia.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=x0khasim@ti.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