linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Meador Inge <meador_inge@mentor.com>
To: linuxppc-dev@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org
Cc: openmcapi-dev@googlegroups.com, "Blanchard,
	Hollis" <Hollis_Blanchard@mentor.com>,
	Hiroshi DOYU <Hiroshi.DOYU@nokia.com>
Subject: [RFC] Inter-processor Mailboxes Drivers
Date: Fri, 11 Feb 2011 15:19:51 -0600	[thread overview]
Message-ID: <4D55A7F7.5090700@mentor.com> (raw)

Hi All,

I am currently working on building AMP systems using OpenMCAPI
(https://bitbucket.org/hollisb/openmcapi/wiki/Home) as the
inter-processor communication mechanism.  With OpenMCAPI we, of course,
need a way to send messages to various cores.  On some Freescale PPC
platforms (e.g. P1022DS, MPC8572DS), we have been using message
registers to do this work.  Recently, I was looking at the OMAP4
mailboxes to gear up for moving into ARM based platforms.

With that, I noticed 'arch/arm/plat-omap/mailbox.c'.  This is very
specific to the OMAP4 boards.  I am looking at designing a new set of
drivers to expose a mailbox service to userspace that will be used
for inter-processor communication.  This would entail the traditional
generic/specific driver split:

     1. Hardware specific bits somewhere under '.../arch/*'.  Drivers
        for the MPIC message registers on Power and OMAP4 mailboxes, for
        example.
     2. A higher level driver under '.../drivers/mailbox/*'.  That the
        pieces in (1) would register with.  This piece would expose the
        main kernel API.
     3. Userspace interfaces for accessing the mailboxes.  A
        '/dev/mailbox1', '/dev/mailbox2', etc... mapping, for example.

Now I have the following questions:

     1. Do others see value in this?
     2. Does something like this already exist?
     3. Is someone else already working on this?

Any feedback will be greatly appreciated.

-- 
Meador Inge     | meador_inge AT mentor.com
Mentor Embedded | http://www.mentor.com/embedded-software

             reply	other threads:[~2011-02-11 21:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11 21:19 Meador Inge [this message]
2011-02-12  6:28 ` [RFC] Inter-processor Mailboxes Drivers Sundar
2011-02-13 21:16   ` Linus Walleij
2011-02-14  7:32     ` Hiroshi DOYU
2011-02-14  8:39       ` Linus Walleij
2011-02-14  8:55         ` Hiroshi DOYU
2011-02-14  9:00           ` Linus Walleij
2011-02-14  9:06           ` Hiroshi DOYU
2011-02-13 21:24 ` Linus Walleij
2011-02-14 23:05   ` Blanchard, Hollis
2011-02-16 21:54     ` Linus Walleij
2011-02-14  7:21 ` Hiroshi DOYU
2011-02-14 10:01 ` Jamie Iles
2011-02-14 10:03   ` Ohad Ben-Cohen
2011-02-14 16:53     ` Ira W. Snyder
2011-02-15 21:58   ` Meador Inge
2011-02-15 23:38     ` Blanchard, Hollis
2011-02-16  6:22       ` Hiroshi DOYU
2011-02-16 20:22         ` [openmcapi-dev] " Blanchard, Hollis

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=4D55A7F7.5090700@mentor.com \
    --to=meador_inge@mentor.com \
    --cc=Hiroshi.DOYU@nokia.com \
    --cc=Hollis_Blanchard@mentor.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=openmcapi-dev@googlegroups.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;
as well as URLs for NNTP newsgroup(s).