On Wed, 10 Sep 2014 17:57:23 +0100, Mark Brown <broonie@xxxxxxxxxx> wrote: > On Wed, Sep 10, 2014 at 05:29:32PM +0100, Grant Likely wrote: > > > What we can do is have an inhibit flag for > > simplefb/simpleuart/simplewhatever that holds off PM. When a real > > driver, or a stub that understands parsing the resource dependencies, > > takes ownership of the device (or userspace tells the kernel to stop > > caring) it can clear the inhibit. > > It's not quite as simple as just disabling PM - for example in the > clocks case we've also got to worry about what happens with rate changes > (which is going to get more and more risky as we get smarter about being > able to push configuration changes back up the tree), regulators have a > similar thing with voltage changes. With simple enables and disables we > have to worry about things like handling users who actively want to > power things on and and off but may potentially be sharing a resource > with an undeclared dependency. I think we can be okay with the above. This is a best-effort situation where we don't want to tear down how firmware has set up the board if it can be reasonably assumed that something depends on it (simplefb). However, if clocks or regulators are shared with other devices and those drivers ask for other settings, then there is simply no recourse. In that situation there must be a driver for the video device that takes care of any constraints. g. -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |