All of lore.kernel.org
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: marvell: add Device Tree files for Armada-8KP
Date: Wed, 09 Aug 2017 11:20:42 +0100	[thread overview]
Message-ID: <86inhxxcsl.fsf@arm.com> (raw)
In-Reply-To: <022fd386-a9a9-6f9d-27a9-3a63b5a81bbf@marvell.com> (Hanna Hawa's message of "Wed, 9 Aug 2017 09:29:25 +0300")

On Wed, Aug 09 2017 at  9:29:25 am BST, Hanna Hawa <hannah@marvell.com> wrote:
> On 08/08/2017 04:06 PM, Marc Zyngier wrote:
>> On 08/08/17 13:31, hannah at marvell.com wrote:

[...]

>>> +				ranges;
>>> +
>>> +				reg = <0x3000000 0x10000>,     /* GICD */
>>> +				      <0x3060000 0x100000>;    /* GICR */
>>
>> Where is the GICv2 compatibility region (GICV)that is provided by each
>> A72 cores? It should be at PERIPHBASE+0x20000 (see
>> http://infocenter.arm.com/help/topic/com.arm.doc.100095_0003_06_en/way1382452674438.html).
> Currently virtualization out of our focus, I add GICV region & it not
> tested.

To be completely blunt, this is a bit out of your hands. The HW exists
(it is part of the Cortex-A72 core), and it should be described. If it
doesn't work for one reason or another, then this is a defect and we
should treat it as such.

Also, you do describe the maintenance interrupt, whose sole purpose is
to support virtualization.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny.

      reply	other threads:[~2017-08-09 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08 12:31 [PATCH] arm64: dts: marvell: add Device Tree files for Armada-8KP hannah at marvell.com
2017-08-08 13:06 ` Marc Zyngier
2017-08-09  6:29   ` Hanna Hawa
2017-08-09 10:20     ` Marc Zyngier [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=86inhxxcsl.fsf@arm.com \
    --to=marc.zyngier@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.