Linux Remote Processor Subsystem development
 help / color / mirror / Atom feed
From: Yann Sionneau <ysionneau@kalrayinc.com>
To: linux-remoteproc@vger.kernel.org
Cc: Bjorn Andersson <andersson@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Julian Vetter <jvetter@kalrayinc.com>,
	Jonathan Borne <jborne@kalray.eu>,
	Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>,
	Julien Hascoet <jhascoet@kalray.eu>,
	Damien Hedde <dhedde@kalrayinc.com>,
	Titouan Huard <thuard@kalrayinc.com>
Subject: Re: [RFC] Passing device-tree to remoteproc?
Date: Tue, 30 Jan 2024 11:20:59 +0100	[thread overview]
Message-ID: <f67cd822-4e29-71f2-7c42-e11dbaa6cd8c@kalrayinc.com> (raw)
In-Reply-To: <9c32f94e-869a-16d3-6bba-064082518ce4@kalrayinc.com>

Hello,

On 1/23/24 14:32, Yann Sionneau wrote:
> Hello,
>
> How interesting to upstream Linux would it be to have a way for Linux 
> kernel or user space to pass a device tree blob to remote processor 
> when starting a remote proc FW?
>
> For instance we could imagine something like this:
>
> 1/ user space does echo -n firmware.elf > 
> /sys/class/remoteproc/remoteprocXXX/firmware
>
> 2/ user space does echo -n my_dt.dtb > 
> /sys/class/remoteproc/remoteprocXXX/dtb
>
> 3/ user space does echo start > /sys/class/remoteproc/remoteprocXXX/state

Any opinion on this proposal?

Thanks!

Regards,

-- 

Yann






  reply	other threads:[~2024-01-30 10:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 13:32 [RFC] Passing device-tree to remoteproc? Yann Sionneau
2024-01-30 10:20 ` Yann Sionneau [this message]
2024-02-02  9:14   ` Arnaud POULIQUEN
2024-02-05 21:05     ` Mathieu Poirier
2024-02-19 16:17       ` Yann Sionneau

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=f67cd822-4e29-71f2-7c42-e11dbaa6cd8c@kalrayinc.com \
    --to=ysionneau@kalrayinc.com \
    --cc=andersson@kernel.org \
    --cc=arnaud.pouliquen@foss.st.com \
    --cc=dhedde@kalrayinc.com \
    --cc=jborne@kalray.eu \
    --cc=jhascoet@kalray.eu \
    --cc=jvetter@kalrayinc.com \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=thuard@kalrayinc.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