remoteproc/keystone: explicitly request exclusive reset control

Commit a53e35db70d1 ("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 <[email protected]>
Cc: Bjorn Andersson <[email protected]>
Cc: [email protected]
Acked-by: Suman Anna <[email protected]>
Signed-off-by: Philipp Zabel <[email protected]>
Signed-off-by: Bjorn Andersson <[email protected]>

diff --git a/drivers/remoteproc/keystone_remoteproc.c b/drivers/remoteproc/keystone_remoteproc.c
index 97abb0c8ad65c5ea4ab4fc141a03957284edd941..aaac31134e3952441dbc7a8260768f6f00540d22 100644 (file)
--- a/drivers/remoteproc/keystone_remoteproc.c
+++ b/drivers/remoteproc/keystone_remoteproc.c
@@ -410,7 +410,7 @@ static int keystone_rproc_probe(struct platform_device *pdev)
        if (ret)
                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)) {
                ret = PTR_ERR(ksproc->reset);
                goto free_rproc;