Message ID | 20220418105508.2558696-1-chi.minghao@zte.com.cn (mailing list archive) |
---|---|
State | Accepted |
Headers | show |
Series | hwspinlock: using pm_runtime_resume_and_get instead of pm_runtime_get_sync | expand |
On Mon, 18 Apr 2022 10:55:08 +0000, cgel.zte@gmail.com wrote: > From: Minghao Chi <chi.minghao@zte.com.cn> > > Using pm_runtime_resume_and_get is more appropriate > for simplifing code > > Applied, thanks! [1/1] hwspinlock: using pm_runtime_resume_and_get instead of pm_runtime_get_sync commit: 0e01d176d5788f66dc64a7e61119edb56eb08339 Best regards,
diff --git a/drivers/hwspinlock/omap_hwspinlock.c b/drivers/hwspinlock/omap_hwspinlock.c index 33eeff94fc2a..1fb3a2550e29 100644 --- a/drivers/hwspinlock/omap_hwspinlock.c +++ b/drivers/hwspinlock/omap_hwspinlock.c @@ -94,11 +94,9 @@ static int omap_hwspinlock_probe(struct platform_device *pdev) * the module SYSSTATUS register */ pm_runtime_enable(&pdev->dev); - ret = pm_runtime_get_sync(&pdev->dev); - if (ret < 0) { - pm_runtime_put_noidle(&pdev->dev); + ret = pm_runtime_resume_and_get(&pdev->dev); + if (ret < 0) goto runtime_err; - } /* Determine number of locks */ i = readl(io_base + SYSSTATUS_OFFSET);