From: Meador Inge <meador_inge@mentor.com>
To: Yoder Stuart-B08248 <B08248@freescale.com>
Cc: "Blanchard, Hollis" <Hollis_Blanchard@mentor.com>,
Wood Scott-B07421 <B07421@freescale.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 1/2] powerpc: document the MPIC device tree binding
Date: Wed, 19 Jan 2011 18:08:03 -0600 [thread overview]
Message-ID: <4D377CE3.6000608@mentor.com> (raw)
In-Reply-To: <9F6FE96B71CF29479FF1CDC8046E150306BF11@039-SN1MPN1-004.039d.mgd.msft.net>
On 01/19/2011 04:14 PM, Yoder Stuart-B08248 wrote:
>
>> +** Optional properties:
>> +
>> + - no-reset : The presence of this property indicates that the MPIC
>> + should not be reset during runtime initialization.
>> + - protected-sources : Specifies a list of interrupt sources that are
>> + not
>> + available for use and whose corresponding
>> + vectors
>> + should not be initialized. A typical use case
>> + for
>> + this property is in AMP systems where multiple
>> + independent operating systems need to share
>> + the MPIC
>> + without clobbering each other.
>
> Is "protected-sources" really needed for AMP systems to
> tell the OSes not to clobber each other? Won't each
> OS be given a device tree with only its interrupt
> sources? ...so you know what you are allowed to touch.
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-software
[1]
http://lists.ozlabs.org/pipermail/devicetree-discuss/2010-December/003850.html
[2]
http://lists.ozlabs.org/pipermail/devicetree-discuss/2011-January/003936.html
next prev parent reply other threads:[~2011-01-20 0:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 0:52 [PATCH 1/2] powerpc: document the MPIC device tree binding Meador Inge
2011-01-18 20:31 ` Scott Wood
[not found] ` <AANLkTi=QX4BfLvPfQDMOgmh90TtX4MQqio6AOZR8JKas@mail.gmail.com>
2011-01-18 20:21 ` Yoder Stuart-B08248
2011-01-19 20:24 ` Meador Inge
2011-01-19 20:38 ` Yoder Stuart-B08248
2011-01-19 22:14 ` Yoder Stuart-B08248
2011-01-20 0:08 ` Meador Inge [this message]
2011-01-20 15:50 ` Yoder Stuart-B08248
2011-01-27 23:50 ` Meador Inge
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=4D377CE3.6000608@mentor.com \
--to=meador_inge@mentor.com \
--cc=B07421@freescale.com \
--cc=B08248@freescale.com \
--cc=Hollis_Blanchard@mentor.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).