On Wed 13 June 2012 07:31:37 Scott Jiang wrote: > Hi Hans, > > > I would expect that the combination of v4l2_mbus_framefmt + v4l2_dv_timings > > gives you the information you need. > > > I can solve this problem in HD, but how about SD? Add a fake > dv_timings ops in SD decoder driver? > No, you add g/s_std instead. SD timings are set through that API. It is not so much that you give explicit timings, but that you give the SD standard. And from that you can derive the timings (i.e., one for 60 Hz formats, and one for 50 Hz formats). SD is handled through the ENUM/G/S/QUERYSTD API (userspace) and s/g/querystd (in the subdevice API). HD is handled through the ENUM/G/S/QUERY_DV_TIMINGS API and enum/g/s/query_dv_timings subdevice API. I've updated my cisco.git tree today and SD support is added to adv7842.c. Most of the other changes that I wanted to do are in there as well. It is not yet prime time, but it is getting close. Regards, Hans -- 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
