From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Diana Craciun <diana.craciun@freescale.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/dts: Added aliased MSIIR register address to MSI node in dts
Date: Fri, 16 Mar 2012 14:42:51 -0500 [thread overview]
Message-ID: <4F6397BB.7080802@freescale.com> (raw)
In-Reply-To: <9D3E9651-1D03-4079-98D9-B08D46306879@kernel.crashing.org>
On 03/16/2012 02:32 PM, Kumar Gala wrote:
>
> On Feb 1, 2012, at 9:50 AM, Diana Craciun wrote:
>
>> From: Diana CRACIUN <Diana.Craciun@freescale.com>
>>
>> The MSIIR register for each MSI bank is aliased to a different
>> address. The MSI node reg property was updated to contain this
>> address:
>>
>> e.g. reg = <0x41600 0x200 0x44140 4>;
>>
>> The first region contains the address and length of the MSI
>> register set and the second region contains the address of
>> the aliased MSIIR register at 0x44140.
>>
>> Signed-off-by: Diana CRACIUN <Diana.Craciun@freescale.com>
>> ---
>> .../devicetree/bindings/powerpc/fsl/msi-pic.txt | 6 ++++--
>> arch/powerpc/boot/dts/fsl/qoriq-mpic.dtsi | 6 +++---
>> 2 files changed, 7 insertions(+), 5 deletions(-)
>
> Why, we should only use one of the register regions. The second region was added to allow for 4k separation and thus PAMU protection. Not sure what listed both regions gets us.
We list both because the hardware has both. Device tree describes the
hardware; it doesn't tell you how to use it.
Plus, the separte 4K page has only the MSIIRn register, not the other
MSI registers. So we still need the first resource.
The second resource will probably not be used by Linux at the moment,
but it used by Topaz, and it may be used by KVM/VFIO in the future.
-Scott
prev parent reply other threads:[~2012-03-16 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 15:50 [PATCH] powerpc/dts: Added aliased MSIIR register address to MSI node in dts Diana Craciun
2012-03-16 19:32 ` Kumar Gala
2012-03-16 19:42 ` Scott Wood [this message]
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=4F6397BB.7080802@freescale.com \
--to=scottwood@freescale.com \
--cc=diana.craciun@freescale.com \
--cc=galak@kernel.crashing.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).