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 additional code in the separate file in the mach-omap2 layer.
Showing the changes to include/linux (1 of 1 file). Show all
Unified · Split
| @@ -13,6 +13,8 @@ struct iommu_platform_data { · 12 unmodified lines | ||
| 13 | 13 | const char *reset_name; |
| 14 | 14 | int (*assert_reset)(struct platform_device *pdev, const char *name); |
| 15 | 15 | int (*deassert_reset)(struct platform_device *pdev, const char *name); |
| 16 | + int (*device_enable)(struct platform_device *pdev); | |
| 17 | + int (*device_idle)(struct platform_device *pdev); | |
| 16 | 18 | int (*set_pwrdm_constraint)(struct platform_device *pdev, bool request, |
| 17 | 19 | u8 *pwrst); |
| 18 | 20 | }; |