From: Tony Lindgren <tony@atomide.com>
To: Trilok Soni <soni.trilok@gmail.com>
Cc: "Pasam, Vijay" <vpasam@ti.com>,
Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
linux-omap@vger.kernel.org, "Woodruff,
Richard" <r-woodruff2@ti.com>,
felipe.contreras@gmail.com, siarhei.siamashka@nokia.com,
"Ramirez Luna, Omar" <x00omar@ti.com>,
"Gupta, Ramesh" <grgupta@ti.com>,
"Kanigeri, Hari" <h-kanigeri2@ti.com>
Subject: Re: [RFC][DRAFT] TODO list for TI DSP BRIDGE
Date: Tue, 19 Aug 2008 09:20:34 +0300 [thread overview]
Message-ID: <20080819062020.GC17276@atomide.com> (raw)
In-Reply-To: <5d5443650808181020l19e9bce2g9ccb59979f626a93@mail.gmail.com>
* Trilok Soni <soni.trilok@gmail.com> [080818 20:21]:
> Hi Vijay,
>
> On Mon, Aug 18, 2008 at 10:42 PM, Pasam, Vijay <vpasam@ti.com> wrote:
> > Hi Hiroshi,
> >
> >> Yes, "dspgateway" won't support OMAP3 but if I remember
> >> correctly that TWL is already in OMAP2? and also does Camera
> >> use the same mechanism of this MMU? This may be benefit or a
> >> must, I guess..
> >
> > I agree. If we are certain that camera driver or some other driver uses
> > MMU the same way bridge does and the MMU architecture is the same, it
> > makes sense to make this generic code. My point is that if DSPGateway
> > doesn't use TWL, it will not benefit from using the Bridge MMU code
> > which has TWL enabled.
> >
>
> I think recently some one from TI posted OMAP3 camera driver at
> linux-v4l2 mailing list and which I think was using camera MMU, but
> not the common MMU framework it seems from the description. They
> should first start converting to the common MMU infrastructure then.
>
> http://lists-archives.org/video4linux/23215-omap3-camera-driver.html
We must make the MMU framework generic for the coprocessors, otherwise
maintenance will be a nightmare and the code will never get merged
upstream.
Tony
next prev parent reply other threads:[~2008-08-19 6:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 13:35 [RFC][DRAFT] TODO list for TI DSP BRIDGE Hiroshi DOYU
2008-08-18 14:28 ` Pasam, Vijay
2008-08-18 15:08 ` Hiroshi DOYU
2008-08-18 17:12 ` Pasam, Vijay
2008-08-18 17:20 ` Trilok Soni
2008-08-19 6:20 ` Tony Lindgren [this message]
2008-08-19 12:26 ` Woodruff, Richard
2008-08-20 16:08 ` Sakari Ailus
2008-08-18 16:27 ` Kanigeri, Hari
2008-08-18 17:17 ` Trilok Soni
2008-08-18 19:28 ` Kanigeri, Hari
2008-08-18 20:08 ` Felipe Contreras
2008-08-19 6:24 ` Tony Lindgren
2008-08-19 18:24 ` Kanigeri, Hari
2008-08-19 19:10 ` Felipe Contreras
2008-08-19 20:46 ` Kanigeri, Hari
2008-08-19 23:45 ` Felipe Contreras
2008-08-20 22:34 ` Kanigeri, Hari
2008-08-21 8:10 ` Felipe Contreras
2008-08-20 10:10 ` Hiroshi DOYU
2008-08-20 14:32 ` Woodruff, Richard
2008-08-21 7:41 ` Hiroshi DOYU
2008-08-21 12:34 ` Woodruff, Richard
2008-08-21 16:11 ` Hiroshi DOYU
2008-08-21 19:43 ` Woodruff, Richard
2008-08-22 9:24 ` Hiroshi DOYU
2008-08-21 15:37 ` Kanigeri, Hari
2008-08-21 16:08 ` Hiroshi DOYU
2008-08-18 17:24 ` Trilok Soni
2008-08-19 18:33 ` Kanigeri, Hari
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=20080819062020.GC17276@atomide.com \
--to=tony@atomide.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=felipe.contreras@gmail.com \
--cc=grgupta@ti.com \
--cc=h-kanigeri2@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=r-woodruff2@ti.com \
--cc=siarhei.siamashka@nokia.com \
--cc=soni.trilok@gmail.com \
--cc=vpasam@ti.com \
--cc=x00omar@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