From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: shared resources in AMP between Cortex-A9 and Cortex-M4
Date: Tue, 7 Jun 2016 18:25:45 +0200 [thread overview]
Message-ID: <20160607162545.GX26768@pengutronix.de> (raw)
Hello Stefan,
I'm currently trying to get Linux running on the M4 of an i.MX6 Solo X
and found you describing doing this on the Vybrid already[1].
I see the problem that clk and pinmux must be used by both cores. Did
you solve this for your Vybrid experiments? And if so, how did it work?
Having two drivers on the same IP is racy at best and using some kind of
inter cpu communication to let (say) the A9 enable the clks for the M4
sounds like overkill.
Best regards
Uwe
[1] https://falstaff.agner.ch/2015/05/17/u-boot-command-to-boot-vybrids-cortex-m4-core/
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next reply other threads:[~2016-06-07 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 16:25 Uwe Kleine-König [this message]
2016-06-07 16:50 ` shared resources in AMP between Cortex-A9 and Cortex-M4 Sudeep Holla
2016-06-07 17:06 ` Stefan Agner
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=20160607162545.GX26768@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).