Message ID | 20220411013656.2517150-1-chi.minghao@zte.com.cn (mailing list archive) |
---|---|
State | Accepted |
Headers | show |
Series | remoteproc: using pm_runtime_resume_and_get instead of pm_runtime_get_sync | expand |
On Mon, 11 Apr 2022 01:36:56 +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] remoteproc: using pm_runtime_resume_and_get instead of pm_runtime_get_sync commit: 3ebebb9a2d9a5c2d2b866739b50838dc152727fc Best regards,
diff --git a/drivers/remoteproc/keystone_remoteproc.c b/drivers/remoteproc/keystone_remoteproc.c index 54781f553f4e..594a9b43b7ae 100644 --- a/drivers/remoteproc/keystone_remoteproc.c +++ b/drivers/remoteproc/keystone_remoteproc.c @@ -410,10 +410,9 @@ static int keystone_rproc_probe(struct platform_device *pdev) /* enable clock for accessing DSP internal memories */ pm_runtime_enable(dev); - ret = pm_runtime_get_sync(dev); + ret = pm_runtime_resume_and_get(dev); if (ret < 0) { dev_err(dev, "failed to enable clock, status = %d\n", ret); - pm_runtime_put_noidle(dev); goto disable_rpm; }