From: Mathieu Poirier <mathieu.poirier@linaro.org> To: Md Danish Anwar <a0501179@ti.com> Cc: linux-kernel@vger.kernel.org, bjorn.andersson@linaro.org, krzysztof.kozlowski+dt@linaro.org, linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org, nm@ti.com, ssantosh@kernel.org, s-anna@ti.com, linux-arm-kernel@lists.infradead.org, rogerq@kernel.org, grygorii.strashko@ti.com, vigneshr@ti.com, kishon@ti.com, robh@kernel.org Subject: Re: [PATCH v5 6/6] remoteproc: pru: add support for configuring GPMUX based on client setup Date: Tue, 6 Sep 2022 13:29:49 -0600 [thread overview] Message-ID: <20220906192949.GA64477@p14s> (raw) In-Reply-To: <49d1959e-88ae-c605-aafc-ca9819c4f85c@ti.com> Good day, On Mon, Sep 05, 2022 at 02:41:27PM +0530, Md Danish Anwar wrote: > Hi Mathieu, > > On 19/07/22 21:46, Mathieu Poirier wrote: > > On Tue, Jun 07, 2022 at 10:26:50AM +0530, Puranjay Mohan wrote: > >> From: Tero Kristo <t-kristo@ti.com> > >> > >> Client device node property ti,pruss-gp-mux-sel can now be used to > >> configure the GPMUX config value for PRU. > >> > >> Signed-off-by: Tero Kristo <t-kristo@ti.com> > >> [s-anna@ti.com: simplify the pru id usage] > >> Signed-off-by: Suman Anna <s-anna@ti.com> > >> Signed-off-by: Puranjay Mohan <p-mohan@ti.com> > >> --- > >> V4->v5 > >> * This patch was included in v4 and had some checkpatch errors that have > >> been resolved in v5 > >> --- > >> drivers/remoteproc/pru_rproc.c | 20 ++++++++++++++++++++ > >> 1 file changed, 20 insertions(+) > >> > >> diff --git a/drivers/remoteproc/pru_rproc.c b/drivers/remoteproc/pru_rproc.c > >> index 2977eb50631b..f2c6c55f0f20 100644 > >> --- a/drivers/remoteproc/pru_rproc.c > >> +++ b/drivers/remoteproc/pru_rproc.c > >> @@ -123,6 +123,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; > >> @@ -141,6 +142,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) > >> @@ -250,6 +252,7 @@ struct rproc *pru_rproc_get(struct device_node *np, int index, > >> struct device *dev; > >> const char *fw_name; > >> int ret; > >> + u32 mux; > >> > >> try_module_get(THIS_MODULE); > >> > >> @@ -273,6 +276,22 @@ struct rproc *pru_rproc_get(struct device_node *np, int index, > >> > >> mutex_unlock(&pru->lock); > >> > >> + 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; > >> + } > >> + > >> + 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; > >> + } > >> + } > >> + > >> if (pru_id) > >> *pru_id = pru->id; > >> > >> @@ -310,6 +329,7 @@ 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); > >> > > > > CC drivers/remoteproc/pru_rproc.o > > /home/mpoirier/work/remoteproc/kernel-review/drivers/remoteproc/pru_rproc.c: In function ‘pru_rproc_get’: > > /home/mpoirier/work/remoteproc/kernel-review/drivers/remoteproc/pru_rproc.c:279:8: error: implicit declaration of function ‘pruss_cfg_get_gpmux’ [-Werror=implicit-function-declaration] > > 279 | ret = pruss_cfg_get_gpmux(pru->pruss, pru->id, &pru->gpmux_save); > > | ^~~~~~~~~~~~~~~~~~~ > > /home/mpoirier/work/remoteproc/kernel-review/drivers/remoteproc/pru_rproc.c:288:9: error: implicit declaration of function ‘pruss_cfg_set_gpmux’ [-Werror=implicit-function-declaration] > > 288 | ret = pruss_cfg_set_gpmux(pru->pruss, pru->id, mux); > > | ^~~~~~~~~~~~~~~~~~~ > > > > I get this on both rproc-next and today's linux next. > > This patch is dependent on the series [2] Introduce PRU platform consumer API > https://patchwork.kernel.org/project/linux-remoteproc/cover/20220406094358.7895-1-p-mohan@ti.com/ > as the api pruss_cfg_get_gpmux calls the api pruss_cfg_read and the api > pruss_cfg_set_gpmux calls the api pruss_cfg_update which are implemented by the > patch "soc: ti: pruss: Add pruss_cfg_read()/update() API" in the above series. > What I read from the cover letter is that the series you are referring to was an RFC that predated this series. Also from the cover letter, the second paragraph clearly indicate that two other series _depend_ on this series. As such there was no way for me to identify the dependency. > This error is coming as the dependent patch needs the patch "soc: ti: pruss: > Add pruss_cfg_read()/update() API" to be applied for compilation. Please provide a link when referencing patchsets. That way we know exactly which one we are talking about. > > Thanks, > Danish. > > > > >> mutex_lock(&pru->lock); > >> -- > >> 2.17.1 > >>
WARNING: multiple messages have this Message-ID (diff)
From: Mathieu Poirier <mathieu.poirier@linaro.org> To: Md Danish Anwar <a0501179@ti.com> Cc: nm@ti.com, devicetree@vger.kernel.org, grygorii.strashko@ti.com, vigneshr@ti.com, kishon@ti.com, linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org, bjorn.andersson@linaro.org, rogerq@kernel.org, krzysztof.kozlowski+dt@linaro.org, ssantosh@kernel.org, robh@kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v5 6/6] remoteproc: pru: add support for configuring GPMUX based on client setup Date: Tue, 6 Sep 2022 13:29:49 -0600 [thread overview] Message-ID: <20220906192949.GA64477@p14s> (raw) In-Reply-To: <49d1959e-88ae-c605-aafc-ca9819c4f85c@ti.com> Good day, On Mon, Sep 05, 2022 at 02:41:27PM +0530, Md Danish Anwar wrote: > Hi Mathieu, > > On 19/07/22 21:46, Mathieu Poirier wrote: > > On Tue, Jun 07, 2022 at 10:26:50AM +0530, Puranjay Mohan wrote: > >> From: Tero Kristo <t-kristo@ti.com> > >> > >> Client device node property ti,pruss-gp-mux-sel can now be used to > >> configure the GPMUX config value for PRU. > >> > >> Signed-off-by: Tero Kristo <t-kristo@ti.com> > >> [s-anna@ti.com: simplify the pru id usage] > >> Signed-off-by: Suman Anna <s-anna@ti.com> > >> Signed-off-by: Puranjay Mohan <p-mohan@ti.com> > >> --- > >> V4->v5 > >> * This patch was included in v4 and had some checkpatch errors that have > >> been resolved in v5 > >> --- > >> drivers/remoteproc/pru_rproc.c | 20 ++++++++++++++++++++ > >> 1 file changed, 20 insertions(+) > >> > >> diff --git a/drivers/remoteproc/pru_rproc.c b/drivers/remoteproc/pru_rproc.c > >> index 2977eb50631b..f2c6c55f0f20 100644 > >> --- a/drivers/remoteproc/pru_rproc.c > >> +++ b/drivers/remoteproc/pru_rproc.c > >> @@ -123,6 +123,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; > >> @@ -141,6 +142,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) > >> @@ -250,6 +252,7 @@ struct rproc *pru_rproc_get(struct device_node *np, int index, > >> struct device *dev; > >> const char *fw_name; > >> int ret; > >> + u32 mux; > >> > >> try_module_get(THIS_MODULE); > >> > >> @@ -273,6 +276,22 @@ struct rproc *pru_rproc_get(struct device_node *np, int index, > >> > >> mutex_unlock(&pru->lock); > >> > >> + 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; > >> + } > >> + > >> + 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; > >> + } > >> + } > >> + > >> if (pru_id) > >> *pru_id = pru->id; > >> > >> @@ -310,6 +329,7 @@ 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); > >> > > > > CC drivers/remoteproc/pru_rproc.o > > /home/mpoirier/work/remoteproc/kernel-review/drivers/remoteproc/pru_rproc.c: In function ‘pru_rproc_get’: > > /home/mpoirier/work/remoteproc/kernel-review/drivers/remoteproc/pru_rproc.c:279:8: error: implicit declaration of function ‘pruss_cfg_get_gpmux’ [-Werror=implicit-function-declaration] > > 279 | ret = pruss_cfg_get_gpmux(pru->pruss, pru->id, &pru->gpmux_save); > > | ^~~~~~~~~~~~~~~~~~~ > > /home/mpoirier/work/remoteproc/kernel-review/drivers/remoteproc/pru_rproc.c:288:9: error: implicit declaration of function ‘pruss_cfg_set_gpmux’ [-Werror=implicit-function-declaration] > > 288 | ret = pruss_cfg_set_gpmux(pru->pruss, pru->id, mux); > > | ^~~~~~~~~~~~~~~~~~~ > > > > I get this on both rproc-next and today's linux next. > > This patch is dependent on the series [2] Introduce PRU platform consumer API > https://patchwork.kernel.org/project/linux-remoteproc/cover/20220406094358.7895-1-p-mohan@ti.com/ > as the api pruss_cfg_get_gpmux calls the api pruss_cfg_read and the api > pruss_cfg_set_gpmux calls the api pruss_cfg_update which are implemented by the > patch "soc: ti: pruss: Add pruss_cfg_read()/update() API" in the above series. > What I read from the cover letter is that the series you are referring to was an RFC that predated this series. Also from the cover letter, the second paragraph clearly indicate that two other series _depend_ on this series. As such there was no way for me to identify the dependency. > This error is coming as the dependent patch needs the patch "soc: ti: pruss: > Add pruss_cfg_read()/update() API" to be applied for compilation. Please provide a link when referencing patchsets. That way we know exactly which one we are talking about. > > Thanks, > Danish. > > > > >> mutex_lock(&pru->lock); > >> -- > >> 2.17.1 > >> _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-06 19:30 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-07 4:56 [PATCH v5 0/6] Introduce PRU remoteproc consumer API Puranjay Mohan 2022-06-07 4:56 ` Puranjay Mohan 2022-06-07 4:56 ` [PATCH v5 1/6] dt-bindings: remoteproc: Add PRU consumer bindings Puranjay Mohan 2022-06-07 4:56 ` Puranjay Mohan 2022-07-19 16:17 ` Mathieu Poirier 2022-07-19 16:17 ` Mathieu Poirier 2022-06-07 4:56 ` [PATCH v5 2/6] remoteproc: pru: Add APIs to get and put the PRU cores Puranjay Mohan 2022-06-07 4:56 ` Puranjay Mohan 2022-07-12 17:59 ` Mathieu Poirier 2022-07-12 17:59 ` Mathieu Poirier 2022-07-14 17:20 ` Mathieu Poirier 2022-07-14 17:20 ` Mathieu Poirier 2022-07-15 6:22 ` Kishon Vijay Abraham I 2022-07-15 6:22 ` Kishon Vijay Abraham I 2022-09-02 9:39 ` Md Danish Anwar 2022-09-02 9:39 ` Md Danish Anwar 2022-09-06 19:28 ` Mathieu Poirier 2022-09-06 19:28 ` Mathieu Poirier 2022-09-07 9:24 ` Md Danish Anwar 2022-09-07 9:24 ` Md Danish Anwar 2022-09-12 13:24 ` Romain Naour 2022-09-12 13:24 ` Romain Naour 2022-09-13 11:40 ` Md Danish Anwar 2022-09-13 11:40 ` Md Danish Anwar 2022-09-19 20:45 ` Mathieu Poirier 2022-09-19 20:45 ` Mathieu Poirier 2022-09-26 10:23 ` [EXTERNAL] " Md Danish Anwar 2022-09-26 10:23 ` Md Danish Anwar 2022-09-29 23:02 ` Mathieu Poirier 2022-09-29 23:02 ` Mathieu Poirier 2022-06-07 4:56 ` [PATCH v5 3/6] remoteproc: pru: Make sysfs entries read-only for PRU client driven boots Puranjay Mohan 2022-06-07 4:56 ` Puranjay Mohan 2022-06-07 4:56 ` [PATCH v5 4/6] remoteproc: pru: Add pru_rproc_set_ctable() function Puranjay Mohan 2022-06-07 4:56 ` Puranjay Mohan 2022-07-19 15:53 ` Mathieu Poirier 2022-07-19 15:53 ` Mathieu Poirier 2022-06-07 4:56 ` [PATCH v5 5/6] remoteproc: pru: Configure firmware based on client setup Puranjay Mohan 2022-06-07 4:56 ` Puranjay Mohan 2022-06-07 4:56 ` [PATCH v5 6/6] remoteproc: pru: add support for configuring GPMUX " Puranjay Mohan 2022-06-07 4:56 ` Puranjay Mohan 2022-07-19 16:16 ` Mathieu Poirier 2022-07-19 16:16 ` Mathieu Poirier 2022-09-05 9:11 ` Md Danish Anwar 2022-09-05 9:11 ` Md Danish Anwar 2022-09-06 19:29 ` Mathieu Poirier [this message] 2022-09-06 19:29 ` Mathieu Poirier 2022-09-07 9:14 ` [EXTERNAL] " Md Danish Anwar 2022-09-07 9:14 ` Md Danish Anwar
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=20220906192949.GA64477@p14s \ --to=mathieu.poirier@linaro.org \ --cc=a0501179@ti.com \ --cc=bjorn.andersson@linaro.org \ --cc=devicetree@vger.kernel.org \ --cc=grygorii.strashko@ti.com \ --cc=kishon@ti.com \ --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=nm@ti.com \ --cc=robh@kernel.org \ --cc=rogerq@kernel.org \ --cc=s-anna@ti.com \ --cc=ssantosh@kernel.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.