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 1/4] [PATCH] ARM: OMAP: Update camera sensor interface
Date: Fri, 02 Mar 2007 18:37:19 +0200	[thread overview]
Message-ID: <45E852BF.9020200@nokia.com> (raw)

Hi,

(Sorry for not replying, I just recently ordered this list.)

 > From: Trilok Soni <soni.trilok@gmail.com>
...
 > +#define PAR_MODE_NOBT8                       0
 > +#define PAR_MODE_NOBT10                      1
 > +#define PAR_MODE_NOBT12                      2
 > +#define PAR_MODE_BT8                 4
 > +#define PAR_MODE_BT10                        5
 > +
 > +#define SYNC_ACTIVE_HIGH             0
 > +#define SYNC_ACTIVE_LOW                      1

How about prefixing these with OMAP_SENSOR_ or something?

 > +#define V4L2_BUF_TYPE_STILL_CAPTURE  V4L2_BUF_TYPE_PRIVATE
 > +
 >  struct omap_camera_sensor {
 >       unsigned int version;
 >       char name[OMAP_SENSOR_NAME_LEN + 1];
 >
 > -     void *(*init)(struct v4l2_pix_format *);
 > +     int parallel_mode;  /* parallel I/F mode */
 > +     int hs_polarity;    /* horizontal sync polarity */
 > +     int vs_polarity;    /* vertical sync polarity */
 > +     int image_swap;     /* image swap or not */
 > +     int bt_correction;  /* BT correction enabled or not */

It's probably good to add here more information about the sensor. OV9640 
has differences in these compared to TCP825x? Or the Micron sensor?

 > +     /* init the sensor with the passed pix format. A none zero private
 > +        pointer must be returned on success. The same pointer is passed
 > +        back for all other functions. This gives a sensor driver the
 > +        chance to handle multiple sensor. */

Multiple sensor support is ability to handle different sensors?

What do you think of giving names to the function arguments?

 > +     void *(*init)(struct v4l2_pix_format *, struct v4l2_pix_format *);
...
 > +     /* These are only for those sensors that use a different sensor 
context
 > +        for still image capture. A simple sensor driver doesn't have to
 > +        implement them. */
 > +     int (*try_format_still_capture) (struct v4l2_pix_format *, void *);
 > +     int (*configure_still_capture) (struct v4l2_pix_format *, 
unsigned long,
 > +                                       struct v4l2_fract *, void *);
 > +     unsigned long (*calc_xclk_still_capture) (struct v4l2_pix_format *,
 > +             struct v4l2_fract *, void *);
 > +     int (*enter_still_capture) (int, void *);
 > +     int (*exit_still_capture) (void *);

Probably capturing still images and video is exclusive at least here? 
I've been thinking that omap24xxcam_poll mess...

-- 
Sakari Ailus
sakari.ailus@nokia.com

             reply	other threads:[~2007-03-02 16:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02 16:37 Sakari Ailus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-15 11:28 [PATCH 1/4] [PATCH] ARM: OMAP: Update camera sensor interface 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=45E852BF.9020200@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