public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Komal Shah <komal_shah802003@yahoo.com>
To: "Zhang, Jian" <jzhang@ti.com>, Tony Lindgren <tony@atomide.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: RE: [PATCH] camera: c99 style structure
Date: Tue, 22 Nov 2005 21:39:30 -0800 (PST)	[thread overview]
Message-ID: <20051123053930.43841.qmail@web32904.mail.mud.yahoo.com> (raw)
In-Reply-To: <304D2A85A9643F4A991BDDF8D297BBA60181A903@dlee05.ent.ti.com>


--- "Zhang, Jian" <jzhang@ti.com> wrote:

> I think it is as simple as a bunch of board files in the same
> directory
> (drivers/media/video/omap2420). They don't need to go to
> arch/arm/mach/
> directory. I believe OMAP1 frame buffer driver takes this
> approach.

No, Imre has added OMAP2 fb support without creating new omap2
directory under drivers/video directory. But I was thinking to create
files under drivers/media/video/omap directory like
sensor_power_h2/h4/<custom board name> to export powerup/down function
related to sensors based on board interface.

Also while porting omap24xx camera interface, I want to keep the same
camera_core and sensor interface as you had suggested earlier.

---Komal Shah
http://komalshah.blogspot.com/


	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

  reply	other threads:[~2005-11-23  5:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 14:44 [PATCH] camera: c99 style structure Zhang, Jian
2005-11-23  5:39 ` Komal Shah [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-23 15:36 Zhang, Jian
2005-11-24 10:47 ` Komal Shah
2005-11-21 15:19 Zhang, Jian
2005-11-21 17:52 ` Tony Lindgren
2005-11-22  8:50   ` Komal Shah
2005-11-21 14:00 Komal Shah

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=20051123053930.43841.qmail@web32904.mail.mud.yahoo.com \
    --to=komal_shah802003@yahoo.com \
    --cc=jzhang@ti.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=tony@atomide.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