public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@nokia.com>
To: ext Trilok Soni <soni.trilok@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP2: Camera: Adapt to 2.6.20.
Date: Fri, 02 Mar 2007 13:49:03 +0200	[thread overview]
Message-ID: <45E80F2F.8060008@nokia.com> (raw)
In-Reply-To: <5d5443650702282128v6d3e7ab6jff886249e300db6e@mail.gmail.com>

ext Trilok Soni wrote:
> I think you have not looked at patches posted by me about OMAP2420
> camera. Part of the changes are taken from N800 kernel tree and TI's
> tree. Those sensor interface changes are also changed to adapt TI
> Micron sensor. I believe you should have worked on those changes and
> modified sensor interface for N800. Why re-work?

I was actually thinking of that sensor interface change due to Micron 
sensor (in your patches) a bit. Anyway, as I said, this is a work in 
progress, and I've been just trying to keep the driver somehow functional.

I don't like the original sensor interface very much. It passes void 
pointers with no name to interface functions, these pointers obviously 
point to some sensor private data. Then the init function returns the 
pointer to the sensor. Hmm.

I'd like that the sensor didn't know about the camera. This is 
accomplished by adding a generic camera interface with register, reset 
(so far specific to N800) and unregister. The sensor could then register 
itself to the camera, whose pointer it gets from its configuration 
(machine specific).

module field has been added so that the camera can try_module_get() the 
sensor when the device is opened. Beyond that it's just what I see fit. 
:) This is all naturally open for changes.

> http://linux.omap.com/pipermail/linux-omap-open-source/2007-February/009062.html 
> 
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-February/009063.html 
> 
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-February/009069.html 
> 
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-February/009064.html 
> 
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-February/009065.html 
> 
> 
> Please help me to review above patches instead, then we will have less
> re-work and come to conclusion, whose patches should be integrated
> instead. BTW, I have N800 so I can test this sensor now.

I'll have a look.

-- 
Sakari Ailus
sakari.ailus@nokia.com

  reply	other threads:[~2007-03-02 11:49 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 [this message]
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
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=45E80F2F.8060008@nokia.com \
    --to=sakari.ailus@nokia.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=soni.trilok@gmail.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