On Wed, Nov 24, 2010 at 3:25 PM, Stephen Warren <swarren@xxxxxxxxxx> wrote: >> Aside from said dependency loop, why does the dma code not handle >> clock enable/disable on it's own? > > That's what this change currently adds, although I asked whether the > clock should be blanket enabled at boot time like many other clocks. > > Or, do you mean that when initiating a new DMA, the code should enable > the clock if currently disabled, and later disable the clock after all > DMAs are complete (or some timeout thereafter), much like > nvhost_module_busy/powerdown_handler does for graphics? Yes. Pretty much every driver will enable the clock when it has work to do and disable it when idle. -Erik -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
