public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "ribrishimov" <ribrishimov@mm-sol.com>
To: "'Tuukka.O Toivonen'" <tuukka.o.toivonen@nokia.com>
Cc: <camera@ok.research.nokia.com>, <linux-media@vger.kernel.org>,
	"'ext Hans Verkuil'" <hverkuil@xs4all.nl>
Subject: RE: [Camera] identifying camera sensor
Date: Wed, 4 Mar 2009 16:43:36 +0200	[thread overview]
Message-ID: <011401c99cd7$9d20bd40$020014ac@ribrishimov> (raw)
In-Reply-To: <200903041612.54557.tuukka.o.toivonen@nokia.com>

Hi,

Some sensor ID is definitely needed at least for Camera daemon and iCapture
to load the appropriate tuning data.

Ivan can comment which the preferable approach.

Best regards,

RADO

-----Original Message-----
From: camera-bounces@ok.research.nokia.com
[mailto:camera-bounces@ok.research.nokia.com] On Behalf Of Tuukka.O Toivonen
Sent: Wednesday, March 04, 2009 4:13 PM
To: ext Hans Verkuil
Cc: camera@ok.research.nokia.com; linux-media@vger.kernel.org
Subject: [Camera] identifying camera sensor

Hi,

I am writing a generic driver for SMIA-compatible sensors.
SMIA-sensors have registers containing:
  u16 model_id
  u16 revision_number
  u8 manufacturer_id
which could be used to detect the sensor.
However, since the driver is generic, it is not interested
of these values.

Nevertheless, in some cases user space applications want
to know the exact chip. For example, to get the highest
possible image quality, user space application might capture
an image and postprocess it using sensor-specific filtering
algorithms (which don't belong into kernel driver).

I am planning to export the chip identification information
to user space using VIDIOC_DBG_G_CHIP_IDENT.
Here's a sketch:
  #define V4L2_IDENT_SMIA_BASE	(0x53 << 24)
then in sensor driver's VIDIOC_DBG_G_CHIP_IDENT ioctl handler:
  struct v4l2_dbg_chip_ident id;
  id.ident = V4L2_IDENT_SMIA_BASE | (manufacturer_id << 16) | model_id;
  id.revision = revision_number;

Do you think this is acceptable?

Alternatively, VIDIOC_QUERYCAP could be used to identify the sensor.
Would it make more sense if it would return something like
  capability.card:  `omap3/smia-sensor-12-1234-5678//'
where 12 would be manufacturer_id, 1234 model_id, and
5678 revision_number?

I'll start writing a patch as soon as you let me know
which would be the best alternative. Thanks!

- Tuukka
_______________________________________________
Camera mailing list
Camera@ok.research.nokia.com
http://ok.research.nokia.com/cgi-bin/mailman/listinfo/camera


  reply	other threads:[~2009-03-04 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04 14:12 identifying camera sensor Tuukka.O Toivonen
2009-03-04 14:43 ` ribrishimov [this message]
2009-03-04 23:00   ` [Camera] " Trent Piepho
2009-03-05  0:42 ` DongSoo(Nathaniel) Kim

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='011401c99cd7$9d20bd40$020014ac@ribrishimov' \
    --to=ribrishimov@mm-sol.com \
    --cc=camera@ok.research.nokia.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=tuukka.o.toivonen@nokia.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