From: Arnaud Pouliquen <arnaud.pouliquen@st.com> To: Bjorn Andersson <bjorn.andersson@linaro.org>, Ohad Ben-Cohen <ohad@wizery.com>, Mathieu Poirier <mathieu.poirier@linaro.org> Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, arnaud.pouliquen@st.com Subject: [RFC 10/18] remoteproc: Add capability to populate rproc subnode devices Date: Thu, 16 Apr 2020 18:13:23 +0200 [thread overview] Message-ID: <20200416161331.7606-11-arnaud.pouliquen@st.com> (raw) In-Reply-To: <20200416161331.7606-1-arnaud.pouliquen@st.com> Add the capability to add rproc sub nodes in device tree. Devices declared as rproc sub node will be probed before the remote firmware boot sequence. Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@st.com> --- drivers/remoteproc/remoteproc_core.c | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c index c9e07c53ed0c..75f84fd3bd60 100644 --- a/drivers/remoteproc/remoteproc_core.c +++ b/drivers/remoteproc/remoteproc_core.c @@ -1605,6 +1605,26 @@ static void rproc_crash_handler_work(struct work_struct *work) rproc_trigger_recovery(rproc); } +static int rproc_platform_populate(struct rproc *rproc) +{ + struct device *dev = rproc->dev.parent; + int ret; + + ret = of_platform_populate(dev->of_node, NULL, NULL, dev); + if (ret < 0) { + dev_err(dev, "failed to populate child devices (%d)\n", ret); + + goto depopulate; + } + + return 0; + +depopulate: + of_platform_depopulate(dev); + + return ret; +} + /** * rproc_boot() - boot a remote processor * @rproc: handle of a remote processor @@ -1629,6 +1649,10 @@ int rproc_boot(struct rproc *rproc) dev = &rproc->dev; + ret = rproc_platform_populate(rproc); + if (ret) + return ret; + ret = mutex_lock_interruptible(&rproc->lock); if (ret) { dev_err(dev, "can't lock rproc %s: %d\n", rproc->name, ret); @@ -1735,6 +1759,7 @@ void rproc_shutdown(struct rproc *rproc) rproc->table_ptr = NULL; out: mutex_unlock(&rproc->lock); + of_platform_depopulate(rproc->dev.parent); } EXPORT_SYMBOL(rproc_shutdown); -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Arnaud Pouliquen <arnaud.pouliquen@st.com> To: Bjorn Andersson <bjorn.andersson@linaro.org>, Ohad Ben-Cohen <ohad@wizery.com>, Mathieu Poirier <mathieu.poirier@linaro.org> Cc: <linux-remoteproc@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-stm32@st-md-mailman.stormreply.com>, <arnaud.pouliquen@st.com> Subject: [RFC 10/18] remoteproc: Add capability to populate rproc subnode devices Date: Thu, 16 Apr 2020 18:13:23 +0200 [thread overview] Message-ID: <20200416161331.7606-11-arnaud.pouliquen@st.com> (raw) Message-ID: <20200416161323.rMMhL4Gx0Yuhax2OVBJFI_1Xm6iixDNzA5p2vJQZDLU@z> (raw) In-Reply-To: <20200416161331.7606-1-arnaud.pouliquen@st.com> Add the capability to add rproc sub nodes in device tree. Devices declared as rproc sub node will be probed before the remote firmware boot sequence. Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@st.com> --- drivers/remoteproc/remoteproc_core.c | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c index c9e07c53ed0c..75f84fd3bd60 100644 --- a/drivers/remoteproc/remoteproc_core.c +++ b/drivers/remoteproc/remoteproc_core.c @@ -1605,6 +1605,26 @@ static void rproc_crash_handler_work(struct work_struct *work) rproc_trigger_recovery(rproc); } +static int rproc_platform_populate(struct rproc *rproc) +{ + struct device *dev = rproc->dev.parent; + int ret; + + ret = of_platform_populate(dev->of_node, NULL, NULL, dev); + if (ret < 0) { + dev_err(dev, "failed to populate child devices (%d)\n", ret); + + goto depopulate; + } + + return 0; + +depopulate: + of_platform_depopulate(dev); + + return ret; +} + /** * rproc_boot() - boot a remote processor * @rproc: handle of a remote processor @@ -1629,6 +1649,10 @@ int rproc_boot(struct rproc *rproc) dev = &rproc->dev; + ret = rproc_platform_populate(rproc); + if (ret) + return ret; + ret = mutex_lock_interruptible(&rproc->lock); if (ret) { dev_err(dev, "can't lock rproc %s: %d\n", rproc->name, ret); @@ -1735,6 +1759,7 @@ void rproc_shutdown(struct rproc *rproc) rproc->table_ptr = NULL; out: mutex_unlock(&rproc->lock); + of_platform_depopulate(rproc->dev.parent); } EXPORT_SYMBOL(rproc_shutdown); -- 2.17.1
next prev parent reply other threads:[~2020-04-16 16:13 UTC|newest] Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-16 16:13 [RFC 00/18] remoteproc: Decorelate virtio from core Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 01/18] remoteproc: Store resource table address in rvdev Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 02/18] remoteproc: Introduce virtio device add/remove functions in core Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-21 20:41 ` Mathieu Poirier 2020-04-22 12:30 ` Arnaud POULIQUEN 2020-04-22 12:30 ` Arnaud POULIQUEN 2020-04-22 16:57 ` Mathieu Poirier 2020-04-16 16:13 ` [RFC 03/18] remoteproc: Move rvdev management in rproc_virtio Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-21 22:18 ` Mathieu Poirier 2020-04-22 17:26 ` Mathieu Poirier 2020-04-16 16:13 ` [RFC 04/18] remoteproc: Add rproc_get_by_node helper Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 05/18] remoteproc: Create platform device for vdev Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 06/18] remoteproc: Add component in core for child devices synchronization Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 07/18] remoteproc: Add component bind/unbind for virtio platform Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 08/18] remoteproc: Externalize carveout functions Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 09/18] remoteproc: Move vring management from core to virtio Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen [this message] 2020-04-16 16:13 ` [RFC 10/18] remoteproc: Add capability to populate rproc subnode devices Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 11/18] remoteproc: Add child node component in rproc match list Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 12/18] remoteproc: Support of pre-registered virtio device Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 13/18] remoteproc: Add memory default allocator helper Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 14/18] remoteproc: Add pa to da translation API Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 15/18] remoteproc: associate memory entry to a device Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 16/18] remoteproc: Parse virtio node for memory region Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 17/18] remoteproc: stm32: Add the pa to da ops Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-16 16:13 ` [RFC 18/18] ARM: dts: stm32: Declare a virtio device Arnaud Pouliquen 2020-04-16 16:13 ` Arnaud Pouliquen 2020-04-23 17:26 ` [RFC 00/18] remoteproc: Decorelate virtio from core 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=20200416161331.7606-11-arnaud.pouliquen@st.com \ --to=arnaud.pouliquen@st.com \ --cc=bjorn.andersson@linaro.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-remoteproc@vger.kernel.org \ --cc=linux-stm32@st-md-mailman.stormreply.com \ --cc=mathieu.poirier@linaro.org \ --cc=ohad@wizery.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.