Some MPIC implementations contain one or more blocks of message registers
that are used to send messages between cores via IPIs. A simple API has
been added to access (get/put, read, write, etc ...) these message registers.
The available message registers are initially discovered via nodes in the
On Thu, 5 May 2011 16:41:29 -0500
Meador Inge meador_i...@mentor.com wrote:
/* OS 1 */
mpic_msgr_block0: mpic-msgr-block@41400 {
compatible = fsl,mpic-v3.1-msgr;
reg = 0x41400 0x200;
interrupts = 0xb0 2 0xb2 2;
On 05/06/2011 02:29 PM, Scott Wood wrote:
On Thu, 5 May 2011 16:41:29 -0500
How can both OSes independently own registers 1 and 3 for alloction?
They can't. I just choose a horrible example. It does point to a serious
flaw (which you allude to later) in inferring free registers from
On 05/03/2011 10:19 AM, Scott Wood wrote:
In the absence of partitioning, no driver should need a specific one. With
partitioning, let the system designer mark those resources as reserved so
they don't get allocated. :-)
That seem reasonable. Back to the device tree then. One option is to
On Mon, 2 May 2011 09:03:53 -0700
Hollis Blanchard hollis_blanch...@mentor.com wrote:
On 05/01/2011 08:41 PM, Kushwaha Prabhakar-B32579 wrote:
Perhaps an allocator could be added in the same patchset that adds such a
user.
Yaa. It can be done. Otherwise module has to query each message
On 05/01/2011 08:41 PM, Kushwaha Prabhakar-B32579 wrote:
Hi,
I have no comments about coding and architecture. It looks fine.
Only have a query about its use case..
Any application intended to use message interrupt requires to
know
reg_num because of struct mpic_msgr*
Hi,
I have no comments about coding and architecture. It looks fine.
Only have a query about its use case..
Any application intended to use message interrupt requires to
know
reg_num because of struct mpic_msgr* mpic_msgr_get(unsigned int
reg_num) API
On 04/28/2011 10:00 PM, Kushwaha Prabhakar-B32579 wrote:
Hi,
I have no comments about coding and architecture. It looks fine.
Only have a query about its use case..
Any application intended to use message interrupt requires to know reg_num
because of struct mpic_msgr*
Hi,
I have no comments about coding and architecture. It looks fine.
Only have a query about its use case..
Any application intended to use message interrupt requires to know
reg_num because of struct mpic_msgr* mpic_msgr_get(unsigned int reg_num)
API
It will be good to
On Fri, 29 Apr 2011 17:27:06 +
Kushwaha Prabhakar-B32579 b32...@freescale.com wrote:
Hi,
I have no comments about coding and architecture. It looks fine.
Only have a query about its use case..
Any application intended to use message interrupt requires to know
Sent: Tuesday, April 19, 2011 10:30 PM
To: linuxppc-dev@lists.ozlabs.org
Cc: openmcapi-...@googlegroups.com; devicetree-disc...@lists.ozlabs.org;
Hollis Blanchard
Subject: [PATCH 2/2] powerpc: add support for MPIC message register API
Some MPIC implementations contain one or more blocks
Some MPIC implementations contain one or more blocks of message registers
that are used to send messages between cores via IPIs. A simple API has
been added to access (get/put, read, write, etc ...) these message registers.
The available message registers are initially discovered via nodes in the
12 matches
Mail list logo
