On Thu, May 09, 2013 at 05:39:03PM +0100, Grant Likely wrote: > +1. You can /minimize/ up-down cycles with the kind of optimization > that is being attempted here, but the driver still *must* deal with > bringing resources back up if they get requested "later than you would > otherwise like". Now that I think about it we should probably have a debug option like the shared IRQ testing one which does actually disable all resources as soon as the kernel gains control of them in order to help with test coverage for this.
Attachment:
signature.asc
Description: Digital signature
