From: Ohad Ben-Cohen <ohad@wizery.com>
To: Preetham-rao K <preetham.rao@stericsson.com>
Cc: Fernando Guzman Lugo <fernando.lugo@ti.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remoteproc: block premature rproc booting
Date: Fri, 29 Jun 2012 17:56:09 +0300 [thread overview]
Message-ID: <CAK=WgbYXR7ino3LN1UKbmHi=qhYgQbF439mD93rVXFWTf68osw@mail.gmail.com> (raw)
In-Reply-To: <81C3A93C17462B4BBD7E272753C10579232F86B623@EXDCVYMBSTM005.EQ1STM.local>
Hello Preetham rao,
On Fri, Jun 29, 2012 at 2:13 PM, Preetham-rao K
<preetham.rao@stericsson.com> wrote:
> We have some questions …
>
>
>
> Is remoteproc self governor the remote processor?
>
> When the time of crash on remote processor, will remoteproc take care of
> loading the firmware?
Yes. the low level driver just has to notify remoteproc that the crash
occurred, and the remoteproc framework will take care of the rest.
This is not upstream yet - but Fernando (cc'ed) already has the
patches and can probably share them with you if you're interested.
Ohad.
> Or user has to drive this using remoteproc API?
>
>
>
> Regards,
>
> Preetham rao
next parent reply other threads:[~2012-06-29 14:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <81C3A93C17462B4BBD7E272753C10579232F86B623@EXDCVYMBSTM005.EQ1STM.local>
2012-06-29 14:56 ` Ohad Ben-Cohen [this message]
2012-07-02 6:08 ` [PATCH] remoteproc: block premature rproc booting Preetham-rao K
2012-07-02 21:10 ` Guzman Lugo, Fernando
2012-05-22 11:51 Ohad Ben-Cohen
2012-05-22 11:51 ` Ohad Ben-Cohen
2012-05-22 11:51 ` Ohad Ben-Cohen
2012-05-24 9:15 ` Stephen Boyd
2012-05-24 9:15 ` Stephen Boyd
2012-05-24 20:11 ` Ohad Ben-Cohen
2012-05-24 20:11 ` Ohad Ben-Cohen
2012-06-04 21:23 ` Stephen Boyd
2012-06-04 21:23 ` Stephen Boyd
2012-06-05 10:57 ` Ohad Ben-Cohen
2012-06-05 10:57 ` Ohad Ben-Cohen
2012-06-06 3:25 ` Stephen Boyd
2012-06-06 3:25 ` Stephen Boyd
2012-06-06 5:44 ` Ohad Ben-Cohen
2012-06-06 5:44 ` Ohad Ben-Cohen
2012-06-06 5:44 ` Ohad Ben-Cohen
2012-07-02 12:25 ` Ohad Ben-Cohen
2012-07-02 12:25 ` Ohad Ben-Cohen
2012-07-02 15:15 ` Sjur BRENDELAND
2012-07-02 15:15 ` Sjur BRENDELAND
2012-07-02 15:15 ` Sjur BRENDELAND
2012-07-02 15:19 ` Ohad Ben-Cohen
2012-07-02 15:19 ` Ohad Ben-Cohen
2012-07-02 15:19 ` 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='CAK=WgbYXR7ino3LN1UKbmHi=qhYgQbF439mD93rVXFWTf68osw@mail.gmail.com' \
--to=ohad@wizery.com \
--cc=fernando.lugo@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=preetham.rao@stericsson.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 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.