On Tue, Sep 17, 2013 at 01:07:37PM +0200, Sylwester Nawrocki wrote: > On 09/16/2013 10:47 AM, Mika Westerberg wrote: > > I'm actually thinking that it is probably better now if we don't touch the > > client runtime PM at all in the I2C core. > > > > I proposed a less intrusive solution in this same thread where we power the > > I2C controller briefly at the client ->probe() (In order to have all the > > ACPI power resources etc. and the controller on) and let the client driver > > handle their own runtime PM as they do currently. > > > > Do you think that would work better wrt. fimc-isp-i2c driver? > > That would be no different for this particular driver, as long as the > I2C bus controller is activated right before the I2C client's probe(). Rafael pointed out that we can use ->ignore_children for the I2C adapter device for everything else than ACPI devices. That should keep the existing behavior. For ACPI devices we don't set that flag and the runtime PM core will activate the adapter whenever we try to power on I2C client device. This will make ACPI happy as well. If there are no objections, I'm going to send a new version based on the above. Thanks everyone for valuable input :) -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
