Hi Omar On Wed, 22 Aug 2012, Omar Ramirez Luna wrote: > Some IP blocks might not be using/controlling more than one > reset line, this check loosens the restriction to fully use > hwmod framework for those drivers. > > E.g.: ipu has reset lines: mmu_cache, cpu0 and cpu1. > - As of now cpu1 is not used and hence (with previous check) the > IP block isn't fully enabled by hwmod code. > - Usually ipu and dsp processors configure their mmu module first > and then enable the processors, this involves: > * Deasserting mmu reset line, and enabling the module. > * Deasserting cpu0 reset line, and enabling the processor. > The ones portrayed in this example are controlled through > rproc_fw_boot in drivers/remoteproc/remoteproc_core.c > > While at it, prevent _omap4_module_disable if all the hardreset > lines on an IP block are not under reset. > > This will allow the driver to: > a. Deassert the reset line. > b. Enable the hwmod through runtime PM default callbacks. > c. Do its usecase. > d. Disable hwmod through runtime PM. > e. Assert the reset line. > > Signed-off-by: Omar Ramirez Luna <omar.luna@xxxxxxxxxx> Well, I don't think this is the right long-term solution, but I'd like to see this moving forward. So this one has been queued for 3.7. Hopefully we can figure out the right thing once the PRM driver is ready (which will handle the low-level hard resets). - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
