From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: shared resources in AMP between Cortex-A9 and Cortex-M4
Date: Tue, 7 Jun 2016 17:50:44 +0100 [thread overview]
Message-ID: <5756FB64.6060207@arm.com> (raw)
In-Reply-To: <20160607162545.GX26768@pengutronix.de>
On 07/06/16 17:25, Uwe Kleine-K?nig wrote:
> 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.
>
IMO it should be other way around. In-fact few latest platforms(with
performant Cortex-A cores) have dedicated Cortex-M core to do such
system control and power management as it are low power and mostly
always on.
--
Regards,
Sudeep
next prev parent reply other threads:[~2016-06-07 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 16:25 shared resources in AMP between Cortex-A9 and Cortex-M4 Uwe Kleine-König
2016-06-07 16:50 ` Sudeep Holla [this message]
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=5756FB64.6060207@arm.com \
--to=sudeep.holla@arm.com \
--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).