devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Griffin <peter.griffin@linaro.org>
To: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel@stlinux.com,
	vinod.koul@intel.com, patrice.chotard@st.com,
	bjorn.andersson@linaro.org, ohad@wizery.com
Cc: peter.griffin@linaro.org, lee.jones@linaro.org,
	dmaengine@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH v6 18/18] remoteproc: core: Retry rproc_fw_config_virtio() if !rproc->table_ptr
Date: Wed,  6 Jul 2016 09:54:36 +0100	[thread overview]
Message-ID: <1467795276-21725-19-git-send-email-peter.griffin@linaro.org> (raw)
In-Reply-To: <1467795276-21725-1-git-send-email-peter.griffin@linaro.org>

When rproc drivers are built-in the async firmware load done by rproc_add()
can fail due to the firmware not being present. Subsqeuent calls to
rproc_fw_boot() then fail, even though by this point firmware has been
successfully obtained.

This patch changes the behaviour to re-execute rproc_fw_config_virtio()
in rproc_fw_boot() if it has previously failed, and we are sure it is
now available.

Signed-off-by: Peter Griffin <peter.griffin@linaro.org>
---
 drivers/remoteproc/remoteproc_core.c     | 25 +++++++++++++++++++------
 drivers/remoteproc/remoteproc_internal.h |  3 +++
 2 files changed, 22 insertions(+), 6 deletions(-)

diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
index db3958b..749f261 100644
--- a/drivers/remoteproc/remoteproc_core.c
+++ b/drivers/remoteproc/remoteproc_core.c
@@ -801,8 +801,12 @@ static int rproc_fw_boot(struct rproc *rproc, const struct firmware *fw)
 	struct resource_table *table, *loaded_table;
 	int ret, tablesz;
 
+	/*
+	 * This can happen when built-in if initial async fw load fails.
+	 * However we now have firmware available so retry.
+	 */
 	if (!rproc->table_ptr)
-		return -ENOMEM;
+		rproc_fw_config_virtio(fw, rproc);
 
 	ret = rproc_fw_sanity_check(rproc, fw);
 	if (ret)
@@ -895,9 +899,20 @@ clean_up:
  * to unregister the device. one other option is just to use kref here,
  * that might be cleaner).
  */
-static void rproc_fw_config_virtio(const struct firmware *fw, void *context)
+
+static void rproc_fw_config_virtio_cb(const struct firmware *fw, void *context)
 {
 	struct rproc *rproc = context;
+
+	rproc_fw_config_virtio(fw, rproc);
+
+	release_firmware(fw);
+	/* allow rproc_del() contexts, if any, to proceed */
+	complete_all(&rproc->firmware_loading_complete);
+}
+
+static void rproc_fw_config_virtio(const struct firmware *fw, struct rproc *rproc)
+{
 	struct resource_table *table;
 	int ret, tablesz;
 
@@ -934,9 +949,7 @@ static void rproc_fw_config_virtio(const struct firmware *fw, void *context)
 	ret = rproc_handle_resources(rproc, tablesz, rproc_vdev_handler);
 
 out:
-	release_firmware(fw);
-	/* allow rproc_del() contexts, if any, to proceed */
-	complete_all(&rproc->firmware_loading_complete);
+	return;
 }
 
 static int rproc_add_virtio_devices(struct rproc *rproc)
@@ -956,7 +969,7 @@ static int rproc_add_virtio_devices(struct rproc *rproc)
 	 */
 	ret = request_firmware_nowait(THIS_MODULE, FW_ACTION_HOTPLUG,
 				      rproc->firmware, &rproc->dev, GFP_KERNEL,
-				      rproc, rproc_fw_config_virtio);
+				      rproc, rproc_fw_config_virtio_cb);
 	if (ret < 0) {
 		dev_err(&rproc->dev, "request_firmware_nowait err: %d\n", ret);
 		complete_all(&rproc->firmware_loading_complete);
diff --git a/drivers/remoteproc/remoteproc_internal.h b/drivers/remoteproc/remoteproc_internal.h
index 57e1de5..39916c1 100644
--- a/drivers/remoteproc/remoteproc_internal.h
+++ b/drivers/remoteproc/remoteproc_internal.h
@@ -49,6 +49,9 @@ struct rproc_fw_ops {
 void rproc_release(struct kref *kref);
 irqreturn_t rproc_vq_interrupt(struct rproc *rproc, int vq_id);
 int rproc_boot_nowait(struct rproc *rproc);
+static void rproc_fw_config_virtio_cb(const struct firmware *fw, void *context);
+static void rproc_fw_config_virtio(const struct firmware *fw, struct rproc *rproc);
+
 
 /* from remoteproc_virtio.c */
 int rproc_add_virtio_dev(struct rproc_vdev *rvdev, int id);
-- 
1.9.1

  parent reply	other threads:[~2016-07-06  8:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06  8:54 [PATCH v6 00/18] Add support for FDMA DMA controller and slim core rproc found on STi chipsets Peter Griffin
2016-07-06  8:54 ` [PATCH v6 01/18] remoteproc: st_slim_rproc: add a slimcore rproc driver Peter Griffin
2016-07-06 10:22   ` kbuild test robot
     [not found]   ` <1467795276-21725-2-git-send-email-peter.griffin-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-07-07  4:43     ` kbuild test robot
2016-07-06  8:54 ` [PATCH v6 02/18] MAINTAINERS: Add st slim core rproc driver to STi section Peter Griffin
2016-07-06  8:54 ` [PATCH v6 03/18] dmaengine: st_fdma: Add STMicroelectronics FDMA DT binding documentation Peter Griffin
2016-07-06  8:54 ` [PATCH v6 04/18] dmaengine: st_fdma: Add STMicroelectronics FDMA driver header file Peter Griffin
2016-07-06  8:54 ` [PATCH v6 05/18] dmaengine: st_fdma: Add STMicroelectronics FDMA engine driver support Peter Griffin
     [not found]   ` <1467795276-21725-6-git-send-email-peter.griffin-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-07-06 16:31     ` kbuild test robot
2016-07-06  8:54 ` [PATCH v6 06/18] ARM: STi: DT: STiH407: Add FDMA driver dt nodes Peter Griffin
2016-07-06  8:54 ` [PATCH v6 07/18] MAINTAINERS: Add FDMA driver files to STi section Peter Griffin
2016-07-06  8:54 ` [PATCH v6 08/18] ARM: multi_v7_defconfig: Enable STi FDMA driver Peter Griffin
2016-07-06  8:54 ` [PATCH v6 09/18] ARM: multi_v7_defconfig: Enable STi and simple-card drivers Peter Griffin
2016-07-06  8:54 ` [PATCH v6 10/18] ARM: DT: STiH407: Add i2s_out pinctrl configuration Peter Griffin
2016-07-06  8:54 ` [PATCH v6 11/18] ARM: DT: STiH407: Add i2s_in " Peter Griffin
     [not found] ` <1467795276-21725-1-git-send-email-peter.griffin-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-07-06  8:54   ` [PATCH v6 12/18] ARM: DT: STiH407: Add spdif_out pinctrl config Peter Griffin
2016-07-06  8:54   ` [PATCH v6 13/18] ARM: STi: DT: STiH407: Add sti-sasg-codec dt node Peter Griffin
2016-07-06  8:54   ` [PATCH v6 15/18] ARM: STi: DT: STiH407: Add uniperif reader dt nodes Peter Griffin
2016-07-06  8:54 ` [PATCH v6 14/18] ARM: STi: DT: STiH407: Add uniperif player " Peter Griffin
2016-07-06  8:54 ` [PATCH v6 16/18] ARM: DT: STi: stihxxx-b2120: Add DT nodes for STi audio card Peter Griffin
2016-07-06  8:54 ` [PATCH v6 17/18] dmaengine: st_fdma: Change to late_initcall_sync Peter Griffin
2016-07-06  8:54 ` Peter Griffin [this message]
2016-07-07  1:25   ` [PATCH v6 18/18] remoteproc: core: Retry rproc_fw_config_virtio() if !rproc->table_ptr kbuild test robot
     [not found]     ` <201607070935.iuu6KqiK%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-07-07 10:20       ` Peter Griffin
2016-08-05 12:52   ` Lee Jones
2016-07-06 16:40 ` [PATCH v6 00/18] Add support for FDMA DMA controller and slim core rproc found on STi chipsets Joe Perches
2016-07-06 19:49   ` Peter Griffin

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=1467795276-21725-19-git-send-email-peter.griffin@linaro.org \
    --to=peter.griffin@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=kernel@stlinux.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=patrice.chotard@st.com \
    --cc=vinod.koul@intel.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).