Recent changes in omap_hwmod framework have reworked the behaviour
towards hardreset handling, commit 747834a (ARM: OMAP2+: hwmod:
revise hardreset behavior) recommends for drivers to implement
their own reset sequences until code out-of-tree hits mainline
and then their needs and code can be reviewed.
Since it is not clear when this will occur for all drivers and
hwmod code was not deleted (presumably because at some point it
will handle the resets once again), this series exports functions
to handle hardreset lines in an attempt to reduce code duplication
for those who have a common reset sequence.
These APIs are intended to be used by iommu for now, but were
tested with IPU and remoteproc on Pandaboard.
Omar Ramirez Luna (3):
ARM: OMAP: hwmod: partially un-reset hwmods might not be properly
enabled
ARM: OMAP: hwmod: revise deassert sequence
ARM: OMAP: omap_device: expose hwmod assert/deassert to omap devices
arch/arm/mach-omap2/omap_hwmod.c | 70 +++++++++++++++++++------
arch/arm/plat-omap/include/plat/omap_device.h | 4 ++
arch/arm/plat-omap/omap_device.c | 45 ++++++++++++++++
3 files changed, 103 insertions(+), 16 deletions(-)
--
1.7.4.1
--
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
