6 0x2 0xb7 0x2>;
};
};
* References
[1] PowerPC Microprocessor Common Hardware Reference Platform (CHRP)
Binding, Version 1.8, 1998. Published by the Open Firmware Working
Group. (http://playground.sun.com/1275/bindings/chrp/chrp1_8a.ps)
--
Meador Ing
6 0x2 0xb7 0x2>;
};
};
* References
[1] PowerPC Microprocessor Common Hardware Reference Platform (CHRP)
Binding, Version 1.8, 1998. Published by the Open Firmware Working
Group. (http://playground.sun.com/1275/bindings/chrp/chrp1_8a.ps)
--
Meador Inge | meador_inge AT mentor.com
Mentor Embedded | http://www.mentor.com/embedded-software
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
ve a 'ranges' property.
Yes, they are. I will look into adding that.
[1] commit 7fd7218610600b16f6f0af3f9d9353ba0265c09f,
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.36.y.git;a=commit;h=7fd7218610600b16f6f0af3f9d9353ba0265c09f
[2] Documentation/powerpc/dts-bindings/fsl/msi-pic.txt
[
ls =<&msg1 0>; // receive messages on MSGR1
};
some-other-amp-protocol-thingy {
send-doorbells =<&msg1 1>; // generate messages on MSGR2
receive-doorbells =<&msg1 1>; // receive messages on MSGR3
};
Doorbell capabilities such as passing a 32-bit message
On 01/04/2011 06:13 PM, Scott Wood wrote:
On Tue, 4 Jan 2011 17:52:38 -0600
Meador Inge wrote:
Thanks for the feedback Scott.
On 01/03/2011 02:22 PM, Scott Wood wrote:
On Wed, 22 Dec 2010 23:58:09 -0600
These nodes cannot go under the mpic node, because interrupt
controllers need #address
On 01/03/2011 01:51 PM, Scott Wood wrote:
On Thu, 23 Dec 2010 15:33:25 -0700
Grant Likely wrote:
On Thu, Dec 23, 2010 at 03:49:54PM -0600, Meador Inge wrote:
How do you
see this working in terms of processing the data? It seems like we
are going to have to be aware of N values instead of 1
l as well.
I would be happy to contribute to that, but I am still learning the best
practices :)
--
Meador Inge | meador_inge AT mentor.com
Mentor Embedded | http://www.mentor.com/embedded-software
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
g1, &value) == 0);
The API usage for other cores would look similar. As mentioned in
another thread, this will provide us with the low-level building blocks
and we can layer other protocols, such as the doorbell protocol, on top
later (if needed).
Hollis, how do you feel about this?
--
This patch set provides a binding for the MPIC and implements support
for a new property, specified by that binding, called 'no-reset'.
Signed-off-by: Meador Inge
CC: Hollis Blanchard
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs
This binding documents several properties that have been in use for
quite some time, and adds one new property 'no-reset', which controls
whether the MPIC should be reset during runtime initialization.
Signed-off-by: Meador Inge
CC: Hollis Blanchard
---
Documentation/powerpc/dt
This property, defined in the MPIC binding, tells the kernel not to use
the reset bit in the global configuration register.
Signed-off-by: Meador Inge
CC: Hollis Blanchard
---
arch/powerpc/sysdev/mpic.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc
quot;fsl,mpic";
+ interrupt-controller;
+ #interrupt-cells =<4>;
+ #address-cells =<0>;
+ reg =<0x4 0x4>;
+ };
--
1.7.2.2
___
devicetree-discuss mailing list
devicetree-disc.
escale specific thing and does belong in the
Freescale binding directory.
Agreed.
That being said, if there is consensus on the AMP related properties,
I should probably incorporate those as well-- protected-sources
and no-reset.
I'll separately comment on your mpic binding
independent operating systems need to share
+ the MPIC
+ without clobbering each other.
I do think you need to include the definition of interrupt
specifiers here. Feel free to cut/paste text from my
Freescale mpic binding.
OK, I will look into that. Thanks.
uch.
This was discussed a little bit already [1, 2]. The MPIC driver
currently initializes the VECPRI register for all interrupt sources,
which can lead to the aforementioned clobbering.
--
Meador Inge | meador_inge AT mentor.com
Mentor Embedded | http://www.mentor.com/embedded-soft
On 01/20/2011 09:50 AM, Yoder Stuart-B08248 wrote:
-Original Message-
From: Meador Inge [mailto:meador_i...@mentor.com]
Sent: Wednesday, January 19, 2011 6:08 PM
To: Yoder Stuart-B08248
Cc: Wood Scott-B07421; linuxppc-dev@lists.ozlabs.org; devicetree-
disc...@lists.ozlabs.org
-January/003991.html
Signed-off-by: Meador Inge
CC: Hollis Blanchard
CC: Benjamin Herrenschmidt
---
arch/powerpc/include/asm/mpic.h |3 ---
arch/powerpc/sysdev/mpic.c | 38 --
2 files changed, 0 insertions(+), 41 deletions(-)
diff --git a/arc
This patch set provides a binding for Open PIC and implements support for
a new property, specified by that binding, called 'no-reset'. With 'no-reset'
in place the 'protected-sources' property is no longer needed and was removed.
Signed-off-by: Meador Inge
CC: Hol
rt Yoder's FSL MPIC binding.
Signed-off-by: Meador Inge
CC: Hollis Blanchard
CC: Stuart Yoder
---
Documentation/powerpc/dts-bindings/open-pic.txt | 115 +++
1 files changed, 115 insertions(+), 0 deletions(-)
create mode 100644 Documentation/powerpc/dts-bindings/open-pic.
: Meador Inge
CC: Hollis Blanchard
CC: Benjamin Herrenschmidt
---
arch/powerpc/include/asm/mpic.h |4 ++-
arch/powerpc/sysdev/mpic.c | 54 ++
2 files changed, 45 insertions(+), 13 deletions(-)
diff --git a/arch/powerpc/include/asm/mpic.h b/arch
On 02/03/2011 09:56 AM, Grant Likely wrote:
On Wed, Feb 2, 2011 at 6:51 PM, Meador Inge wrote:
This binding documents several properties that have been in use for quite
some time, and adds one new property 'no-reset', which controls whether the
Open PIC should be reset duri
On 02/03/2011 09:56 AM, Arnd Bergmann wrote:
On Thursday 03 February 2011, Meador Inge wrote:
In a recent discussion [1, 2] concerning device trees for AMP systems, the
question of whether we really need 'protected-sources' arose. The general
consensus was that if you don't want
quot;protected-sources" as a
synonym for "pic-no-reset" was added.
Signed-off-by: Meador Inge
Cc: Hollis Blanchard
Meador Inge (4):
powerpc: Removing support for 'protected-sources'
powerpc: document the Open PIC device tree binding
powerpc: make MPIC honor the
-January/003991.html
[3]
http://lists.ozlabs.org/pipermail/devicetree-discuss/2011-January/004043.html
[4]
http://lists.ozlabs.org/pipermail/devicetree-discuss/2011-February/004254.html
Signed-off-by: Meador Inge
Cc: Hollis Blanchard
Cc: Benjamin Herrenschmidt
---
arch/powerpc
e with OSes that are
already up and running.
The interrupt specifier definition is based off of Stuart Yoder's FSL MPIC
binding.
Signed-off-by: Meador Inge
Cc: Hollis Blanchard
Cc: Stuart Yoder
---
Documentation/powerpc/dts-bindings/open-pic.txt | 98 +++
1 files cha
ot; is
effectively a synonym for "pic-no-reset".
Signed-off-by: Meador Inge
Cc: Hollis Blanchard
Cc: Benjamin Herrenschmidt
---
arch/powerpc/include/asm/mpic.h |4 ++-
arch/powerpc/sysdev/mpic.c | 64 +++---
2 files changed, 55 insertions(+),
The "protected-sources" property was being used in the AMP configured
MPC8572DS and P2020RDB DTS files. This changeset modifies those files
to use "pic-no-reset" instead.
Signed-off-by: Meador Inge
Cc: Hollis Blanchard
Cc: Kumar Gala
---
arch/powerpc/boot/dts/mpc8572ds_c
On 02/06/2011 05:35 PM, Benjamin Herrenschmidt wrote:
On Fri, 2011-02-04 at 17:25 -0600, Meador Inge wrote:
In a recent thread [1,2,3] concerning device trees for AMP systems, the
question of whether we really need 'protected-sources' arose. The general
consensus was that a n
On 02/06/2011 05:35 PM, Benjamin Herrenschmidt wrote:
On Fri, 2011-02-04 at 17:25 -0600, Meador Inge wrote:
In a recent thread [1,2,3] concerning device trees for AMP systems, the
question of whether we really need 'protected-sources' arose. The general
consensus was that a n
as there is they will botch the "interrupts"
property. We could perhaps still preform these checks without the extra
property: if a source is not mentioned in an interrupts property, then
it is not allowed.
Cheers,
Ben.
[1] http://lists.ozlabs.org/pipermail/linuxppc-dev/2011-February
ng protected sources implementation
in place?
For (1), I am fine with either. For (2), I still think that we can make
"pic-no-reset" a synonym for "protected-sources" and that things will
work out.
On 02/10/2011 02:42 PM, Meador Inge wrote:
-- Forwarded messag
Apologies for the bad post. Bad day for email ... Please ignore the
top reply in my previous reply. The full reply is the below the
quote.
On Thu, Feb 10, 2011 at 8:01 PM, Meador Inge wrote:
>
> On 02/10/2011 02:42 PM, Meador Inge wrote:
>>
>> -- Forwarded message
On 02/11/2011 08:58 AM, Yoder Stuart-B08248 wrote:
-Original Message-
From: Meador Inge [mailto:mead...@gmail.com]
Sent: Thursday, February 10, 2011 9:26 PM
To: Benjamin Herrenschmidt
Cc: Yoder Stuart-B08248; devicetree-disc...@lists.ozlabs.org; linuxppc-
d...@lists.ozlabs.org
Subject
dev/mailbox1', '/dev/mailbox2', etc... mapping, for example.
Now I have the following questions:
1. Do others see value in this?
2. Does something like this already exist?
3. Is someone else already working on this?
Any feedback will be greatly appreciated.
--
Meador In
On 02/14/2011 04:01 AM, Jamie Iles wrote:
On Fri, Feb 11, 2011 at 03:19:51PM -0600, Meador Inge wrote:
1. Hardware specific bits somewhere under '.../arch/*'. Drivers
for the MPIC message registers on Power and OMAP4 mailboxes, for
example.
2. A higher le
done (i.e. U-Boot or device tree magic)?
--
Meador Inge | meador_inge AT mentor.com
Mentor Embedded | http://www.mentor.com/embedded-software
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
On 02/16/2011 01:24 PM, Scott Wood wrote:
On Wed, 16 Feb 2011 12:00:25 -0600
Meador Inge wrote:
Hi Kumar,
Quick question about the support for booting at a non-zero base address
(as committed here:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h
nonym for
"pic-no-reset" was added.
Signed-off-by: Meador Inge
Cc: Benjamin Herrenschmidt
Cc: Hollis Blanchard
Cc: Dave Kleikamp
Meador Inge (2):
powerpc: document the Open PIC device tree binding
powerpc: make MPIC honor the "pic-no-reset" de
quot;pic-no-reset" *and* "protected-sources" are both used, however, then
"pic-no-reset" takes precedence in terms of the init behavior and the
sanity checks done by protected sources will still take place.
Signed-off-by: Meador Inge
Cc: Hollis Blanchard
Cc: Benjamin Herrensc
e with OSes that are
already up and running.
The interrupt specifier definition is based off of Stuart Yoder's FSL MPIC
binding.
Signed-off-by: Meador Inge
Cc: Hollis Blanchard
Cc: Stuart Yoder
---
Documentation/powerpc/dts-bindings/open-pic.txt | 98 +++
1 files cha
ea was that either the boot program
would leave it masked or one of the AMP OSes would boot without
'pic-no-reset', which would mask everything. Most likely the boot program.
I think it would be kosher to mask it in set_type unconditi
synonym for
"pic-no-reset" was added.
Signed-off-by: Meador Inge
Cc: Benjamin Herrenschmidt
Cc: Hollis Blanchard
Meador Inge (3):
powerpc: document the Open PIC device tree binding
powerpc: make MPIC honor the "pic-no-reset" device tree property
powerpc: factoring
e with OSes that are
already up and running.
The interrupt specifier definition is based off of Stuart Yoder's FSL MPIC
binding.
Signed-off-by: Meador Inge
Cc: Grant Likely
Cc: Stuart Yoder
Cc: Hollis Blanchard
---
Documentation/devicetree/bindings/open-pic.txt | 98
quot;pic-no-reset" *and* "protected-sources" are both used, however, then
"pic-no-reset" takes precedence in terms of the init behavior and the
sanity checks done by protected sources will still take place.
Signed-off-by: Meador Inge
Cc: Hollis Blanchard
Cc: Benjamin Herrens
essor_id'.
Signed-off-by: Meador Inge
Cc: Benjamin Herrenschmidt
---
arch/powerpc/sysdev/mpic.c | 31 ++-
1 files changed, 14 insertions(+), 17 deletions(-)
diff --git a/arch/powerpc/sysdev/mpic.c b/arch/powerpc/sysdev/mpic.c
index 112bff0..bf77eb7 10064
the OpenMCAPI shared
memory driver to send notifications between cores.
Signed-off-by: Meador Inge
Cc: Hollis Blanchard
Meador Inge (2):
powerpc: document the FSL MPIC message register binding
powerpc: add support for MPIC message register API
.../devicetree/bindings/powerpc/fsl/mpic
This binding documents how the message register blocks found in some FSL
MPIC implementations shall be represented in a device tree.
Signed-off-by: Meador Inge
Cc: Hollis Blanchard
Cc: Grant Likely
Cc: Benjamin Herrenschmidt
---
.../devicetree/bindings/powerpc/fsl/mpic-msgr.txt | 71
device tree. A separate commit contains a binding for the message register
nodes.
Signed-off-by: Meador Inge
Cc: Benjamin Herrenschmidt
Cc: Hollis Blanchard
---
arch/powerpc/include/asm/mpic_msgr.h | 35 +
arch/powerpc/platforms/Kconfig |8 +
arch/powerpc/sysdev/Makefile
On 04/19/2011 12:52 PM, Scott Wood wrote:
> On Tue, 19 Apr 2011 11:59:34 -0500
> Meador Inge wrote:
>
>> +- interrupt-parent: Specifies the interrupt parent of the message
>> register
>> + block. The type shall be a and the value of that
>> + sh
On 04/19/2011 01:33 PM, Scott Wood wrote:
> On Tue, 19 Apr 2011 13:26:26 -0500
> Meador Inge wrote:
>
>> On 04/19/2011 12:52 PM, Scott Wood wrote:
>>> On Tue, 19 Apr 2011 11:59:34 -0500
>>> Meador Inge wrote:
>>>
>>>> Aliases are of
<0xb0 2 0xb2 2>;
mpic-msgr-receive-mask = <0x5>;
};
Now OS 1 has registers 0 and 2 available for general allocation, which
OS 2 is receiving on. However, we already have that problem if someone
botches the masks. So I am not very worried about that.
ree-mask would be
> a subset of both the send and receive masks.
free-mask seems reasonable. Although, all of these masks are starting to get
rather complicated :-)
Anyway, I am going to cut a v2 patch without the dynamic allocation. All
of this is getting complicated without a public use c
ing.
* Fixed some example bugs with receive masks.
Signed-off-by: Meador Inge
Cc: Hollis Blanchard
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 +
This binding documents how the message register blocks found in some FSL
MPIC implementations shall be represented in a device tree.
Signed-off-by: Meador Inge
Cc: Hollis Blanchard
Cc: Grant Likely
Cc: Benjamin Herrenschmidt
---
.../devicetree/bindings/powerpc/fsl/mpic-msgr.txt | 62
device tree. A separate commit contains a binding for the message register
nodes.
Signed-off-by: Meador Inge
Cc: Benjamin Herrenschmidt
Cc: Hollis Blanchard
---
arch/powerpc/include/asm/mpic_msgr.h | 35 +
arch/powerpc/platforms/Kconfig |8 +
arch/powerpc/sysdev/Makefile
t-parent' from binding.
> * Fixed some example bugs with receive masks.
>
> Signed-off-by: Meador Inge
> Cc: Hollis Blanchard
>
> Meador Inge (2):
> powerpc: document the FSL MPIC message register binding
> powerpc: add support for MPIC message register API
>
.
* 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
Cc: Hollis Blanchard
Meador Inge (2):
powerpc: document the FSL MPIC message r
This binding documents how the message register blocks found in some FSL
MPIC implementations shall be represented in a device tree.
Signed-off-by: Meador Inge
Cc: Hollis Blanchard
Cc: Grant Likely
Cc: Benjamin Herrenschmidt
Cc: Scott Wood
---
.../devicetree/bindings/powerpc/fsl/mpic
device tree. A separate commit contains a binding for the message register
nodes.
Signed-off-by: Meador Inge
Cc: Benjamin Herrenschmidt
Cc: Hollis Blanchard
---
arch/powerpc/include/asm/mpic_msgr.h | 35 +
arch/powerpc/platforms/Kconfig |8 +
arch/powerpc/sysdev/Makefile
>> > + the message registers in the block are available.
> ...and mpic-msgr-receive-mask here.
>
> Might want to just say "equal to the number of registers that are
> available for receiving interrupts", to more clearly apply to the case where
> mpic-msgr-receive-m
On 05/31/2011 02:23 PM, Scott Wood wrote:
> On Tue, 31 May 2011 14:19:02 -0500
> Meador Inge wrote:
>
>> This binding documents how the message register blocks found in some FSL
>> MPIC implementations shall be represented in a device tree.
>>
>> Signed-o
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
On 06/17/2011 12:33 AM, Benjamin Herrenschmidt wrote:
> On Tue, 2011-05-31 at 14:19 -0500, Meador Inge wrote:
>> 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 add
On 06/17/2011 12:33 AM, Benjamin Herrenschmidt wrote:
> On Tue, 2011-05-31 at 14:19 -0500, Meador Inge wrote:
>> 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 add
64 matches
Mail list logo
