From: Caesar Wang <wxt@rock-chips.com>
To: Mark Rutland <mark.rutland@arm.com>, marc.zyngier@arm.com
Cc: Caesar Wang <wxt@rock-chips.com>,
huangtao@rock-chips.com, devicetree@vger.kernel.org,
Heiko Stuebner <heiko@sntech.de>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Brian Norris <briannorris@chromium.org>,
Will Deacon <will.deacon@arm.com>,
dianders@chromium.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
David Wu <david.wu@rock-chips.com>,
cf@rock-chips.com, briannorris@google.com, jay.xu@rock-chips.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: support the pmu node for rk3399
Date: Wed, 06 Jul 2016 10:55:51 +0800 [thread overview]
Message-ID: <577C7337.7060803@rock-chips.com> (raw)
In-Reply-To: <20160701102612.GB22953@leverpostej>
[-- Attachment #1: Type: text/plain, Size: 3287 bytes --]
Hi Mark,
On 2016?07?01? 18:26, Mark Rutland wrote:
> On Fri, Jul 01, 2016 at 03:36:10PM +0800, Caesar Wang wrote:
>> As the Marc posted the patches [0] to support Partitioning per-cpu
>> interrupts. Let's add this patch to match it on rk3399 SoCs.
>>
>> [0]:
>> https://lkml.org/lkml/2016/4/11/182
> The core IRQ support is merged, but it's worth noting that the perf code
> doesn't use it yet. So we still need a patch adding support to the perf
> code before we can change the dts.
>
> I think Marc had a prototype of that somewhere.
>
> Marc?
>
>> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
>> Cc: Heiko Stuebner <heiko@sntech.de>
>> Cc: Will Deacon <will.deacon@arm.com>
>> Cc: Marc Zyngier <marc.zyngier@arm.com>
>> CC: linux-arm-kernel@lists.infradead.org
>>
>> ---
>>
>> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 26 ++++++++++++++++++++++++++
>> 1 file changed, 26 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> index 8f0a069..b260f62 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> @@ -165,6 +165,22 @@
>> <GIC_PPI 10 IRQ_TYPE_LEVEL_LOW 0>;
>> };
>>
>> + pmu_a53 {
>> + compatible = "arm,cortex-a53-pmu";
>> + interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_LOW &part0>;
>> + interrupt-affinity = <&cpu_l0>,
>> + <&cpu_l1>,
>> + <&cpu_l2>,
>> + <&cpu_l3>;
>> + };
> I'm not keen on having to redundantly describe the affinity in
> interrupt-affinity and the partition's affinity property. Those will
> almost certainly be out-of-sync in some DTs, and it'll be very painful
> to deal with.
>
> I think that for partitioned PPIs the PMU driver should use the affinity
> from the PPI, and not have an interrupt-affinity property. Hopefully
> that's relatively simple to handle.
So you are keen have the simple to handle the pmu.
e.g.:
+ pmu_a53 {
+ compatible = "arm,cortex-a53-pmu";
+ interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_LOW &part0>;
+ };
+
+ pmu_a72 {
+ compatible = "arm,cortex-a72-pmu";
+ interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_LOW &part1>;
+ };
Right?
---
BTW:
Do I need continue to send it for upstream or you guys will change it
for all platform?
Thanks
-
Caesar
>
> Thanks,
> Mark.
>
>> +
>> + pmu_a72 {
>> + compatible = "arm,cortex-a72-pmu";
>> + interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_LOW &part1>;
>> + interrupt-affinity = <&cpu_b0>,
>> + <&cpu_b1>;
>> + };
>> +
>> xin24m: xin24m {
>> compatible = "fixed-clock";
>> clock-frequency = <24000000>;
>> @@ -296,6 +312,16 @@
>> msi-controller;
>> reg = <0x0 0xfee20000 0x0 0x20000>;
>> };
>> +
>> + ppi-partitions {
>> + part0: interrupt-partition-0 {
>> + affinity = <&cpu_l0 &cpu_l1 &cpu_l2 &cpu_l3>;
>> + };
>> +
>> + part1: interrupt-partition-1 {
>> + affinity = <&cpu_b0 &cpu_b1>;
>> + };
>> + };
>> };
>>
>> i2c1: i2c@ff110000 {
>> --
>> 1.9.1
>>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
--
caesar wang | software engineer | wxt@rock-chip.com
[-- Attachment #2: Type: text/html, Size: 5504 bytes --]
prev parent reply other threads:[~2016-07-06 2:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 7:36 [PATCH 0/2] arm64: dts: rockchip: Support PMU for rk3399 SoCs Caesar Wang
2016-07-01 7:36 ` Caesar Wang
2016-07-01 7:36 ` Caesar Wang
2016-07-01 7:36 ` [PATCH 1/2] arm64: dts: rockchip: change all interrupts cells for 4 on " Caesar Wang
2016-07-01 7:36 ` Caesar Wang
2016-07-01 7:36 ` [PATCH 2/2] arm64: dts: rockchip: support the pmu node for rk3399 Caesar Wang
2016-07-01 7:36 ` Caesar Wang
2016-07-01 10:26 ` Mark Rutland
2016-07-01 10:26 ` Mark Rutland
2016-07-01 12:50 ` Marc Zyngier
2016-07-01 12:50 ` Marc Zyngier
2016-07-01 12:50 ` Marc Zyngier
2016-07-06 2:55 ` Caesar Wang [this message]
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=577C7337.7060803@rock-chips.com \
--to=wxt@rock-chips.com \
--cc=briannorris@chromium.org \
--cc=briannorris@google.com \
--cc=catalin.marinas@arm.com \
--cc=cf@rock-chips.com \
--cc=david.wu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
--cc=yamada.masahiro@socionext.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 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.