Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-18.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F29B1C4338F for ; Mon, 26 Jul 2021 07:13:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id DA03D60F44 for ; Mon, 26 Jul 2021 07:13:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231902AbhGZGcf (ORCPT ); Mon, 26 Jul 2021 02:32:35 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:58667 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231332AbhGZGce (ORCPT ); Mon, 26 Jul 2021 02:32:34 -0400 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 688025C010A; Mon, 26 Jul 2021 03:13:03 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 26 Jul 2021 03:13:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=traverse.com.au; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; s=fm1; bh=XGXySQXk0njgc 3zuMDvI8hFGu0ZsjKRJKHONoj+sjhY=; b=eKozgajZfbcpTkOstPn8yJm42kdcg /fKLuVgBYtREfJDsKs/c69JzKChti2VeNgfEa0tjeAzvcfTjzulDmlRRvgjHDGaQ zDW9Vq0qmMRFOasjruUF0ltQcDEdH9ndpMAtxJoGLz0jgtXDILyDfq7odgyKowLQ Bzy8i/vuVw5xM0wlMHUXHAkpzEhv0GHpW6oc4GelmR3GJJQsrIurKRYTeUv3pu7O fuoYIW5jnTgA7zCd60+dY/odJDxOF67qAfe8ZBtf5Wx7QNQcXp9eZPjjaBJM2BD4 Kdj7ZFYcliRJ96iyu/syYIlacYAi2Rb/B6syG3YVgcoBWl4kIa9tKMzJA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:date:from :in-reply-to:message-id:mime-version:references:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=XGXySQXk0njgc3zuMDvI8hFGu0ZsjKRJKHONoj+sjhY=; b=GuD+WNdU RBefUnEBGLJqkIbFkKyfCQkGjSgaqU2Qaz4DyzkXTPdWL7Na6+dCdPPS0+yOihgV JRGvjPeaIG/vAoPAisp9YtySLmLs3P6sjoP4Gy4TMhKw+udLoUz0uPzLqFNDOUts syk6Cz2BvS8/HZE8tPcV8AHbp8wze0wCPVpCiRDKv3n0XitjQOzVpDOU2ZPT83d6 OAZsvA/r+bSNk4Cc5c2wpxw+SLs2VaOtBuVSaE7pGJSHtSaUuPP7r5VadeevR7f1 DobKsTuxFWZSUhWeoyzpiruafa24SoZ8E2FRzNyfKue+k7Azj12cY59uGgY1Ycwm 0U5h5VZ8w83a2g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrgeeggdduuddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkffojghfggfgsedtkeertdertddtnecuhfhrohhmpeforghthhgv ficuofgtuehrihguvgcuoehmrghtthesthhrrghvvghrshgvrdgtohhmrdgruheqnecugg ftrfgrthhtvghrnhepkeelveetledvudehtefgvdefleeukeffgeegteehtdetleejieev vdfgheejjeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepmhgrthhtsehtrhgrvhgvrhhsvgdrtghomhdrrghu X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 26 Jul 2021 03:13:00 -0400 (EDT) From: Mathew McBride To: Shawn Guo , Li Yang , Ioana Ciornei , Rob Herring , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org Cc: Mathew McBride Subject: [PATCH v2 2/5] arm64: dts: ls1088a: add missing PMU node Date: Mon, 26 Jul 2021 07:12:13 +0000 Message-Id: <20210726071216.22711-3-matt@traverse.com.au> X-Mailer: git-send-email 2.30.1 In-Reply-To: <20210726071216.22711-1-matt@traverse.com.au> References: <20210722042450.11862-1-matt@traverse.com.au> <20210726071216.22711-1-matt@traverse.com.au> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org The Performance Manager Unit was not described in the DTS which meant performance event monitoring was not possible. This was exposed by a change to the PMU handling in KVM in 5.11-rc3 which now prevents a PMU being exposed to a guest when the host does not provide one: "KVM: arm64: Don't access PMCR_EL0 when no PMU is available" Signed-off-by: Mathew McBride --- arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi b/arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi index 79ceadc9dc4a..f85e437f80b7 100644 --- a/arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi +++ b/arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi @@ -189,6 +189,11 @@ timer { <1 10 IRQ_TYPE_LEVEL_LOW>;/* Hypervisor PPI */ }; + pmu { + compatible = "arm,cortex-a53-pmu"; + interrupts = ; + }; + psci { compatible = "arm,psci-0.2"; method = "smc"; -- 2.30.1