All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Liviu Dudau <liviu.dudau@arm.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region
Date: Mon, 12 Feb 2018 18:17:13 +0000	[thread overview]
Message-ID: <d10fa874-1de2-1b95-dae1-42a336b98fa2@arm.com> (raw)
In-Reply-To: <20180207143255.17003-3-marc.zyngier@arm.com>



On 07/02/18 14:32, Marc Zyngier wrote:
> From: Robin Murphy <robin.murphy@arm.com>
> 
> Juno's GICv2m implementation consists of four frames providing 32
> interrupts each. Since it is possible to plug in enough PCIe endpoints
> to consume more than 32 MSIs, and the driver already has a bodge to
> handle multiple frames, let's expose the other three as well.
> 

Change on it own looks good. So if you want to merge via your tree:

Acked-by: Sudeep Holla <sudeep.holla@arm.com>

Let me know if you decide not to take it via your tree and you want me
to send it to arm-soc.

On the side note I just noticed the Juno TRM[1] has 64k for each of
these MSI frames(page 3-24 section 3.3.5 Application memory map summary)

I am not sure if TRM is wrong. This patch is just copying the 4k size
from frame 0 which got added with initial Juno DTS.

-- 
Regards,
Sudeep

[1]
http://infocenter.arm.com/help/topic/com.arm.doc.ddi0515f/DDI0515F_juno_arm_development_platform_soc_trm.pdf

WARNING: multiple messages have this Message-ID (diff)
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region
Date: Mon, 12 Feb 2018 18:17:13 +0000	[thread overview]
Message-ID: <d10fa874-1de2-1b95-dae1-42a336b98fa2@arm.com> (raw)
In-Reply-To: <20180207143255.17003-3-marc.zyngier@arm.com>



On 07/02/18 14:32, Marc Zyngier wrote:
> From: Robin Murphy <robin.murphy@arm.com>
> 
> Juno's GICv2m implementation consists of four frames providing 32
> interrupts each. Since it is possible to plug in enough PCIe endpoints
> to consume more than 32 MSIs, and the driver already has a bodge to
> handle multiple frames, let's expose the other three as well.
> 

Change on it own looks good. So if you want to merge via your tree:

Acked-by: Sudeep Holla <sudeep.holla@arm.com>

Let me know if you decide not to take it via your tree and you want me
to send it to arm-soc.

On the side note I just noticed the Juno TRM[1] has 64k for each of
these MSI frames(page 3-24 section 3.3.5 Application memory map summary)

I am not sure if TRM is wrong. This patch is just copying the 4k size
from frame 0 which got added with initial Juno DTS.

-- 
Regards,
Sudeep

[1]
http://infocenter.arm.com/help/topic/com.arm.doc.ddi0515f/DDI0515F_juno_arm_development_platform_soc_trm.pdf

  reply	other threads:[~2018-02-12 18:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 14:32 [PATCH 0/2] irqchip: GICv2m Multi-MSI support Marc Zyngier
2018-02-07 14:32 ` Marc Zyngier
2018-02-07 14:32 ` [PATCH 1/2] irqchip/gic-v2m: Add PCI " Marc Zyngier
2018-02-07 14:32   ` Marc Zyngier
2018-02-07 15:18   ` Liviu Dudau
2018-02-07 15:18     ` Liviu Dudau
2018-02-07 14:32 ` [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region Marc Zyngier
2018-02-07 14:32   ` Marc Zyngier
2018-02-12 18:17   ` Sudeep Holla [this message]
2018-02-12 18:17     ` Sudeep Holla
2018-02-12 18:22     ` Robin Murphy
2018-02-12 18:22       ` Robin Murphy
2018-02-12 18:26       ` Sudeep Holla
2018-02-12 18:26         ` Sudeep Holla
2018-02-12 18:27     ` Marc Zyngier
2018-02-12 18:27       ` Marc Zyngier
2018-02-12 19:17       ` Robin Murphy
2018-02-12 19:17         ` Robin Murphy
2018-02-28 15:48         ` Sudeep Holla
2018-02-28 15:48           ` Sudeep Holla
2018-02-28 15:48   ` [PATCH] arm64: dts: juno: fix size of GICv2m MSI frames Sudeep Holla
2018-02-28 15:48     ` Sudeep Holla
2018-02-28 15:51     ` Robin Murphy
2018-02-28 15:51       ` Robin Murphy
2018-02-28 15:58       ` Sudeep Holla
2018-02-28 15:58         ` Sudeep Holla
2018-02-28 16:54     ` Marc Zyngier
2018-02-28 16:54       ` Marc Zyngier

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=d10fa874-1de2-1b95-dae1-42a336b98fa2@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liviu.dudau@arm.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=marc.zyngier@arm.com \
    --cc=robin.murphy@arm.com \
    --cc=tglx@linutronix.de \
    /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.