Hi Guennadia, 2012/9/27 Guennadi Liakhovetski <g.liakhovetski@xxxxxx>: > Currently soc-camera doesn't work with independently registered I2C client > devices, it has to register them itself. This patch adds support for such > configurations, in which case client drivers have to request deferred > probing until their host becomes available and enables the data interface. > > Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@xxxxxx> > --- it seems deferred probing for i2c camera sensors is a more workaround than a solution. currently, soc-camera-pdrv is the manager of the whole initilization flow. it all requires the host/client registerred and initilized synchronously. so that results in strange things like that we fill a i2c_board_info structure in arch/arm/mach-xxx but we never call anything like i2c_new_device() to add the i2c client in mach. because we need to do that in the soc-camera-pdrv driver to make all things happen orderly. but now after we move to DT, all i2c device will be registerred automatically by of_i2c_register_devices() in i2c_host 's probe, that makes the problem much worse and very urgent to get fixed. returning DEFERRED_PROBE error until getting the private data filled by the manager, indirectly, makes the things seem to be asynchronous, but essentially it is still synchronous because the overall timing line is still controller by soc-camera-pdrv. what about another possible way: we let all host and i2c client driver probed in any order, but let the final soc-camera-pdrv is the connection of all things. the situation of soc_camera is very similar with ALSA SoC. it turns out ASoC has done that very well. -barry -- 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
