On Monday 30 March 2009 11:56:25 Daniel Glöckner wrote: > On 03/26/2009 04:08 PM, Hans Verkuil wrote: > > I've been working on a new framework for devices like this and almost > > all i2c v4l drivers are now converted to v4l2_subdev in our v4l-dvb > > tree. It will also be merged in 2.6.30. Please take a look at > > v4l2-framework.txt in the v4l-dvb repository for more information. > > > > I'm sure you will have questions later, please don't hesitate to ask! > > It's a recent development but very much needed. Otherwise we will end > > up with a lot of duplicate i2c drivers, each tied to their own platform > > or framework. That's clearly something we do not want. > > Hi Hans, > > the problem I see with the v4l2-framework in this case is that in its > current state it does not allow to exchange information regarding the bus > parameters between the sub device and the controller. What exactly do you need? If there is something missing, then it should be added. But my guess is that you can pass such information via the s_routing callback. That's what all other drivers that use v4l2_subdev do. > It seems the soc-camera framework is a better choice here, but to make it > work with the saa7121 one would first have to implement support for video > output. This framework will also be converted to use v4l2_subdev for the communication with i2c drivers. > What do you recommend? Actually, I recommend that you first look at the existing saa7127.c source. I don't know how many differences there are between the saa7121 and saa7127, but perhaps support for the saa7121 can be added there rather than introducing a new driver. Of course, that only works if the differences are not too big. 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
