Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1398072

Re: [PATCH 3/5] remoteproc: core: Add ability to select a firmware from the client

From Lee Jones <lee.jones@linaro.org>
Newsgroups linux.kernel
Subject Re: [PATCH 3/5] remoteproc: core: Add ability to select a firmware from the client
Date 2016-05-10 15:10 +0200
Message-ID <rxfAe-2Xf-17@gated-at.bofh.it> (permalink)
References <rvrFw-S0-5@gated-at.bofh.it> <rvrFw-S0-13@gated-at.bofh.it> <rvT8K-20P-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Fri, 06 May 2016, Bjorn Andersson wrote:

> On Thu 05 May 06:29 PDT 2016, Lee Jones wrote:
> 
> > ST Co-Processors can be loaded with different firmwares to execute
> > specific tasks without the need for unloading the rproc module.
> > 
> 
> I'm very much interested in ideas related to this and who "owns" the
> life cycle of remoteprocs, do you have any code I can take a look at
> that's using this interface?

I was part of a conversation on the list which should explain some of
your queries [0].  The conclusion was, that only the client can know
what which firmware it is compatible with.  This information can not
realistically either live in DT (or any other platform data) or within
RemoteProc.  I hope that link answers your questions.

[0] http://www.spinics.net/lists/devicetree-spec/msg00144.html

> > This patch provides a function which can update the firmware name.
> > 
> > NB: This can only happen if the rproc is offline.
> 
> How is this working in the case when the remoteproc provides vdevs that
> is holding references towards the rproc?
> 
> Do you unload rpmsg et al before doing this?

RemoteProc needs to be offline for the firmware name to be set, this
includes links to RPMsg, so yes, they would have to be unloaded.

> > Signed-off-by: Ludovic Barre <ludovic.barre@st.com>
> > Signed-off-by: Lee Jones <lee.jones@linaro.org>
> > ---
> >  drivers/remoteproc/remoteproc_core.c | 63 ++++++++++++++++++++++++++++++++++++
> >  include/linux/remoteproc.h           | 13 ++++++++
> >  2 files changed, 76 insertions(+)

Happy with the remainder of your comments -- will fix.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH 0/5] remoteproc: A few important improvements Lee Jones <lee.jones@linaro.org> - 2016-05-05 15:40 +0200
  [PATCH 3/5] remoteproc: core: Add ability to select a firmware from the client Lee Jones <lee.jones@linaro.org> - 2016-05-05 15:40 +0200
    Re: [PATCH 3/5] remoteproc: core: Add ability to select a firmware  from the client Bjorn Andersson <bjorn.andersson@linaro.org> - 2016-05-06 21:00 +0200
      Re: [PATCH 3/5] remoteproc: core: Add ability to select a firmware  from the client Lee Jones <lee.jones@linaro.org> - 2016-05-10 15:10 +0200
  [PATCH 4/5] remoteproc: core: Supply framework to request, declare and fetch shared memory Lee Jones <lee.jones@linaro.org> - 2016-05-05 15:40 +0200
    Re: [PATCH 4/5] remoteproc: core: Supply framework to request,  declare and fetch shared memory Bjorn Andersson <bjorn.andersson@linaro.org> - 2016-05-12 00:40 +0200
  [PATCH 1/5] remoteproc: core: Task sync during rproc_fw_boot() Lee Jones <lee.jones@linaro.org> - 2016-05-05 15:40 +0200
    Re: [PATCH 1/5] remoteproc: core: Task sync during rproc_fw_boot() Bjorn Andersson <bjorn.andersson@linaro.org> - 2016-05-06 20:50 +0200

csiph-web