From: Scott Wood <scottwood@freescale.com>
To: Meador Inge <meador_inge@mentor.com>
Cc: openmcapi-dev@googlegroups.com,
Hollis Blanchard <hollis_blanchard@mentor.com>,
devicetree-discuss@lists.ozlabs.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] powerpc: document the FSL MPIC message register binding
Date: Tue, 19 Apr 2011 13:33:36 -0500 [thread overview]
Message-ID: <20110419133336.46d8566f@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <4DADD3D2.6070805@mentor.com>
On Tue, 19 Apr 2011 13:26:26 -0500
Meador Inge <meador_inge@mentor.com> wrote:
> On 04/19/2011 12:52 PM, Scott Wood wrote:
> > On Tue, 19 Apr 2011 11:59:34 -0500
> > Meador Inge <meador_inge@mentor.com> wrote:
> >
> >> Aliases are of the form 'msgr-block<n>',
> >> + where <n> is an integer specifying the block's number. Numbers shall start
> >> + at 0.
> >
> > The hw docs refer to "group A" and "group B", not "block 0" and "block 1".
> >
> > Plus, I'd put "mpic-" in the alias name.
>
> Are you suggesting that the alias should be called: 'mpic-groupA',
> 'mpic-groupB', 'mpic-groupC', etc... ?
I was thinking something like "mpic-msgr-group-a", "mpic-msgr-group-b" --
though if you want to use numbers instead to more easily map to potential
APIs, that's OK.
-Scott
next prev parent reply other threads:[~2011-04-19 18:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 16:59 [PATCH 0/2] powerpc: define and implement MPIC message register support Meador Inge
2011-04-19 16:59 ` [PATCH 1/2] powerpc: document the FSL MPIC message register binding Meador Inge
2011-04-19 17:52 ` Scott Wood
2011-04-19 18:26 ` Meador Inge
2011-04-19 18:33 ` Scott Wood [this message]
2011-04-21 19:26 ` Meador Inge
2011-04-21 19:35 ` Scott Wood
2011-04-19 16:59 ` [PATCH 2/2] powerpc: add support for MPIC message register API Meador Inge
2011-04-29 5:00 ` Kushwaha Prabhakar-B32579
2011-04-29 16:54 ` Hollis Blanchard
2011-04-29 17:27 ` Kushwaha Prabhakar-B32579
2011-04-29 17:30 ` Scott Wood
2011-05-02 3:41 ` Kushwaha Prabhakar-B32579
2011-05-02 16:03 ` Hollis Blanchard
2011-05-03 15:19 ` Scott Wood
2011-05-05 21:41 ` Meador Inge
2011-05-06 19:29 ` Scott Wood
2011-05-06 23:51 ` Meador Inge
-- strict thread matches above, loose matches on Subject: below --
2012-02-17 2:49 [PATCH 1/2] powerpc: document the FSL MPIC message register binding Jia Hongtao
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=20110419133336.46d8566f@schlenkerla.am.freescale.net \
--to=scottwood@freescale.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=hollis_blanchard@mentor.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=meador_inge@mentor.com \
--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).