On 07/23/2012 02:14 PM, Mark Brown wrote: > On Wed, Jul 18, 2012 at 07:00:15PM +0200, Sylwester Nawrocki wrote: > >> One possible solution would be to have host/bridge drivers to register >> a clkdev entry for I2C client device, so it can acquire the clock through >> just clk_get(). We would have to ensure the clock is not tried to be >> accessed before it is registered by a bridge. This would require to add >> clock handling code to all sensor/encoder subdev drivers though.. > > If this is done well it could just be a simple callback, and we could > probably arrange for the framework to just implement the default > behaviour if the driver doesn't do anything explicit. I agree, if a clock is bound to a sub-device beforehand it could probably be done with just a callback as well. Implementing default behaviour at the framework makes a lot of sense too, it could ease the conversion process significantly. > Of couse this is one of those things where we really need the generic > clock API to be generally available... Indeed, I hope it won't take too much time before at least some of the platforms get converted. -- Thanks, Sylwester -- 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
