On Friday 20 March 2009 00:55:20 Pete Eberlein wrote: > Hello Hans, > > I'm looking at converting the go7007 staging driver to use the subdev > API. Hoorah! :-) > I don't see any v4l2_subdev_video_ops for VIDIOC_S_INPUT nor > VIDIOC_S_STD. Were those overlooked, or should I use the generic > v4l2_subdev_core_ops->ioctl? (The chip in particular does not have a > tuner, but it does have multiple inputs (svidio, composite) and supports > NTSC or PAL.) S_STD exists, but it is in tuner_ops. I know, I know, that's the wrong place. I'll move it to video_ops once all conversions are done. S_INPUT must not be used in subdevices. S_INPUT deals with user-level inputs (e.g. "Composite", "S-Video", "Tuner"), not with the sub-device-level inputs/outputs (e.g. PIN-X, PIN-Y). Sub-devices know nothing about the user-level since that's a board-level informations. Sub-devices only know about their own input and output pins. The adapter driver is responsible for mapping an S_INPUT ioctl to video/s_routing and audio/s_routing subdev ops. These routing commands tell the sub-device on what pin(s) it receives its input data and what pin(s) are used for the output. What values you put in the v4l2_routing struct is sub-device dependent and is defined in the include/media/<subdev>.h header. Regards, Hans -- Hans Verkuil - video4linux developer - sponsored by TANDBERG -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
