Le Monday 22 September 2008 19:50:25 Erik Andrén, vous avez écrit :
> Hi,
> I've begun the working investigating the possibility of converting the
> m5602 driver to the gspca framework.
> I currently have the following questions:
> 1) From my understanding each driver implementing the gspca framework
> has a static list of v4l2 controls. In the m5602 driver, each sensor has
> its own set of v4l2 controls with different resolutions.
> Is there a obious solution to this problem?
>
> 2) In the sd_desc struct, is it necessary to implement the dq_callback
> or does the gspca driver automagically requeue buffers?
>
> Thanks,
> Erik
>
1)
Use a switch ?? Where/what is the problem??
Controls existing for one resolution but not other
resolution?
2)
No! it is optional, and is not intended to dequeue
but just inform your subdriver in case it needs to
add particular operations *in its scope*.
/* subdriver description */
struct sd_desc {
/* information */
const char *name; /* sub-driver name */
/* controls */
const struct ctrl *ctrls;
int nctrls;
/* mandatory operations */
cam_cf_op config; /* called on probe */
cam_op init; /* called on probe and resume */
cam_v_op start; /* called on stream on */
cam_pkt_op pkt_scan;
/* optional operations */
cam_v_op stopN; /* called on stream off - main alt */
cam_v_op stop0; /* called on stream off - alt 0 */
cam_v_op dq_callback; /* called when a frame has been dequeued */
cam_jpg_op get_jcomp;
cam_jpg_op set_jcomp;
cam_qmnu_op querymenu;
};
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
M560x-driver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/m560x-driver-devel
