devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@kernel.org>
To: MD Danish Anwar <danishanwar@ti.com>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: Suman Anna <s-anna@ti.com>, "Andrew F . Davis" <afd@ti.com>,
	nm@ti.com, vigneshr@ti.com, srk@ti.com,
	linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 5/5] remoteproc: pru: Configure firmware based on client setup
Date: Fri, 4 Nov 2022 15:02:59 +0200	[thread overview]
Message-ID: <0f9dbaa5-10b8-1126-6df9-e87e81d3abac@kernel.org> (raw)
In-Reply-To: <20221031073801.130541-6-danishanwar@ti.com>



On 31/10/2022 09:38, MD Danish Anwar wrote:
> From: Tero Kristo <t-kristo@ti.com>
> 
> Client device node property firmware-name is now used to configure
> firmware for the PRU instances. The default firmware is also
> restored once releasing the PRU resource.
> 
> Co-developed-by: Suman Anna <s-anna@ti.com>
> Signed-off-by: Suman Anna <s-anna@ti.com>
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> Co-developed-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
> Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
> Signed-off-by: Puranjay Mohan <p-mohan@ti.com>
> Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
> ---
>  drivers/remoteproc/pru_rproc.c | 34 ++++++++++++++++++++++++++++++++++
>  1 file changed, 34 insertions(+)
> 
> diff --git a/drivers/remoteproc/pru_rproc.c b/drivers/remoteproc/pru_rproc.c
> index 3d1870e6b13b..15ffaeddd963 100644
> --- a/drivers/remoteproc/pru_rproc.c
> +++ b/drivers/remoteproc/pru_rproc.c
> @@ -172,6 +172,23 @@ void pru_control_set_reg(struct pru_rproc *pru, unsigned int reg,
>  	spin_unlock_irqrestore(&pru->rmw_lock, flags);
>  }
>  
> +/**
> + * pru_rproc_set_firmware() - set firmware for a pru core

s/pru/PRU

> + * @rproc: the rproc instance of the PRU
> + * @fw_name: the new firmware name, or NULL if default is desired
> + *
> + * Return: 0 on success, or errno in error case.
> + */
> +static int pru_rproc_set_firmware(struct rproc *rproc, const char *fw_name)
> +{
> +	struct pru_rproc *pru = rproc->priv;
> +
> +	if (!fw_name)
> +		fw_name = pru->fw_name;
> +
> +	return rproc_set_firmware(rproc, fw_name);
> +}
> +
>  static struct rproc *__pru_rproc_get(struct device_node *np, int index)
>  {
>  	struct rproc *rproc;
> @@ -230,6 +247,7 @@ struct rproc *pru_rproc_get(struct device_node *np, int index,
>  	struct rproc *rproc;
>  	struct pru_rproc *pru;
>  	struct device *dev;
> +	const char *fw_name;
>  	int ret;
>  
>  	rproc = __pru_rproc_get(np, index);
> @@ -256,11 +274,25 @@ struct rproc *pru_rproc_get(struct device_node *np, int index,
>  	if (pru_id)
>  		*pru_id = pru->id;
>  
> +	ret = of_property_read_string_index(np, "firmware-name", index,
> +					    &fw_name);
> +	if (!ret) {
> +		ret = pru_rproc_set_firmware(rproc, fw_name);
> +		if (ret) {
> +			dev_err(dev, "failed to set firmware: %d\n", ret);
> +			goto err;
> +		}
> +	}
> +
>  	return rproc;
>  
>  err_no_rproc_handle:
>  	rproc_put(rproc);
>  	return ERR_PTR(ret);
> +
> +err:
> +	pru_rproc_put(rproc);
> +	return ERR_PTR(ret);
>  }
>  EXPORT_SYMBOL_GPL(pru_rproc_get);
>  
> @@ -280,6 +312,8 @@ void pru_rproc_put(struct rproc *rproc)
>  
>  	pru = rproc->priv;
>  
> +	pru_rproc_set_firmware(rproc, NULL);
> +
>  	mutex_lock(&pru->lock);
>  
>  	if (!pru->client_np) {

Reviewed-by: Roger Quadros <rogerq@kernel.org>

--
cheers,
-roger

      reply	other threads:[~2022-11-04 13:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  7:37 [PATCH v7 0/5] Introduce PRU remoteproc consumer API MD Danish Anwar
2022-10-31  7:37 ` [PATCH v7 1/5] dt-bindings: remoteproc: Add PRU consumer bindings MD Danish Anwar
2022-11-02 14:08   ` Rob Herring
2022-10-31  7:37 ` [PATCH v7 2/5] remoteproc: pru: Add APIs to get and put the PRU cores MD Danish Anwar
2022-11-04 12:55   ` Roger Quadros
2022-11-08 10:08     ` [EXTERNAL] " Md Danish Anwar
2022-11-08 13:25       ` Roger Quadros
2022-11-15  5:53     ` Md Danish Anwar
2022-11-15  8:34       ` Roger Quadros
2022-11-14 20:50   ` Mathieu Poirier
2022-11-15  5:59     ` Md Danish Anwar
2022-11-15 18:28       ` Mathieu Poirier
2022-10-31  7:37 ` [PATCH v7 3/5] remoteproc: pru: Make sysfs entries read-only for PRU client driven boots MD Danish Anwar
2022-11-04 12:57   ` Roger Quadros
2022-10-31  7:38 ` [PATCH v7 4/5] remoteproc: pru: Add pru_rproc_set_ctable() function MD Danish Anwar
2022-10-31  7:38 ` [PATCH v7 5/5] remoteproc: pru: Configure firmware based on client setup MD Danish Anwar
2022-11-04 13:02   ` Roger Quadros [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0f9dbaa5-10b8-1126-6df9-e87e81d3abac@kernel.org \
    --to=rogerq@kernel.org \
    --cc=afd@ti.com \
    --cc=danishanwar@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=s-anna@ti.com \
    --cc=srk@ti.com \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).