From: Meador Inge <meador_inge@mentor.com>
To: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: Scott Wood <scottwood@freescale.com>
Subject: Re: [PATCH v2 0/2] powerpc: define and implement MPIC message register support
Date: Thu, 26 May 2011 09:21:55 -0500 [thread overview]
Message-ID: <4DDE6203.10007@mentor.com> (raw)
In-Reply-To: <BANLkTikvDEG4DSvVMtxa8=i=NV=o=DQLXA@mail.gmail.com>
Scott, I addressed your feedback in this patch set:
* 1/2 - http://lists.ozlabs.org/pipermail/linuxppc-dev/2011-May/090405.html
* 2/2 - http://lists.ozlabs.org/pipermail/linuxppc-dev/2011-May/090406.html
Ben, my Cc for you didn't go through the first time.
> 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.
>
> * 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
> powerpc: add support for MPIC message register API
>
> .../devicetree/bindings/powerpc/fsl/mpic-msgr.txt | 62 +++++
> arch/powerpc/include/asm/mpic_msgr.h | 35 +++
> arch/powerpc/platforms/Kconfig | 8 +
> arch/powerpc/sysdev/Makefile | 3 +-
> arch/powerpc/sysdev/mpic_msgr.c | 279 ++++++++++++++++++++
> 5 files changed, 386 insertions(+), 1 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/mpic-msgr.txt
> create mode 100644 arch/powerpc/include/asm/mpic_msgr.h
> create mode 100644 arch/powerpc/sysdev/mpic_msgr.c
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
--
Meador Inge
CodeSourcery / Mentor Embedded
http://www.mentor.com/embedded-software
prev parent reply other threads:[~2011-05-26 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 16:36 [PATCH v2 0/2] powerpc: define and implement MPIC message register support Meador Inge
2011-05-20 16:36 ` [PATCH v2 1/2] powerpc: document the FSL MPIC message register binding Meador Inge
2011-05-26 20:03 ` Scott Wood
2011-05-26 20:06 ` Scott Wood
2011-05-31 19:19 ` Meador Inge
2011-05-20 16:36 ` [PATCH v2 2/2] powerpc: add support for MPIC message register API Meador Inge
[not found] ` <BANLkTikvDEG4DSvVMtxa8=i=NV=o=DQLXA@mail.gmail.com>
2011-05-26 14:21 ` Meador Inge [this message]
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=4DDE6203.10007@mentor.com \
--to=meador_inge@mentor.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--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 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).