| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <c533371d-efcd-59dc-0172-3f5775221302@kernel.org>
Date: Mon, 19 Aug 2019 13:07:00 +0100
From: Marc Zyngier <maz@...nel.org>
To: Mars Cheng <mars.cheng@...iatek.com>
Cc: Matthias Brugger <matthias.bgg@...il.com>,
Rob Herring <robh@...nel.org>, Stephen Boyd <sboyd@...nel.org>,
Sean Wang <sean.wang@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
devicetree@...r.kernel.org, CC Hwang <cc.hwang@...iatek.com>,
wsd_upstream@...iatek.com, Loda Chou <loda.chou@...iatek.com>,
linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
mtk01761 <wendell.lin@...iatek.com>, linux-clk@...r.kernel.org
Subject: Re: [PATCH v2 11/11] arm64: dts: add dts nodes for MT6779
Hi Mars,
On 19/08/2019 12:42, Mars Cheng wrote:
> Hi Marc
>
> On Mon, 2019-08-19 at 10:40 +0100, Marc Zyngier wrote:
>> On 19/08/2019 10:21, Mars Cheng wrote:
>>> this adds initial MT6779 dts settings fo board support,
>>> including cpu, gic, timer, ccf, pinctrl, uart...etc.
>>>
>>> Signed-off-by: Mars Cheng <mars.cheng@...iatek.com>
>>> ---
>>> arch/arm64/boot/dts/mediatek/Makefile | 1 +
>>> arch/arm64/boot/dts/mediatek/mt6779-evb.dtsi | 31 ++++
>>> arch/arm64/boot/dts/mediatek/mt6779.dts | 229 ++++++++++++++++++++++++++
>>> 3 files changed, 261 insertions(+)
>>> create mode 100644 arch/arm64/boot/dts/mediatek/mt6779-evb.dtsi
>>> create mode 100644 arch/arm64/boot/dts/mediatek/mt6779.dts
>>>
>>> diff --git a/arch/arm64/boot/dts/mediatek/Makefile b/arch/arm64/boot/dts/mediatek/Makefile
>>> index 458bbc4..53f1c61 100644
>>> --- a/arch/arm64/boot/dts/mediatek/Makefile
>>> +++ b/arch/arm64/boot/dts/mediatek/Makefile
>>> @@ -1,6 +1,7 @@
>>> # SPDX-License-Identifier: GPL-2.0
>>> dtb-$(CONFIG_ARCH_MEDIATEK) += mt2712-evb.dtb
>>> dtb-$(CONFIG_ARCH_MEDIATEK) += mt6755-evb.dtb
>>> +dtb-$(CONFIG_ARCH_MEDIATEK) += mt6779-evb.dtb
>>> dtb-$(CONFIG_ARCH_MEDIATEK) += mt6795-evb.dtb
>>> dtb-$(CONFIG_ARCH_MEDIATEK) += mt6797-evb.dtb
>>> dtb-$(CONFIG_ARCH_MEDIATEK) += mt6797-x20-dev.dtb
>>> diff --git a/arch/arm64/boot/dts/mediatek/mt6779-evb.dtsi b/arch/arm64/boot/dts/mediatek/mt6779-evb.dtsi
>>> new file mode 100644
>>> index 0000000..164f5cb
>>> --- /dev/null
>>> +++ b/arch/arm64/boot/dts/mediatek/mt6779-evb.dtsi
>>> @@ -0,0 +1,31 @@
>>> +// SPDX-License-Identifier: GPL-2.0+
>>> +/*
>>> + * Copyright (c) 2019 MediaTek Inc.
>>> + * Author: Mars.C <mars.cheng@...iatek.com>
>>> + *
>>> + */
>>> +
>>> +/dts-v1/;
>>> +#include "mt6779.dtsi"
>>> +
>>> +/ {
>>> + model = "MediaTek MT6779 EVB";
>>> + compatible = "mediatek,mt6779-evb", "mediatek,mt6779";
>>> +
>>> + aliases {
>>> + serial0 = &uart0;
>>> + };
>>> +
>>> + memory@...00000 {
>>> + device_type = "memory";
>>> + reg = <0 0x40000000 0 0x1e800000>;
>>> + };
>>> +
>>> + chosen {
>>> + stdout-path = "serial0:921600n8";
>>> + };
>>> +};
>>> +
>>> +&uart0 {
>>> + status = "okay";
>>> +};
>>> diff --git a/arch/arm64/boot/dts/mediatek/mt6779.dts b/arch/arm64/boot/dts/mediatek/mt6779.dts
>>> new file mode 100644
>>> index 0000000..daa25b7
>>> --- /dev/null
>>> +++ b/arch/arm64/boot/dts/mediatek/mt6779.dts
>>> @@ -0,0 +1,229 @@
>>> +// SPDX-License-Identifier: GPL-2.0+
>>> +/*
>>> + * Copyright (c) 2019 MediaTek Inc.
>>> + * Author: Mars.C <mars.cheng@...iatek.com>
>>> + *
>>> + */
>>> +
>>> +#include <dt-bindings/clock/mt6779-clk.h>
>>> +#include <dt-bindings/interrupt-controller/irq.h>
>>> +#include <dt-bindings/interrupt-controller/arm-gic.h>
>>> +
>>> +/ {
>>> + compatible = "mediatek,mt6779";
>>> + interrupt-parent = <&sysirq>;
>>> + #address-cells = <2>;
>>> + #size-cells = <2>;
>>> +
>>> + psci {
>>> + compatible = "arm,psci-0.2";
>>> + method = "smc";
>>> + };
>>> +
>>> + cpus {
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> +
>>> + cpu0: cpu@0 {
>>> + device_type = "cpu";
>>> + compatible = "arm,cortex-a55";
>>> + enable-method = "psci";
>>> + reg = <0x000>;
>>> + };
>>> +
>>> + cpu1: cpu@1 {
>>> + device_type = "cpu";
>>> + compatible = "arm,cortex-a55";
>>> + enable-method = "psci";
>>> + reg = <0x100>;
>>> + };
>>> +
>>> + cpu2: cpu@2 {
>>> + device_type = "cpu";
>>> + compatible = "arm,cortex-a55";
>>> + enable-method = "psci";
>>> + reg = <0x200>;
>>> + };
>>> +
>>> + cpu3: cpu@3 {
>>> + device_type = "cpu";
>>> + compatible = "arm,cortex-a55";
>>> + enable-method = "psci";
>>> + reg = <0x300>;
>>> + };
>>> +
>>> + cpu4: cpu@4 {
>>> + device_type = "cpu";
>>> + compatible = "arm,cortex-a55";
>>> + enable-method = "psci";
>>> + reg = <0x400>;
>>> + };
>>> +
>>> + cpu5: cpu@5 {
>>> + device_type = "cpu";
>>> + compatible = "arm,cortex-a55";
>>> + enable-method = "psci";
>>> + reg = <0x500>;
>>> + };
>>> +
>>> + cpu6: cpu@6 {
>>> + device_type = "cpu";
>>> + compatible = "arm,cortex-a75";
>>> + enable-method = "psci";
>>> + reg = <0x600>;
>>> + };
>>> +
>>> + cpu7: cpu@7 {
>>> + device_type = "cpu";
>>> + compatible = "arm,cortex-a75";
>>> + enable-method = "psci";
>>> + reg = <0x700>;
>>> + };
>>> + };
>>> +
>>> + clk26m: oscillator@0 {
>>> + compatible = "fixed-clock";
>>> + #clock-cells = <0>;
>>> + clock-frequency = <26000000>;
>>> + clock-output-names = "clk26m";
>>> + };
>>> +
>>> + clk32k: oscillator@1 {
>>> + compatible = "fixed-clock";
>>> + #clock-cells = <0>;
>>> + clock-frequency = <32768>;
>>> + clock-output-names = "clk32k";
>>> + };
>>> +
>>> + uart_clk: dummy26m {
>>> + compatible = "fixed-clock";
>>> + clock-frequency = <26000000>;
>>> + #clock-cells = <0>;
>>> + };
>>> +
>>> + timer {
>>> + compatible = "arm,armv8-timer";
>>> + interrupt-parent = <&gic>;
>>> + interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_LOW>,
>>> + <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW>,
>>> + <GIC_PPI 11 IRQ_TYPE_LEVEL_LOW>,
>>> + <GIC_PPI 10 IRQ_TYPE_LEVEL_LOW>;
>>> + };
>>> +
>>> + soc {
>>> + #address-cells = <2>;
>>> + #size-cells = <2>;
>>> + compatible = "simple-bus";
>>> + ranges;
>>> +
>>> + gic: interrupt-controller@...00000 {
>>> + compatible = "arm,gic-v3";
>>> + #interrupt-cells = <3>;
>>
>> You also haven't described the CPU PMUs. Depending on how they are wired
>> (SPIs or PPIs), you may have to change the interrupt-cells property to
>> include a cell for the PPI partitioning.
>>
>
> pmu nodes would be:
>
> pmu {
> compatible = "arm,armv8-pmuv3";
> interrupt-parent = <&gic>;
> interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_LOW>;
> };
>
> dsu-pmu-0 {
> compatible = "arm,dsu-pmu";
> interrupts = <GIC_SPI 18 IRQ_TYPE_LEVEL_HIGH>;
> cpus = <&cpu0>, <&cpu1>, <&cpu2>, <&cpu3>,
> <&cpu4>, <&cpu5>, <&cpu6>, <&cpu7>;
> };
>
> so I think interrupt-cells could be <3>, will add pmu nodes in v3.
No, that's wrong, at least for the CPU pmu node.
First, you need two of them (one for the A55s, one for the A75s).
Then you need to partition the corresponding PPI so that they can be
described as separate affinity sets.
Finally, this implies that #interrupt-cells goes up to 4, and all the
interrupts directly routed to the GIC must be updated.
You should have something like this:
&gic {
ppi-partitions {
cluster0: interrupt-partition-0 {
affinity = <&cpu0 &cpu1 &cpu2
&cpu3 &cpu4 &cpu5>;
};
cluster1: interrupt-partition-1 {
affinity = <&cpu6 &cpu7>;
};
};
pmu_a55 {
compatible = "arm,cortex-a55-pmu", "arm,armv8-pmuv3";
interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_LOW &cluster0>;
};
pmu_a75 {
compatible = "arm,cortex-a75-pmu", "arm,armv8-pmuv3";
interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_LOW &cluster1>;
};
Please see the rk3399 usage of the binding, as it is the canonical example.
>
>>
>>> + #address-cells = <2>;
>>> + #size-cells = <2>;
>>> + #redistributor-regions = <1>;
>>
>> This is the default, so this can be omitted.
>>
>
> Got it, will remove it in v3.
>
>>> + interrupt-parent = <&gic>;
>>> + interrupt-controller;
>>> + reg = <0 0x0c000000 0 0x40000>, /* GICD */
>>> + <0 0x0c040000 0 0x200000>, /* GICR */
>>> + <0 0x0c400000 0 0x2000>, /* GICC */
>>> + <0 0x0c410000 0 0x1000>, /* GICH */
>>> + <0 0x0c420000 0 0x2000>; /* GICV */
>>
>> Where do the last 3 ranges come from? Neither Cortex-A55 nor A75 have
>> the memory-mapped CPU interface. It looks like a copy/paste from another
>> SoC...
>>
>
> My bad, should remove the last 3 interfaces. will do in v3.
>
>>> + interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH>;
>>> + };
>>
>> And no ITS?
>>
>
> No, we don't have ITS support in HW.
That's pretty sad.
M.
--
Jazz is not dead, it just smells funny...
Powered by blists - more mailing lists