From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: Saravana Kannan <skannan@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>, Tony Lindgren <tony@atomide.com>,
Brian Swetland <swetland@google.com>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org,
Grant Likely <grant.likely@secretlab.ca>,
akpm@linux-foundation.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/7] Introducing a generic AMP framework
Date: Wed, 23 Nov 2011 16:10:14 +0000 [thread overview]
Message-ID: <20111123161012.GA31423@sirena.org.uk> (raw)
In-Reply-To: <CAK=WgbYyrbZLmDOx8yKWwjhn2MYN8669FDRvsYZSyLj1equcTw@mail.gmail.com>
On Wed, Nov 23, 2011 at 12:27:31PM +0200, Ohad Ben-Cohen wrote:
> On Wed, Nov 23, 2011 at 5:25 AM, Saravana Kannan <skannan@codeaurora.org> wrote:
> > Sorry for the rant, this naming just rubs me the wrong way. I definitely
> > appreciate the idea behind these patches.
> I don't share the same naming concerns you have (if any, then
> confusion with the bluetooth AMP patches and prefixes is more of a
> concern to me), but I don't care deeply about names.
I guess one very real potential for confusion here is the big/little
stuff that ARM are pushing for next generation SoCs where a Linux image
does actually run on muliple asymmetric cores.
> Feel free to offer a different name, though really 'amp' here only
> describes the general model and motivation and is rarely used
> throughout the code; we mostly either use 'remoteproc' or 'rpmsg',
> which respectively refer to the two frameworks that are being added
> (the former responsible for controlling the state of the remote
> processors, and the latter for communicating with them).
How about using remoteproc then?
next prev parent reply other threads:[~2011-11-23 16:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 9:48 Ohad Ben-Cohen
2011-10-25 9:48 ` [PATCH 1/7] amp/remoteproc: add framework for controlling remote processors Ohad Ben-Cohen
2011-10-26 5:16 ` Jean-Christophe PLAGNIOL-VILLARD
2011-10-26 5:25 ` Ohad Ben-Cohen
2011-11-23 3:27 ` Stephen Boyd
2011-11-23 15:34 ` Ohad Ben-Cohen
2012-01-03 23:35 ` Grant Likely
2012-01-04 7:29 ` Mark Grosen
2012-01-05 13:58 ` Ohad Ben-Cohen
2011-10-25 9:48 ` [PATCH 2/7] amp/remoteproc: add debugfs entries Ohad Ben-Cohen
2012-01-03 23:36 ` Grant Likely
2011-10-25 9:48 ` [PATCH 3/7] amp/remoteproc: create rpmsg virtio device Ohad Ben-Cohen
2011-10-25 9:48 ` [PATCH 4/7] amp/omap: add a remoteproc driver Ohad Ben-Cohen
2011-12-08 7:57 ` Ohad Ben-Cohen
2011-12-08 17:01 ` Tony Lindgren
2011-12-08 17:08 ` Ohad Ben-Cohen
2011-10-25 9:48 ` [PATCH 5/7] ARM: OMAP: add amp/remoteproc support Ohad Ben-Cohen
2011-10-25 9:48 ` [PATCH 6/7] amp/rpmsg: add virtio-based remote processor messaging bus Ohad Ben-Cohen
2011-10-25 9:48 ` [PATCH 7/7] samples/amp: add an rpmsg driver sample Ohad Ben-Cohen
2011-10-26 4:00 ` [PATCH 0/7] Introducing a generic AMP framework Rusty Russell
2011-10-26 5:26 ` Ohad Ben-Cohen
2011-11-22 11:40 ` Ohad Ben-Cohen
2011-11-23 1:33 ` Rusty Russell
2011-11-23 9:58 ` Ohad Ben-Cohen
2011-12-08 7:50 ` Ohad Ben-Cohen
2011-12-09 5:38 ` Rusty Russell
2011-12-09 14:15 ` Ohad Ben-Cohen
2011-11-23 3:25 ` Saravana Kannan
2011-11-23 10:27 ` Ohad Ben-Cohen
2011-11-23 16:10 ` Mark Brown [this message]
2011-11-23 20:28 ` Saravana Kannan
2011-11-24 8:43 ` Ohad Ben-Cohen
2011-12-06 22:09 ` Saravana Kannan
2011-12-07 18:53 ` Ohad Ben-Cohen
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=20111123161012.GA31423@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ohad@wizery.com \
--cc=rusty@rustcorp.com.au \
--cc=skannan@codeaurora.org \
--cc=swetland@google.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®