Re: [RFC] MPIC Bindings and Bindings for AMP Systems

On 01/05/2011 02:09 PM, Scott Wood wrote:

On Wed, 5 Jan 2011 15:58:55 -0600
Meador Inge[off-list ref]  wrote:

quoted

We need some sort of mapping between a message register and a message
register number so that the message registers can be referenced =

through

quoted

some sort of API (e.g. 'mpic_msgr_read(0)').  One way to do that =

would

quoted

be by putting an order on the registers.  Maybe there is a better =

way,

quoted

though ...

A message register is uniquely identified by a reference to the device
tree node, plus a 0-3 index into that node's message registers.

Really what we're talking about is software configuration, not hardware=20
description. We've gone back and forth on representing this information=20
in the device tree, and most recently decided against it. Outside the=20
kernel, a device node reference isn't really practical.

Hollis Blanchard
Mentor Graphics, Embedded Systems Division