devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Peter Chen <peter.chen@cixtech.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	catalin.marinas@arm.com, will@kernel.org, arnd@arndb.de,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, cix-kernel-upstream@cixtech.com,
	marcin@juszkiewicz.com.pl,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Fugang Duan <fugang.duan@cixtech.com>
Subject: Re: [PATCH v4 5/6] arm64: dts: cix: add initial CIX P1(SKY1) dts support
Date: Thu, 20 Mar 2025 09:36:37 +0000	[thread overview]
Message-ID: <86frj8m4be.wl-maz@kernel.org> (raw)
In-Reply-To: <20250305053823.2048217-6-peter.chen@cixtech.com>

On Wed, 05 Mar 2025 05:38:22 +0000,
Peter Chen <peter.chen@cixtech.com> wrote:
> 
> +	pmu-a520 {
> +		compatible = "arm,cortex-a520-pmu";
> +		interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_LOW &ppi_partition0>;
> +	};
> +
> +	pmu-a720 {
> +		compatible = "arm,cortex-a720-pmu";
> +		interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_LOW &ppi_partition1>;
> +	};
> +
> +	pmu-spe {
> +		compatible = "arm,statistical-profiling-extension-v1";
> +		interrupts = <GIC_PPI 5 IRQ_TYPE_LEVEL_LOW 0>;
> +	};

SPE should follow the same model as the PMU, as each CPU has its own
SPE implementation, exposing different micro-architectural details.

The rest looks OK.

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2025-03-20  9:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05  5:38 [PATCH v4 0/6] arm64: Introduce CIX P1 (SKY1) SoC Peter Chen
2025-03-05  5:38 ` [PATCH v4 1/6] dt-bindings: vendor-prefixes: Add CIX Technology Group Co., Ltd Peter Chen
2025-03-05  5:38 ` [PATCH v4 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC Peter Chen
2025-03-05  5:38 ` [PATCH v4 3/6] arm64: Kconfig: add ARCH_CIX for cix silicons Peter Chen
2025-03-05  5:38 ` [PATCH v4 4/6] arm64: defconfig: Enable CIX SoC Peter Chen
2025-03-05  5:38 ` [PATCH v4 5/6] arm64: dts: cix: add initial CIX P1(SKY1) dts support Peter Chen
2025-03-20  9:36   ` Marc Zyngier [this message]
2025-03-20  9:57     ` Peter Chen
2025-03-21  9:04       ` Marc Zyngier
2025-03-21 10:31         ` Peter Chen
2025-03-21 11:01           ` Marc Zyngier
2025-03-05  5:38 ` [PATCH v4 6/6] MAINTAINERS: Add CIX SoC maintainer entry Peter Chen
2025-03-20  9:25   ` Krzysztof Kozlowski
2025-03-20 10:49     ` Peter Chen
2025-03-20 15:28       ` Kajetan Puchalski
2025-03-21  1:40         ` Peter Chen
2025-03-20 16:20       ` Krzysztof Kozlowski
2025-03-21  9:00   ` Arnd Bergmann
2025-03-11  1:02 ` [PATCH v4 0/6] arm64: Introduce CIX P1 (SKY1) SoC Peter Chen
2025-03-17  1:38   ` Peter Chen

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=86frj8m4be.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=cix-kernel-upstream@cixtech.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fugang.duan@cixtech.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin@juszkiewicz.com.pl \
    --cc=peter.chen@cixtech.com \
    --cc=robh@kernel.org \
    --cc=will@kernel.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).