From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Andrey Smirnov <andrew.smirnov@gmail.com>,
David Brandt <d.brandt@phytec.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] commands: bootaux: New command bootaux for iMX
Date: Tue, 12 Mar 2019 07:03:34 +0100 [thread overview]
Message-ID: <8b6352d3-bc8d-4564-9eee-0e0eda70515e@pengutronix.de> (raw)
In-Reply-To: <CAHQ1cqHAGSyzJbxeEKW6-Y8g79nv3iMZZGr-qy2pY401=V5b5w@mail.gmail.com>
Hi,
On 12.03.19 02:37, Andrey Smirnov wrote:
> On Mon, Mar 11, 2019 at 6:41 AM David Brandt <d.brandt@phytec.de> wrote:
>>
>> This patch adds the bootaux command which starts
>> auxiliary cores of iMX processors, currently only
>> for iMX8MQ. This is based on the u-boot-imx
>> command and shares the behaviour.
>>
>> The currently unnecessary parameter for the core
>> to start is necessary for the iMX8QM and other
>> processors having multiple auxiliary cores.
>>
>
> Not saying that there's anything wrong with this patch, but I am
> guessing that upstream Linux will eventually implement this
> functionality using remoteproc framework. Maybe now would be a good
> time to add a very basic version of it to Barebox? Another option to
> make this a little bit more flexible would be to implement this using
> firmwaremgr framework similar to
> drivers/frimware/{socfpga.c,altera_serial.c}. Anyway, just a couple of
> suggestions that I had.
I agree with remoteproc here.
The task of remoteproc on linux is:
- parse specially formated ELF file:
- Register needed resources extracted from ELF
- prepare clocks
- do address translation
- kick on the CPU
The main issue of linux part is to dunamically patch devicetree and tell master linux
instance about IP Cores which was migrated for master CPU to the slave CPU.
With barebox this issues can be solved. First of all, barebox already has ELF parser. So
it can be reused. The drivers/remoteproc/imx_rproc.c from linux can probably be ported as
is. As soon as first step done, we would be able to patch devicetree in barebox and gave
it over to linux. So, we will be able to tell linux to let some clocks on and do not touch
reserved memory areas.
Kind regards,
Oleksij Rempel
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-03-12 6:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 13:41 David Brandt
2019-03-11 23:47 ` Roland Hieber
2019-03-12 1:37 ` Andrey Smirnov
2019-03-12 6:03 ` Oleksij Rempel [this message]
2019-03-13 8:32 ` Sascha Hauer
2019-03-13 11:36 ` David Brandt
2019-03-13 14:41 ` [PATCH v2] " David Brandt
2019-03-18 10:15 ` Sascha Hauer
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=8b6352d3-bc8d-4564-9eee-0e0eda70515e@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=d.brandt@phytec.de \
/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