From: Michal Simek <michal.simek@amd.com>
To: linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, git@xilinx.com
Cc: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>,
Conor Dooley <conor+dt@kernel.org>,
Harini Katakam <harini.katakam@amd.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Michael Grzeschik <m.grzeschik@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Robert Hancock <robert.hancock@calian.com>,
Tanmay Shah <tanmay.shah@amd.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 5/6] arm64: zynqmp: Add pmu interrupt-affinity
Date: Mon, 5 Jun 2023 13:16:21 +0200 [thread overview]
Message-ID: <6a8c7157-9632-e07d-0ba3-ee55d73dd9e3@amd.com> (raw)
In-Reply-To: <dde2e4b5ac6018adb9bfae05bb3800af6b7c0f0e.1684767562.git.michal.simek@amd.com>
On 5/22/23 16:59, Michal Simek wrote:
> From: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
>
> Based on dt-binding "This property should present when there is more than a
> single SPI" that's also case that's why explicitly specify interrupt
> affinity to avoid incorrect usage.
>
> Signed-off-by: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
> Signed-off-by: Michal Simek <michal.simek@amd.com>
> ---
>
> Changes in v2:
> - Update commit message to remove OS content - reported by Laurent
>
> This avoids the following error upon linux boot:
> armv8-pmu pmu: hw perfevents: no interrupt-affinity property,
> guessing.
>
> ---
> arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
> index 02bd75900238..fc5e21bc647c 100644
> --- a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
> +++ b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
> @@ -164,6 +164,10 @@ pmu {
> <0 144 4>,
> <0 145 4>,
> <0 146 4>;
> + interrupt-affinity = <&cpu0>,
> + <&cpu1>,
> + <&cpu2>,
> + <&cpu3>;
> };
>
> psci {
Applied.
M
next prev parent reply other threads:[~2023-06-05 11:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 14:59 [PATCH v2 0/6] arm64: zynqmp: Misc zynqmp changes Michal Simek
2023-05-22 14:59 ` [PATCH v2 1/6] arm64: zynqmp: Describe TI phy as ethernet-phy-id Michal Simek
2023-06-05 11:15 ` Michal Simek
2023-05-22 14:59 ` [PATCH v2 2/6] arm64: zynqmp: Fix usb node drive strength and slew rate Michal Simek
2023-06-05 11:15 ` Michal Simek
2023-05-22 14:59 ` [PATCH v2 3/6] arm64: zynqmp: Set qspi tx-buswidth to 4 Michal Simek
2023-06-05 11:16 ` Michal Simek
2023-05-22 14:59 ` [PATCH v2 4/6] arm64: zynqmp: Add L2 cache nodes Michal Simek
2023-05-23 7:48 ` Michal Simek
2023-05-22 14:59 ` [PATCH v2 5/6] arm64: zynqmp: Add pmu interrupt-affinity Michal Simek
2023-06-05 11:16 ` Michal Simek [this message]
2023-05-22 14:59 ` [PATCH v2 6/6] arm64: zynqmp: Used fixed-partitions for QSPI in k26 Michal Simek
2023-06-05 11:16 ` Michal Simek
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=6a8c7157-9632-e07d-0ba3-ee55d73dd9e3@amd.com \
--to=michal.simek@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=harini.katakam@amd.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.grzeschik@pengutronix.de \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=radhey.shyam.pandey@amd.com \
--cc=robert.hancock@calian.com \
--cc=robh+dt@kernel.org \
--cc=tanmay.shah@amd.com \
/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).