On Mon, 29 Aug 2011, Laurent Pinchart wrote: [snip] > My idea was to let the kernel register all devices based on the DT or board > code. When the V4L2 host/bridge driver gets registered, it will then call a > V4L2 core function with a list of subdevs it needs. The V4L2 core would store > that information and react to bus notifier events to notify the V4L2 > host/bridge driver when all subdevs are present. At that point the host/bridge > driver will get hold of all the subdevs and call (probably through the V4L2 > core) their .registered operation. That's where the subdevs will get access to > their clock using clk_get(). Correct me, if I'm wrong, but this seems to be the case of sensor (and other i2c-client) drivers having to succeed their probe() methods without being able to actually access the hardware? Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer http://www.open-technology.de/ -- 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
