From: ddaney@caviumnetworks.com (David Daney)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 3/5] arm64: dts: Add Cavium ThunderX specific PMU
Date: Thu, 18 Feb 2016 10:37:45 -0800 [thread overview]
Message-ID: <56C60F79.5060908@caviumnetworks.com> (raw)
In-Reply-To: <20160218173248.GD16883@arm.com>
On 02/18/2016 09:32 AM, Will Deacon wrote:
> On Thu, Feb 18, 2016 at 05:50:12PM +0100, Jan Glauber wrote:
>> Add a compatible string for the Cavium ThunderX PMU.
>
> Stupid question, but is "thunder" the name of the CPU or the SoC or ...?
At a high level Cavium ThunderX (tm) is a family of SoCs. Since the SoC
contains many different functional blocks ...
>
> Whatever we use to describe the PMU, should probably also identify the
> CPU uniquely.
... In the context of this patch, "cavium,thunder-pmu" refers to the PMU
of Cavium's implementation of the ARMv8 Processing Element (PE)
specification (i.e. the CPU), as found on the CN88XX family of SoCs.
If we think of this in terms of MIDR_EL1, That would be:
Implementer: 0x43
PartNum: 0xA1
>
> Will
>
>> Signed-off-by: Jan Glauber <jglauber@cavium.com>
>> ---
>> Documentation/devicetree/bindings/arm/pmu.txt | 1 +
>> arch/arm64/boot/dts/cavium/thunder-88xx.dtsi | 5 +++++
>> 2 files changed, 6 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/pmu.txt b/Documentation/devicetree/bindings/arm/pmu.txt
>> index 5651883..d3999a1 100644
>> --- a/Documentation/devicetree/bindings/arm/pmu.txt
>> +++ b/Documentation/devicetree/bindings/arm/pmu.txt
>> @@ -25,6 +25,7 @@ Required properties:
>> "qcom,scorpion-pmu"
>> "qcom,scorpion-mp-pmu"
>> "qcom,krait-pmu"
>> + "cavium,thunder-pmu"
>> - interrupts : 1 combined interrupt or 1 per core. If the interrupt is a per-cpu
>> interrupt (PPI) then 1 interrupt should be specified.
>>
>> diff --git a/arch/arm64/boot/dts/cavium/thunder-88xx.dtsi b/arch/arm64/boot/dts/cavium/thunder-88xx.dtsi
>> index 9cb7cf9..2eb9b22 100644
>> --- a/arch/arm64/boot/dts/cavium/thunder-88xx.dtsi
>> +++ b/arch/arm64/boot/dts/cavium/thunder-88xx.dtsi
>> @@ -360,6 +360,11 @@
>> <1 10 0xff01>;
>> };
>>
>> + pmu {
>> + compatible = "cavium,thunder-pmu", "arm,armv8-pmuv3";
>> + interrupts = <1 7 4>;
>> + };
>> +
>> soc {
>> compatible = "simple-bus";
>> #address-cells = <2>;
>> --
>> 1.9.1
>>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
WARNING: multiple messages have this Message-ID (diff)
From: David Daney <ddaney@caviumnetworks.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Jan Glauber <jglauber@cavium.com>,
Mark Rutland <mark.rutland@arm.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 3/5] arm64: dts: Add Cavium ThunderX specific PMU
Date: Thu, 18 Feb 2016 10:37:45 -0800 [thread overview]
Message-ID: <56C60F79.5060908@caviumnetworks.com> (raw)
In-Reply-To: <20160218173248.GD16883@arm.com>
On 02/18/2016 09:32 AM, Will Deacon wrote:
> On Thu, Feb 18, 2016 at 05:50:12PM +0100, Jan Glauber wrote:
>> Add a compatible string for the Cavium ThunderX PMU.
>
> Stupid question, but is "thunder" the name of the CPU or the SoC or ...?
At a high level Cavium ThunderX (tm) is a family of SoCs. Since the SoC
contains many different functional blocks ...
>
> Whatever we use to describe the PMU, should probably also identify the
> CPU uniquely.
... In the context of this patch, "cavium,thunder-pmu" refers to the PMU
of Cavium's implementation of the ARMv8 Processing Element (PE)
specification (i.e. the CPU), as found on the CN88XX family of SoCs.
If we think of this in terms of MIDR_EL1, That would be:
Implementer: 0x43
PartNum: 0xA1
>
> Will
>
>> Signed-off-by: Jan Glauber <jglauber@cavium.com>
>> ---
>> Documentation/devicetree/bindings/arm/pmu.txt | 1 +
>> arch/arm64/boot/dts/cavium/thunder-88xx.dtsi | 5 +++++
>> 2 files changed, 6 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/pmu.txt b/Documentation/devicetree/bindings/arm/pmu.txt
>> index 5651883..d3999a1 100644
>> --- a/Documentation/devicetree/bindings/arm/pmu.txt
>> +++ b/Documentation/devicetree/bindings/arm/pmu.txt
>> @@ -25,6 +25,7 @@ Required properties:
>> "qcom,scorpion-pmu"
>> "qcom,scorpion-mp-pmu"
>> "qcom,krait-pmu"
>> + "cavium,thunder-pmu"
>> - interrupts : 1 combined interrupt or 1 per core. If the interrupt is a per-cpu
>> interrupt (PPI) then 1 interrupt should be specified.
>>
>> diff --git a/arch/arm64/boot/dts/cavium/thunder-88xx.dtsi b/arch/arm64/boot/dts/cavium/thunder-88xx.dtsi
>> index 9cb7cf9..2eb9b22 100644
>> --- a/arch/arm64/boot/dts/cavium/thunder-88xx.dtsi
>> +++ b/arch/arm64/boot/dts/cavium/thunder-88xx.dtsi
>> @@ -360,6 +360,11 @@
>> <1 10 0xff01>;
>> };
>>
>> + pmu {
>> + compatible = "cavium,thunder-pmu", "arm,armv8-pmuv3";
>> + interrupts = <1 7 4>;
>> + };
>> +
>> soc {
>> compatible = "simple-bus";
>> #address-cells = <2>;
>> --
>> 1.9.1
>>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2016-02-18 18:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 16:50 [PATCH v4 0/5] Cavium ThunderX PMU support Jan Glauber
2016-02-18 16:50 ` Jan Glauber
2016-02-18 16:50 ` [PATCH v4 1/5] arm64/perf: Rename Cortex A57 events Jan Glauber
2016-02-18 16:50 ` Jan Glauber
2016-02-18 16:50 ` [PATCH v4 2/5] arm64/perf: Add Cavium ThunderX PMU support Jan Glauber
2016-02-18 16:50 ` Jan Glauber
2016-02-18 16:50 ` [PATCH v4 3/5] arm64: dts: Add Cavium ThunderX specific PMU Jan Glauber
2016-02-18 16:50 ` Jan Glauber
2016-02-18 17:32 ` Will Deacon
2016-02-18 17:32 ` Will Deacon
2016-02-18 18:37 ` David Daney [this message]
2016-02-18 18:37 ` David Daney
2016-02-22 12:40 ` Jan Glauber
2016-02-22 12:40 ` Jan Glauber
2016-02-18 16:50 ` [PATCH v4 4/5] arm64/perf: Enable PMCR long cycle counter bit Jan Glauber
2016-02-18 16:50 ` Jan Glauber
2016-02-18 17:34 ` Will Deacon
2016-02-18 17:34 ` Will Deacon
2016-02-18 18:28 ` Jan Glauber
2016-02-18 18:28 ` Jan Glauber
2016-02-18 18:57 ` David Daney
2016-02-18 18:57 ` David Daney
2016-02-22 12:45 ` Jan Glauber
2016-02-22 12:45 ` Jan Glauber
2016-02-22 13:41 ` Will Deacon
2016-02-22 13:41 ` Will Deacon
2016-02-29 15:39 ` Will Deacon
2016-02-29 15:39 ` Will Deacon
2016-03-01 7:21 ` Jan Glauber
2016-03-01 7:21 ` Jan Glauber
2016-03-01 15:10 ` Jan Glauber
2016-03-01 15:10 ` Jan Glauber
2016-02-18 16:50 ` [PATCH v4 5/5] arm64/perf: Extend event mask for ARMv8.1 Jan Glauber
2016-02-18 16:50 ` Jan Glauber
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=56C60F79.5060908@caviumnetworks.com \
--to=ddaney@caviumnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.