From: Lucas Stach <l.stach@pengutronix.de>
To: Stefan Agner <stefan@agner.ch>,
shawnguo@kernel.org, s.hauer@pengutronix.de
Cc: max.krummenacher@toradex.com, marcel.ziswiler@toradex.com,
linux-kernel@vger.kernel.org, linux-imx@nxp.com,
kernel@pengutronix.de, fabio.estevam@nxp.com, dev@pschenker.ch,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: dts: imx6q: add pmu interrupt-affinity
Date: Fri, 18 Jan 2019 15:12:13 +0100 [thread overview]
Message-ID: <1547820733.2626.11.camel@pengutronix.de> (raw)
In-Reply-To: <20190118135907.2336-1-stefan@agner.ch>
Am Freitag, den 18.01.2019, 14:59 +0100 schrieb Stefan Agner:
> Explicitly specify interrupt affinity to avoid HW perfevents
> need to guess. This avoids the following error upon boot:
> hw perfevents: no interrupt-affinity property for /pmu, guessing.
>
But then it isn't correct either AFAICS. On i.MX6 all the PMU IRQs are
ORed together into a single SPI, instead of each core dealing with its
own PPI. So pretending that there are more IRQs with affinity to each
core isn't the right thing to do, no?
Regards,
Lucas
> Specifying all four CPUs shows no aversive effects on i.MX 6Dual
> SoCs.
>
> > Signed-off-by: Stefan Agner <stefan@agner.ch>
> ---
> arch/arm/boot/dts/imx6q.dtsi | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm/boot/dts/imx6q.dtsi b/arch/arm/boot/dts/imx6q.dtsi
> index 8381d24eff7d..d2c1977c8b16 100644
> --- a/arch/arm/boot/dts/imx6q.dtsi
> +++ b/arch/arm/boot/dts/imx6q.dtsi
> @@ -537,6 +537,13 @@
> > <0x28 0x0000000c>; /* DCIC2_MUX_CTL */
> };
>
> +&pmu {
> > > + interrupt-affinity = <&{/cpus/cpu@0}>,
> > > + <&{/cpus/cpu@1}>,
> > > + <&{/cpus/cpu@2}>,
> > > + <&{/cpus/cpu@3}>;
> +};
> +
> &vpu {
> > compatible = "fsl,imx6q-vpu", "cnm,coda960";
> };
next prev parent reply other threads:[~2019-01-18 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 13:59 Stefan Agner
2019-01-18 13:59 ` [PATCH 2/2] ARM: dts: imx6dl: " Stefan Agner
2019-01-18 14:12 ` Lucas Stach [this message]
2019-01-18 15:41 ` [PATCH 1/2] ARM: dts: imx6q: " Stefan Agner
2019-01-21 9:39 ` Stefan Agner
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=1547820733.2626.11.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=dev@pschenker.ch \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=max.krummenacher@toradex.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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
all inboxes | Powered by JetHome®