> Subject: [PATCH 11/13] remoteproc: Properly deal with detach request
> 
> This patch introduces the capability to detach a remote processor that has
> been attached to or booted by the remoteproc core.  For that to happen a
> rproc::ops::detach() operation need to be available.
> 
> Signed-off-by: Mathieu Poirier <mathieu.poir...@linaro.org>
> ---
>  drivers/remoteproc/remoteproc_cdev.c  | 6 ++++++
> drivers/remoteproc/remoteproc_sysfs.c | 6 ++++++
>  2 files changed, 12 insertions(+)
> 
> diff --git a/drivers/remoteproc/remoteproc_cdev.c
> b/drivers/remoteproc/remoteproc_cdev.c
> index d06f8d4919c7..3a3830e27050 100644
> --- a/drivers/remoteproc/remoteproc_cdev.c
> +++ b/drivers/remoteproc/remoteproc_cdev.c
> @@ -42,6 +42,12 @@ static ssize_t rproc_cdev_write(struct file *filp, const
> char __user *buf, size_
>                       return -EINVAL;
> 
>               ret = rproc_shutdown(rproc);
> +     } else if (!strncmp(cmd, "detach", len)) {
> +             if (rproc->state != RPROC_RUNNING &&
> +                 rproc->state != RPROC_ATTACHED)
> +                     return -EINVAL;
> +
> +             ret = rproc_detach(rproc);
>       } else {
>               dev_err(&rproc->dev, "Unrecognized option\n");
>               ret = -EINVAL;
> diff --git a/drivers/remoteproc/remoteproc_sysfs.c
> b/drivers/remoteproc/remoteproc_sysfs.c
> index 6134d2f083ce..013231f69837 100644
> --- a/drivers/remoteproc/remoteproc_sysfs.c
> +++ b/drivers/remoteproc/remoteproc_sysfs.c
> @@ -118,6 +118,12 @@ static ssize_t state_store(struct device *dev,
>                       return -EINVAL;
> 
>               ret = rproc_shutdown(rproc);
> +     } else if (sysfs_streq(buf, "detach")) {
> +             if (rproc->state != RPROC_RUNNING &&
> +                 rproc->state != RPROC_ATTACHED)
> +                     return -EINVAL;
> +
> +             ret = rproc_detach(rproc);
>       } else {
>               dev_err(&rproc->dev, "Unrecognised option: %s\n", buf);
>               ret = -EINVAL;
> --

Reviewed-by: Peng Fan <peng....@nxp.com>

Reply via email to