summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 1c59fb5)
raw | patch | inline | side by side (parent: 1c59fb5)
author | Suman Anna <s-anna@ti.com> | |
Mon, 27 Apr 2015 22:26:21 +0000 (17:26 -0500) | ||
committer | Suman Anna <s-anna@ti.com> | |
Sun, 17 May 2015 17:43:54 +0000 (12:43 -0500) |
Add two new platform data ops to allow the OMAP iommu driver to
be able to invoke the omap_device_enable and omap_device_idle
from within the driver. These are being added to streamline the
sequence between managing the hard reset lines and the clocks
during the suspend path, as the default device pm_domain callback
sequences in omap_device layer are not conducive for the OMAP
IOMMU driver.
This could have been done by expanding the existing pdata ops
for reset management (like in the OMAP remoteproc driver), but
this was chosen to avoid adding new code in a separate file in
the mach-omap2 layer.
Signed-off-by: Suman Anna <s-anna@ti.com>
be able to invoke the omap_device_enable and omap_device_idle
from within the driver. These are being added to streamline the
sequence between managing the hard reset lines and the clocks
during the suspend path, as the default device pm_domain callback
sequences in omap_device layer are not conducive for the OMAP
IOMMU driver.
This could have been done by expanding the existing pdata ops
for reset management (like in the OMAP remoteproc driver), but
this was chosen to avoid adding new code in a separate file in
the mach-omap2 layer.
Signed-off-by: Suman Anna <s-anna@ti.com>
include/linux/platform_data/iommu-omap.h | patch | blob | history |
index 5b429c43a29778ae9b9fb8b545599c2464a736c7..8aec9172822cbbea6fb1069d6fa9a84b7238342c 100644 (file)
int (*assert_reset)(struct platform_device *pdev, const char *name);
int (*deassert_reset)(struct platform_device *pdev, const char *name);
+ int (*device_enable)(struct platform_device *pdev);
+ int (*device_idle)(struct platform_device *pdev);
};