tis 2014-08-26 klockan 15:53 +0200 skrev Maxime Ripard: > > it should be fixed at the root. So a much better solution would be to > > establish a way for firmware to communicate to the kernel that a given > > resource has been enabled by firmware and shouldn't be disabled. Such a > > solution can be implement for all types of resources and can be reused > > by all drivers since they don't have to worry about these details. > > Mike Turquette repeatedly said that he was against such a DT property: > https://lkml.org/lkml/2014/5/12/693 And not really what we want here. The clocks should be turned off if not in use, i.e. when simplefb is unbound from the device and no other driver has taken over. Maybe even in the case where there is no simplefb driver in-kernel, but if the use case is to be generalized then this kind of resources need to be held until explicitly released to allow resources to be held until their driver is loaded, which may happen long after kernel bootup. But again, for many use cases it is a virtual hardware property, not really hardware in it's own but still smells a lot like hardware. These parameters is only valid until the hardware have been reconfigured. Regards Henrik -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
