From: Tony Lindgren <tony@atomide.com>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: Koen Kooi <k.kooi@student.utwente.nl>,
Trilok Soni <soni.trilok@gmail.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Sakari Ailus <sakari.ailus@nokia.com>,
"linux-omap@vger.kernel.org Mailing List"
<linux-omap@vger.kernel.org>,
"video4linux-list@redhat.com" <video4linux-list@redhat.com>
Subject: Re: [PATCH] Add OMAP2 camera driver
Date: Fri, 5 Dec 2008 11:12:59 -0800 [thread overview]
Message-ID: <20081205191258.GH9714@atomide.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E739403E90E75B9@dbde02.ent.ti.com>
* Hiremath, Vaibhav <hvaibhav@ti.com> [081205 10:58]:
> > From: Tony Lindgren [mailto:tony@atomide.com]
> > * Hiremath, Vaibhav <hvaibhav@ti.com> [081203 01:38]:
<snip>
> > > > Isn't DSS2 supposed to work on omap2 (and perhaps omap1) as
> > well?
> > > >
> > > [Hiremath, Vaibhav] yes, but the DSS2 library goes under
> > arch/arm/plat-omap/dss/. The above files are belongs to the driver
> > underneath.
> >
> > Huh? Why would it need to be under plat-omap?
> >
> [Hiremath, Vaibhav] This is low level library which will export
> Kernel API's to top level driver like, Frame buffer and V4L2 driver.
> So this has to be in some common directory, and both patches on
> DSS (from Tomi and from TI) aligned to the same thing.
We're not adding driver specific code to arch/arm/plat-omap.
Please place your shared driver code either under drivers/video
and export the functions needed by v4l like all other linux
driver code does.
Regards,
Tony
next prev parent reply other threads:[~2008-12-05 19:13 UTC|newest]
Thread overview: 28+ 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 17:04 ` Tony Lindgren
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:34 ` Koen Kooi
2008-12-03 9:37 ` Hiremath, Vaibhav
2008-12-04 23:45 ` Tony Lindgren
2008-12-05 18:57 ` Hiremath, Vaibhav
2008-12-05 19:12 ` Tony Lindgren [this message]
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
2008-12-10 11:43 ` Trilok Soni
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=20081205191258.GH9714@atomide.com \
--to=tony@atomide.com \
--cc=hvaibhav@ti.com \
--cc=hverkuil@xs4all.nl \
--cc=k.kooi@student.utwente.nl \
--cc=linux-omap@vger.kernel.org \
--cc=sakari.ailus@nokia.com \
--cc=soni.trilok@gmail.com \
--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