public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Darius <augulis.darius@gmail.com>
To: video4linux-list@redhat.com
Subject: Re: question about SoC Camera driver (Micron)
Date: Fri, 23 May 2008 12:05:33 +0300	[thread overview]
Message-ID: <g161n1$vmf$1@ger.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0805222105360.8800@axis700.grange>


> Please, tell me exactly where you suspect bugs. soc_camera.c, 
> pxa_camera.c, mt9?0??.c all have *try_fmt_cap().

I see, but try_fmt_cap does not return camera capabilities, it only tries pixel format, without driver state changing.
Maybe it is good idea to implement additional g_fmt_cap ioctl handler in soc_camera? Or instead try_fmt_cap?
Because s_fmt_cap is for fmt setting, g_fmt_cap for getting camera fmt capabilities, and try_fmt_cap is for what? For getting fmt too?
v4l2 documentation recommends not implement this ioctl in the driver.

> 
>> btw, can you tell something about frame rate setting? how to implement that?
>> for example, I want from user space adjust frame rate (4, 15, 25, 30fps...).
>> Should I pass these setting to sensor driver via *_set_fmt_cap()?
> 
> This is not supported.
> 

I think should be not hard to implement vidioc_g_parm and vidioc_s_parm in soc_camera to support frame rate setting?
Now I'm writing driver for OV7670, and I plan to add these features (frame rate setting and g_fmt_cap) to soc_camera driver.
What is your opinion?

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

      reply	other threads:[~2008-05-23  9:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12 14:03 question about SoC Camera driver (Micron) Darius
2008-05-12 18:32 ` Guennadi Liakhovetski
2008-05-13  8:31   ` Darius
2008-05-13 20:19     ` Guennadi Liakhovetski
2008-05-15 14:31       ` Darius
2008-05-15 19:39         ` Guennadi Liakhovetski
2008-05-22 13:19           ` Darius
2008-05-22 19:19             ` Guennadi Liakhovetski
2008-05-23  9:05               ` Darius [this message]

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='g161n1$vmf$1@ger.gmane.org' \
    --to=augulis.darius@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