linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Suravee.Suthikulpanit@amd.com (Suthikulpanit, Suravee)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3] arm64: amd-seattle: Adding device tree for AMD Seattle platform
Date: Fri, 21 Nov 2014 16:25:55 +0000	[thread overview]
Message-ID: <D09577B0.9B9B%suravee.suthikulpanit@amd.com> (raw)
In-Reply-To: <546F50BD.8070501@arm.com>



On 11/21/14, 21:48, "Marc Zyngier" <marc.zyngier@arm.com> wrote:

>On 21/11/14 14:40, Suthikulpanit, Suravee wrote:
>> 
>> 
>> On 11/21/14, 19:57, "Marc Zyngier" <marc.zyngier@arm.com> wrote:
>> 
>>>> +	gic: interrupt-controller at e1101000 {
>>>> +		compatible = "arm,gic-400", "arm,cortex-a15-gic";
>>>> +		interrupt-controller;
>>>> +		#interrupt-cells = <3>;
>>>> +		#address-cells = <2>;
>>>> +		#size-cells = <2>;
>>>> +		reg = <0x0 0xe1110000 0 0x1000>,
>>>> +		      <0x0 0xe112f000 0 0x2000>,
>>>> +		      <0x0 0xe1140000 0 0x10000>,
>>>> +		      <0x0 0xe1160000 0 0x10000>;
>>>> +		interrupts = <1 8 0xf04>;
>>>
>>> Are you sure about this one? ARM systems usually have this wired on
>>>PPI9
>>> (interrupt 25)...
>>>
>>> Thanks,
>>>
>>> 	M.
>> 
>> I think you might be right. GIC-400 TRM says that this is should be
>> 25, and used for virtual maintenance interrupts. How can I verify
>> this in Linux? KVM?
>
>KVM is one way, but you'll never see the interrupt firing (we kill the
>interrupt while in HYP, before the kernel gets a chance to see it).
>
>If you effectively have GIC400 on this system, then I know for sure this
>is interrupt 25.

I?ll make the change. Thanks for clarification.

Suravee
>
>Thanks,
>
>	M.
>-- 
>Jazz is not dead. It just smells funny...

  reply	other threads:[~2014-11-21 16:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 13:36 [PATCH V3] arm64: amd-seattle: Adding device tree for AMD Seattle platform suravee.suthikulpanit at amd.com
2014-11-11  1:24 ` Suravee Suthikulpanit
2014-11-13 11:00   ` Catalin Marinas
2014-11-20 12:33     ` Arnd Bergmann
2014-11-13 11:29 ` Arnd Bergmann
2014-11-20 15:16   ` Rob Herring
2014-11-20 15:23     ` Arnd Bergmann
2014-11-21 12:57 ` Marc Zyngier
2014-11-21 14:40   ` Suthikulpanit, Suravee
2014-11-21 14:48     ` Marc Zyngier
2014-11-21 16:25       ` Suthikulpanit, Suravee [this message]
     [not found] <5468032C.8020505@amd.com>
2014-11-21 12:38 ` Arnd Bergmann

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=D09577B0.9B9B%suravee.suthikulpanit@amd.com \
    --to=suravee.suthikulpanit@amd.com \
    --cc=linux-arm-kernel@lists.infradead.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).