Re: [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region

On 12/02/18 19:17, Robin Murphy wrote: > On 12/02/18 18:27, Marc Zyngier wrote: >> Hi Sudeep, >> >> On 12/02/18 18:17, Sudeep Holla wrote: >>> >>> >>> On 07/02/18 14:32, Marc Zyngier wrote: From: Robin Murphy Juno's GICv2m implementation consists of four

Re: [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region

On 12/02/18 19:17, Robin Murphy wrote: > On 12/02/18 18:27, Marc Zyngier wrote: >> Hi Sudeep, >> >> On 12/02/18 18:17, Sudeep Holla wrote: >>> >>> >>> On 07/02/18 14:32, Marc Zyngier wrote: From: Robin Murphy Juno's GICv2m implementation consists of four frames providing 32

Re: [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region

On 12/02/18 18:27, Marc Zyngier wrote: Hi Sudeep, On 12/02/18 18:17, Sudeep Holla wrote: On 07/02/18 14:32, Marc Zyngier wrote: From: Robin Murphy Juno's GICv2m implementation consists of four frames providing 32 interrupts each. Since it is possible to plug in

Re: [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region

On 12/02/18 18:27, Marc Zyngier wrote: Hi Sudeep, On 12/02/18 18:17, Sudeep Holla wrote: On 07/02/18 14:32, Marc Zyngier wrote: From: Robin Murphy Juno's GICv2m implementation consists of four frames providing 32 interrupts each. Since it is possible to plug in enough PCIe endpoints to

Re: [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region

Hi Sudeep, On 12/02/18 18:17, Sudeep Holla wrote: > > > On 07/02/18 14:32, Marc Zyngier wrote: >> From: Robin Murphy >> >> Juno's GICv2m implementation consists of four frames providing 32 >> interrupts each. Since it is possible to plug in enough PCIe endpoints >> to

Re: [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region

Hi Sudeep, On 12/02/18 18:17, Sudeep Holla wrote: > > > On 07/02/18 14:32, Marc Zyngier wrote: >> From: Robin Murphy >> >> 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

Re: [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region

Hi Robin, On 12/02/18 18:22, Robin Murphy wrote: > On 12/02/18 18:17, Sudeep Holla wrote: >> >> >> On 07/02/18 14:32, Marc Zyngier wrote: >>> From: Robin Murphy >>> >>> Juno's GICv2m implementation consists of four frames providing 32 >>> interrupts each. Since it is

Re: [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region

Hi Robin, On 12/02/18 18:22, Robin Murphy wrote: > On 12/02/18 18:17, Sudeep Holla wrote: >> >> >> On 07/02/18 14:32, Marc Zyngier wrote: >>> From: Robin Murphy >>> >>> Juno's GICv2m implementation consists of four frames providing 32 >>> interrupts each. Since it is possible to plug in enough

Re: [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region

On 12/02/18 18:17, Sudeep Holla wrote: On 07/02/18 14:32, Marc Zyngier wrote: From: Robin Murphy 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

Re: [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region

On 12/02/18 18:17, Sudeep Holla wrote: On 07/02/18 14:32, Marc Zyngier wrote: From: Robin Murphy 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

Re: [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region

On 07/02/18 14:32, Marc Zyngier wrote: > From: Robin Murphy > > 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

Re: [PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region

On 07/02/18 14:32, Marc Zyngier wrote: > From: Robin Murphy > > 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

[PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region

From: Robin Murphy 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

[PATCH 2/2] arm64: dts: juno: Describe the full GICv2m region

From: Robin Murphy 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.