Commit f5f98654 authored by Philipp Zabel's avatar Philipp Zabel Committed by Bjorn Andersson

remoteproc/keystone: explicitly request exclusive reset control

Commit a53e35db ("reset: Ensure drivers are explicit when requesting
reset lines") started to transition the reset control request API calls
to explicitly state whether the driver needs exclusive or shared reset
control behavior. Convert all drivers requesting exclusive resets to the
explicit API call so the temporary transition helpers can be removed.

No functional changes.

Cc: Ohad Ben-Cohen <ohad@wizery.com>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: linux-remoteproc@vger.kernel.org
Acked-by: default avatarSuman Anna <s-anna@ti.com>
Signed-off-by: default avatarPhilipp Zabel <p.zabel@pengutronix.de>
Signed-off-by: default avatarBjorn Andersson <bjorn.andersson@linaro.org>
parent b4daf890
...@@ -410,7 +410,7 @@ static int keystone_rproc_probe(struct platform_device *pdev) ...@@ -410,7 +410,7 @@ static int keystone_rproc_probe(struct platform_device *pdev)
if (ret) if (ret)
goto free_rproc; goto free_rproc;
ksproc->reset = devm_reset_control_get(dev, NULL); ksproc->reset = devm_reset_control_get_exclusive(dev, NULL);
if (IS_ERR(ksproc->reset)) { if (IS_ERR(ksproc->reset)) {
ret = PTR_ERR(ksproc->reset); ret = PTR_ERR(ksproc->reset);
goto free_rproc; goto free_rproc;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment