Hi, --- On 21/4/09, Guennadi Liakhovetski <g.liakhovetski@xxxxxx> wrote: > Video (sub)devices, connecting to SoCs over generic i2c busses cannot > provide a pointer to struct v4l2_device in i2c-adapter driver_data, and > provide their own i2c_board_info data, including a platform_data field. > Add a v4l2_i2c_new_dev_subdev() API function that does exactly the same > as v4l2_i2c_new_subdev() but uses different parameters, and make > v4l2_i2c_new_subdev() a wrapper around it. [snip] I am wondering about this ongoing effort and its pursued goal: is it to hierarchize the v4l architecture, adding new abstraction levels? If so, what for? To me, as an eventual driver developer, this makes it harder to integrate my own drivers, as I use I2C and V4L in my system but I don't want them to be tightly coupled. Of course I can ignore this "subdev" stuff and just link against soc-camera which is what I need, and manage I2C without V4L knowing about it. Which is what I do. So, which is the point I am missing? Regards, --Agustín. -- Agustin Ferrin Pozuelo Embedded Systems Consultant http://embedded.ferrin.org Tel. +34 610502587 -- 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
