From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: MD Danish Anwar <danishanwar@ti.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org,
srk@ti.com, rogerq@kernel.org, vigneshr@ti.com
Subject: Re: [PATCH] remoteproc: pru: add support for configuring GPMUX based on client setup
Date: Mon, 21 Aug 2023 15:21:56 -0600 [thread overview]
Message-ID: <ZOPVdFMmUxT+wp8n@p14s> (raw)
In-Reply-To: <20230802064925.1895750-1-danishanwar@ti.com>
On Wed, Aug 02, 2023 at 12:19:25PM +0530, MD Danish Anwar wrote:
> From: Tero Kristo <t-kristo@ti.com>
>
> The GPMUX config value for a PRU device can now be configured by client
> by specifying it in the device node ti,pruss-gp-mux-sel.
>
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> Signed-off-by: Suman Anna <s-anna@ti.com>
> Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
> ---
> drivers/remoteproc/pru_rproc.c | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
Applied.
Thanks,
Mathieu
> diff --git a/drivers/remoteproc/pru_rproc.c b/drivers/remoteproc/pru_rproc.c
> index 5b2dc75836fc..327f0c7ee3d6 100644
> --- a/drivers/remoteproc/pru_rproc.c
> +++ b/drivers/remoteproc/pru_rproc.c
> @@ -110,6 +110,7 @@ struct pru_private_data {
> * @dbg_single_step: debug state variable to set PRU into single step mode
> * @dbg_continuous: debug state variable to restore PRU execution mode
> * @evt_count: number of mapped events
> + * @gpmux_save: saved value for gpmux config
> */
> struct pru_rproc {
> int id;
> @@ -128,6 +129,7 @@ struct pru_rproc {
> u32 dbg_single_step;
> u32 dbg_continuous;
> u8 evt_count;
> + u8 gpmux_save;
> };
>
> static inline u32 pru_control_read_reg(struct pru_rproc *pru, unsigned int reg)
> @@ -229,6 +231,7 @@ struct rproc *pru_rproc_get(struct device_node *np, int index,
> struct device *dev;
> const char *fw_name;
> int ret;
> + u32 mux;
>
> rproc = __pru_rproc_get(np, index);
> if (IS_ERR(rproc))
> @@ -253,6 +256,23 @@ struct rproc *pru_rproc_get(struct device_node *np, int index,
> if (pru_id)
> *pru_id = pru->id;
>
> + ret = pruss_cfg_get_gpmux(pru->pruss, pru->id, &pru->gpmux_save);
> + if (ret) {
> + dev_err(dev, "failed to get cfg gpmux: %d\n", ret);
> + goto err;
> + }
> +
> + /* An error here is acceptable for backward compatibility */
> + ret = of_property_read_u32_index(np, "ti,pruss-gp-mux-sel", index,
> + &mux);
> + if (!ret) {
> + ret = pruss_cfg_set_gpmux(pru->pruss, pru->id, mux);
> + if (ret) {
> + dev_err(dev, "failed to set cfg gpmux: %d\n", ret);
> + goto err;
> + }
> + }
> +
> ret = of_property_read_string_index(np, "firmware-name", index,
> &fw_name);
> if (!ret) {
> @@ -291,6 +311,8 @@ void pru_rproc_put(struct rproc *rproc)
>
> pru = rproc->priv;
>
> + pruss_cfg_set_gpmux(pru->pruss, pru->id, pru->gpmux_save);
> +
> pru_rproc_set_firmware(rproc, NULL);
>
> mutex_lock(&pru->lock);
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-08-21 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 6:49 [PATCH] remoteproc: pru: add support for configuring GPMUX based on client setup MD Danish Anwar
2023-08-21 21:21 ` Mathieu Poirier [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-01 10:59 MD Danish Anwar
2023-06-05 17:26 ` Mathieu Poirier
2023-06-05 20:45 ` Nishanth Menon
2023-06-07 14:35 ` Mathieu Poirier
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=ZOPVdFMmUxT+wp8n@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=danishanwar@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=rogerq@kernel.org \
--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