Linux Media Controller development
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: "Aguirre, Sergio" <saaguirre@ti.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Ivan Ivanov <iivanov@mm-sol.com>
Subject: Re: [Query] Is there a spec to request video sensor information?
Date: Mon, 13 Sep 2010 18:27:52 +0300	[thread overview]
Message-ID: <4C8E42F8.1080201@maxwell.research.nokia.com> (raw)
In-Reply-To: <A24693684029E5489D1D202277BE894472336FC3@dlee02.ent.ti.com>

Aguirre, Sergio wrote:
> Hi,

Hi Sergio,

> I was wondering if there exists a current standard way to query a
> Imaging sensor driver for knowing things like the signal vert/horz blanking time.
> 
> In an old TI custom driver, we used to have a private IOCTL in the sensor
> Driver we interfaced with the omap3 ISP, which was basically reporting:
> 
> - Active resolution (Actual image size)
> - Full resolution (Above size + dummy pixel columns/rows representing blanking times)
> 
> However I resist to keep importing that custom interface, since I think its
> Something that could be already part of an standard API.

The N900 sensor drivers currently use private controls for this purpose.
That is an issue which should be resolved. I agree there should be a
uniform, standard way to access this information.

What we currently have is this, not in upstream:

---
/* SMIA-type sensor information */
#define V4L2_CID_MODE_CLASS_BASE                (V4L2_CTRL_CLASS_MODE |
0x900)
#define V4L2_CID_MODE_CLASS                     (V4L2_CTRL_CLASS_MODE | 1)
#define V4L2_CID_MODE_FRAME_WIDTH               (V4L2_CID_MODE_CLASS_BASE+1)
#define V4L2_CID_MODE_FRAME_HEIGHT              (V4L2_CID_MODE_CLASS_BASE+2)
#define V4L2_CID_MODE_VISIBLE_WIDTH             (V4L2_CID_MODE_CLASS_BASE+3)
#define V4L2_CID_MODE_VISIBLE_HEIGHT            (V4L2_CID_MODE_CLASS_BASE+4)
#define V4L2_CID_MODE_PIXELCLOCK                (V4L2_CID_MODE_CLASS_BASE+5)
#define V4L2_CID_MODE_SENSITIVITY               (V4L2_CID_MODE_CLASS_BASE+6)
---

The pixel clock is read-only but some of the others should likely be
changeable.

Regards,

-- 
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com

  reply	other threads:[~2010-09-13 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09 18:51 [Query] Is there a spec to request video sensor information? Aguirre, Sergio
2010-09-13 15:27 ` Sakari Ailus [this message]
2010-09-13 17:06   ` Hans Verkuil
2010-09-16  9:40     ` Laurent Pinchart
2010-09-16 10:36       ` Hans Verkuil
2010-09-16 11:07         ` Laurent Pinchart

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=4C8E42F8.1080201@maxwell.research.nokia.com \
    --to=sakari.ailus@maxwell.research.nokia.com \
    --cc=iivanov@mm-sol.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=saaguirre@ti.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