linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/4] arm64: dts: add interrupt-affinity property to pmu node for juno
Date: Fri, 27 Mar 2015 17:33:19 +0000	[thread overview]
Message-ID: <20150327173319.GP1562@arm.com> (raw)
In-Reply-To: <20150324150528.GE29342@arm.com>

On Tue, Mar 24, 2015 at 03:05:28PM +0000, Will Deacon wrote:
> [adding arm-soc folks]
> 
> Hi Arnd, Olof,
> 
> Could you take this Juno .dts patch via arm-soc for 4.1 please? I'll queue
> the perf code to make use of the new binding, but there's not a strict
> dependency (the interrupt-affinity property will be ignored by older
> kernels).

Gentle ping, although I guess most people were tied up with ELC/ACPI this
week.

Happy to resend the patch if necessary.

Will

> On Fri, Mar 06, 2015 at 11:54:11AM +0000, Will Deacon wrote:
> > Make the Juno .dts robust against potential reordering of the CPU nodes
> > by adding an explicit interrupt-affinity property to the PMU node. While
> > we're at it, fix the PMU interrupts numbers too.
> > 
> > Cc: Mark Rutland <mark.rutland@arm.com>
> > Acked-by: Liviu Dudau <liviu.dudau@arm.com>
> > Signed-off-by: Will Deacon <will.deacon@arm.com>
> > ---
> >  arch/arm64/boot/dts/arm/juno.dts | 14 ++++++++++----
> >  1 file changed, 10 insertions(+), 4 deletions(-)
> > 
> > diff --git a/arch/arm64/boot/dts/arm/juno.dts b/arch/arm64/boot/dts/arm/juno.dts
> > index 133ee59de2d7..5e9110a3353d 100644
> > --- a/arch/arm64/boot/dts/arm/juno.dts
> > +++ b/arch/arm64/boot/dts/arm/juno.dts
> > @@ -120,12 +120,18 @@
> >  
> >  	pmu {
> >  		compatible = "arm,armv8-pmuv3";
> > -		interrupts = <GIC_SPI 18 IRQ_TYPE_LEVEL_HIGH>,
> > +		interrupts = <GIC_SPI 02 IRQ_TYPE_LEVEL_HIGH>,
> > +			     <GIC_SPI 06 IRQ_TYPE_LEVEL_HIGH>,
> > +			     <GIC_SPI 18 IRQ_TYPE_LEVEL_HIGH>,
> >  			     <GIC_SPI 22 IRQ_TYPE_LEVEL_HIGH>,
> >  			     <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>,
> > -			     <GIC_SPI 30 IRQ_TYPE_LEVEL_HIGH>,
> > -			     <GIC_SPI 02 IRQ_TYPE_LEVEL_HIGH>,
> > -			     <GIC_SPI 06 IRQ_TYPE_LEVEL_HIGH>;
> > +			     <GIC_SPI 30 IRQ_TYPE_LEVEL_HIGH>;
> > +		interrupt-affinity = <&A57_0>,
> > +				     <&A57_1>,
> > +				     <&A53_0>,
> > +				     <&A53_1>,
> > +				     <&A53_2>,
> > +				     <&A53_3>;
> >  	};
> >  
> >  	/include/ "juno-clocks.dtsi"
> > -- 
> > 2.1.4
> > 

  reply	other threads:[~2015-03-27 17:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06 11:54 [PATCH v3 0/4] Fix PMU interrupt affinity for Juno* Will Deacon
2015-03-06 11:54 ` [PATCH v3 1/4] dt: pmu: extend ARM PMU binding to allow for explicit interrupt affinity Will Deacon
2015-03-06 11:54 ` [PATCH v3 2/4] ARM: pmu: add support for interrupt-affinity property Will Deacon
2015-03-06 11:54 ` [PATCH v3 3/4] arm64: " Will Deacon
2015-03-06 11:54 ` [PATCH v3 4/4] arm64: dts: add interrupt-affinity property to pmu node for juno Will Deacon
2015-03-24 15:05   ` Will Deacon
2015-03-27 17:33     ` Will Deacon [this message]
2015-03-29 21:00       ` Olof Johansson

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=20150327173319.GP1562@arm.com \
    --to=will.deacon@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 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).