Re: question about SoC Camera driver (Micron)

[Guennadi Liakhovetski <g.liakhovetski@xxxxxx>]

On Thu, 15 May 2008, Darius wrote:

> Guennadi, can you please describe more detailed struct soc_camera_device
> structure? All these members xmin, ymin, etc...

The main point is, that the unit is 1 pixel. The rest is pretty much 
implementation specific. Just see your datasheet and select some natural 
values for allowed frame sizes and location. As the struct declaration 
says:

	unsigned short width;		/* Current window */
	unsigned short height;		/* sizes */
	unsigned short x_min;		/* Camera capabilities */
	unsigned short y_min;
	unsigned short x_current;	/* Current window location */
	unsigned short y_current;

The vales below are again min and max allowed values.

	unsigned short width_min;
	unsigned short width_max;
	unsigned short height_min;
	unsigned short height_max;

This is just to skip a few lines at the top, in case they are always 
corrupted, as was the case with Micron cameras. Soon there should be ab 
extra x_skip_left parameter.

	unsigned short y_skip_top;	/* Lines to skip at the top */

These are current gain and exposure values again. I selected them scaled 
to some more or less natural for humans ranges. See arrays of struct 
v4l2_queryctrl in mt9m001.c and mt9v022.c for examples

	unsigned short gain;
	unsigned short exposure;

> Also soc_camera_data_format structure has member depht. Should this member fit
> sensor bus bit count or pixel format depht in videodev2.h?
> Because most pixel formats are 16 bit and camera sensor interface in most
> cases is 8 bit.

This is pixel format bit-depth, as provided by the sensor.

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer

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