From: Suman Anna <s-anna@ti.com>
To: Stefan Agner <stefan@agner.ch>, "ohad@wizery.com" <ohad@wizery.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] remoteproc: report error if resource table doesn't exist
Date: Thu, 3 Sep 2015 14:32:11 -0500 [thread overview]
Message-ID: <55E8A03B.9090608@ti.com> (raw)
In-Reply-To: <1440810499-24327-1-git-send-email-stefan@agner.ch>
On 08/28/2015 08:08 PM, Stefan Agner wrote:
> Currently, if the resource table is completely missing in the
> firmware, powering up the remoteproc fails silently. Add a message
> indicating that the resource table is missing in the firmware.
Yeah, pretty useful to have a trace there..
Acked-by: Suman Anna <s-anna@ti.com>
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> ---
> Hi Ohad,
>
> I am currently working on remoteproc support for Freescale Vybrid's
> secondary Cortex-M4 core. I stumbled upon this rough spot since the
> little test firmware I am using now does not have a resource table
> yet.
>
> This also opens up a more general question: Is it mandatory to have
> a resource table in the firmware? Theoretically a remoteproc could
> also work completely independent, all what would be used from the
> remoteproc framework is the loading and starting capabilities...
Hi Ohad,
We will probably be seeing more of such scenarios for very simplistic
devices (like the ones that load into their internal memories), it looks
like the framework needs some kind of support for booting such devices,
whether auto-boot, or give some kind of sysfs control for userspace. We
do have the rproc_boot() and rproc_shutdown() API, but that almost
always requires some other entity in the kernel to be able to invoke
those API. Any suggestions here?
regards
Suman
>
> --
> Stefan
>
> drivers/remoteproc/remoteproc_core.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
> index 8b3130f..29db8b3 100644
> --- a/drivers/remoteproc/remoteproc_core.c
> +++ b/drivers/remoteproc/remoteproc_core.c
> @@ -823,8 +823,10 @@ static int rproc_fw_boot(struct rproc *rproc, const struct firmware *fw)
>
> /* look for the resource table */
> table = rproc_find_rsc_table(rproc, fw, &tablesz);
> - if (!table)
> + if (!table) {
> + dev_err(dev, "Failed to find resource table\n");
> goto clean_up;
> + }
>
> /* Verify that resource table in loaded fw is unchanged */
> if (rproc->table_csum != crc32(0, table, tablesz)) {
>
next prev parent reply other threads:[~2015-09-03 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 1:08 [PATCH] remoteproc: report error if resource table doesn't exist Stefan Agner
2015-09-03 19:32 ` Suman Anna [this message]
2015-11-27 16:50 ` Bjorn Andersson
2015-11-26 9:05 ` Ohad Ben-Cohen
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=55E8A03B.9090608@ti.com \
--to=s-anna@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=stefan@agner.ch \
/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