From: Meador Inge <meador_inge@mentor.com>
To: Scott Wood <scottwood@freescale.com>, galak@kernel.crashing.org
Cc: openmcapi-dev@googlegroups.com,
devicetree-discuss@lists.ozlabs.org, "Blanchard,
Hollis" <Hollis_Blanchard@mentor.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [openmcapi-dev] [PATCH v3 0/2] powerpc: define and implement MPIC message register support
Date: Thu, 09 Jun 2011 09:44:10 -0500 [thread overview]
Message-ID: <4DF0DC3A.1040300@mentor.com> (raw)
In-Reply-To: <1306869543-18812-1-git-send-email-meador_inge@mentor.com>
On 05/31/2011 02:19 PM, Meador Inge wrote:
> This patch set defines a binding for FSL MPIC message registers and implements
> an API for accessing those message registers. Testing was done on a MPC8572DS
> in an Linux-Linux AMP setup using OpenMCAPI (www.openmcapi.org) to communicate
> between OS instances. The message register API is used by the OpenMCAPI shared
> memory driver to send notifications between cores.
>
> * v3 - Clarified a point in the binding concerning the length of the
> 'interrupts' property. Pointed out by Scott Wood.
>
> * v2 - Incorporate feedback from Scott Wood
> * Make binding less implementation specific.
> * Add 'mpic-' prefix to message register node properties and aliases.
> * Remove 'interrupt-parent' from binding.
> * Fixed some example bugs with receive masks.
>
> Signed-off-by: Meador Inge <meador_inge@mentor.com>
> Cc: Hollis Blanchard <hollis_blanchard@mentor.com>
>
> Meador Inge (2):
> powerpc: document the FSL MPIC message register binding
The binding has been acked (Thanks Scott).
> powerpc: add support for MPIC message register API
Scott, Kumar, are you all OK with the
implementation: http://patchwork.ozlabs.org/patch/98075/ ?
--
Meador Inge
CodeSourcery / Mentor Embedded
http://www.mentor.com/embedded-software
WARNING: multiple messages have this Message-ID (diff)
From: Meador Inge <meador_inge-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
To: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org
Cc: openmcapi-dev-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
"Blanchard,
Hollis"
<Hollis_Blanchard-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>,
linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [openmcapi-dev] [PATCH v3 0/2] powerpc: define and implement MPIC message register support
Date: Thu, 09 Jun 2011 09:44:10 -0500 [thread overview]
Message-ID: <4DF0DC3A.1040300@mentor.com> (raw)
In-Reply-To: <1306869543-18812-1-git-send-email-meador_inge-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
On 05/31/2011 02:19 PM, Meador Inge wrote:
> This patch set defines a binding for FSL MPIC message registers and implements
> an API for accessing those message registers. Testing was done on a MPC8572DS
> in an Linux-Linux AMP setup using OpenMCAPI (www.openmcapi.org) to communicate
> between OS instances. The message register API is used by the OpenMCAPI shared
> memory driver to send notifications between cores.
>
> * v3 - Clarified a point in the binding concerning the length of the
> 'interrupts' property. Pointed out by Scott Wood.
>
> * v2 - Incorporate feedback from Scott Wood
> * Make binding less implementation specific.
> * Add 'mpic-' prefix to message register node properties and aliases.
> * Remove 'interrupt-parent' from binding.
> * Fixed some example bugs with receive masks.
>
> Signed-off-by: Meador Inge <meador_inge-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
> Cc: Hollis Blanchard <hollis_blanchard-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
>
> Meador Inge (2):
> powerpc: document the FSL MPIC message register binding
The binding has been acked (Thanks Scott).
> powerpc: add support for MPIC message register API
Scott, Kumar, are you all OK with the
implementation: http://patchwork.ozlabs.org/patch/98075/ ?
--
Meador Inge
CodeSourcery / Mentor Embedded
http://www.mentor.com/embedded-software
next prev parent reply other threads:[~2011-06-09 14:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 19:19 [PATCH v3 0/2] powerpc: define and implement MPIC message register support Meador Inge
2011-05-31 19:19 ` Meador Inge
2011-05-31 19:19 ` [PATCH v3 1/2] powerpc: document the FSL MPIC message register binding Meador Inge
2011-05-31 19:23 ` Scott Wood
2011-06-02 14:33 ` Meador Inge
2011-05-31 19:19 ` [PATCH v3 2/2] powerpc: add support for MPIC message register API Meador Inge
2011-05-31 19:19 ` Meador Inge
2011-06-17 5:33 ` Benjamin Herrenschmidt
2011-06-17 5:33 ` Benjamin Herrenschmidt
2011-06-17 13:49 ` [openmcapi-dev] " Meador Inge
2011-06-17 16:58 ` Scott Wood
2011-06-17 16:58 ` Scott Wood
2011-06-17 22:58 ` Benjamin Herrenschmidt
2011-06-20 15:59 ` Scott Wood
2011-06-20 15:59 ` Scott Wood
2011-06-21 7:47 ` Benjamin Herrenschmidt
2011-06-21 7:47 ` Benjamin Herrenschmidt
2011-06-30 3:04 ` [openmcapi-dev] " Meador Inge
2011-06-30 4:19 ` Benjamin Herrenschmidt
2011-06-30 4:19 ` Benjamin Herrenschmidt
2011-06-09 14:44 ` Meador Inge [this message]
2011-06-09 14:44 ` [openmcapi-dev] [PATCH v3 0/2] powerpc: define and implement MPIC message register support Meador Inge
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=4DF0DC3A.1040300@mentor.com \
--to=meador_inge@mentor.com \
--cc=Hollis_Blanchard@mentor.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=openmcapi-dev@googlegroups.com \
--cc=scottwood@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.