linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: Marc Zyngier <maz@kernel.org>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org" 
	<krzysztof.kozlowski+dt@linaro.org>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"will@kernel.org" <will@kernel.org>,
	"andrew@lunn.ch" <andrew@lunn.ch>,
	"gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
	"sebastian.hesselbarth@gmail.com"
	<sebastian.hesselbarth@gmail.com>,
	"kostap@marvell.com" <kostap@marvell.com>,
	"robert.marko@sartura.hr" <robert.marko@sartura.hr>,
	"vadym.kochan@plvision.eu" <vadym.kochan@plvision.eu>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v7 2/3] arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board
Date: Fri, 13 May 2022 01:26:21 +0000	[thread overview]
Message-ID: <a69eaf73-8c3c-dfd7-16e5-70460c68877e@alliedtelesis.co.nz> (raw)
In-Reply-To: <5c01f20a-acd3-da15-081d-7cf878f8a77a@alliedtelesis.co.nz>

Hi Marc,

On 13/05/22 10:10, Chris Packham wrote:
> Hi Marc,
>
> On 12/05/22 19:38, Marc Zyngier wrote:
>> On Thu, 12 May 2022 05:25:00 +0100,
>> Chris Packham <chris.packham@alliedtelesis.co.nz> wrote:
>>> The 98DX2530 SoC is the Control and Management CPU integrated into
>>> the Marvell 98DX25xx and 98DX35xx series of switch chip (internally
>>> referred to as AlleyCat5 and AlleyCat5X).
>>>
>>> These files have been taken from the Marvell SDK and lightly cleaned
>>> up with the License and copyright retained.
>>>
>>> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
>>> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
>>> ---
>>>
>>> Notes:
>>>      The Marvell SDK has a number of new compatible strings. I've 
>>> brought
>>>      through some of the drivers or where possible used an in-tree
>>>      alternative (e.g. there is SDK code for a ac5-gpio but two 
>>> instances of
>>>      the existing marvell,orion-gpio seems to cover what is needed 
>>> if you use
>>>      an appropriate binding). I expect that there will a new series of
>>>      patches when I get some different hardware (or additions to 
>>> this series
>>>      depending on if/when it lands).
>>>           Changes in v7:
>>>      - Add missing compatible on usb1
>>>      - Add "rd-ac5x" compatible for board
>>>      - Move aliases to board dts
>>>      - Move board specific usb info to board dts
>>>      - Consolidate usb1 board settings and remove unnecessary 
>>> compatible
>>>      - Add Allied Telesis copyright
>>>      - Rename files after mailng-list discussion
>>>      Changes in v6:
>>>      - Move CPU nodes above the SoC (Krzysztof)
>>>      - Minor formatting clean ups (Krzysztof)
>>>      - Run through `make dtbs_check`
>>>      - Move gic nodes inside SoC
>>>      - Group clocks under a clock node
>>>      Changes in v5:
>>>      - add #{address,size}-cells property to i2c nodes
>>>      - make i2c nodes disabled in the SoC and enable them in the board
>>>      - add interrupt controller attributes to gpio nodes
>>>      - Move fixed-clock nodes up a level and remove unnecessary @0
>>>      Changes in v4:
>>>      - use 'phy-handle' instead of 'phy'
>>>      - move status="okay" on usb nodes to board dts
>>>      - Add review from Andrew
>>>      Changes in v3:
>>>      - Move memory node to board
>>>      - Use single digit reg value for phy address
>>>      - Remove MMC node (driver needs work)
>>>      - Remove syscon & simple-mfd for pinctrl
>>>      Changes in v2:
>>>      - Make pinctrl a child node of a syscon node
>>>      - Use marvell,armada-8k-gpio instead of orion-gpio
>>>      - Remove nand peripheral. The Marvell SDK does have some 
>>> changes for the
>>>        ac5-nand-controller but I currently lack hardware with NAND 
>>> fitted so
>>>        I can't test it right now. I've therefore chosen to omit the 
>>> node and
>>>        not attempted to bring in the driver or binding.
>>>      - Remove pcie peripheral. Again there are changes in the SDK 
>>> and I have
>>>        no way of testing them.
>>>      - Remove prestera node.
>>>      - Remove "marvell,ac5-ehci" compatible from USB node as
>>>        "marvell,orion-ehci" is sufficient
>>>      - Remove watchdog node. There is a buggy driver for the ac5 
>>> watchdog in
>>>        the SDK but it needs some work so I've dropped the node for now.
>>>
>>>   arch/arm64/boot/dts/marvell/Makefile          |   1 +
>>>   .../boot/dts/marvell/armada-98dx25xx.dtsi     | 295 
>>> ++++++++++++++++++
>>>   .../boot/dts/marvell/armada-98dx35xx-rd.dts   | 101 ++++++
>>>   .../boot/dts/marvell/armada-98dx35xx.dtsi     |  13 +
>>>   4 files changed, 410 insertions(+)
>>>   create mode 100644 arch/arm64/boot/dts/marvell/armada-98dx25xx.dtsi
>>>   create mode 100644 arch/arm64/boot/dts/marvell/armada-98dx35xx-rd.dts
>>>   create mode 100644 arch/arm64/boot/dts/marvell/armada-98dx35xx.dtsi
>>>
>>> diff --git a/arch/arm64/boot/dts/marvell/Makefile 
>>> b/arch/arm64/boot/dts/marvell/Makefile
>>> index 1c794cdcb8e6..b7a4c715afbb 100644
>>> --- a/arch/arm64/boot/dts/marvell/Makefile
>>> +++ b/arch/arm64/boot/dts/marvell/Makefile
>>> @@ -24,3 +24,4 @@ dtb-$(CONFIG_ARCH_MVEBU) += cn9132-db.dtb
>>>   dtb-$(CONFIG_ARCH_MVEBU) += cn9132-db-B.dtb
>>>   dtb-$(CONFIG_ARCH_MVEBU) += cn9130-crb-A.dtb
>>>   dtb-$(CONFIG_ARCH_MVEBU) += cn9130-crb-B.dtb
>>> +dtb-$(CONFIG_ARCH_MVEBU) += armada-98dx35xx-rd.dtb
>>> diff --git a/arch/arm64/boot/dts/marvell/armada-98dx25xx.dtsi 
>>> b/arch/arm64/boot/dts/marvell/armada-98dx25xx.dtsi
>>> new file mode 100644
>>> index 000000000000..55ab4cd843a9
>>> --- /dev/null
>>> +++ b/arch/arm64/boot/dts/marvell/armada-98dx25xx.dtsi
>>> @@ -0,0 +1,295 @@
>>> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
>>> +/*
>>> + * Device Tree For AC5.
>>> + *
>>> + * Copyright (C) 2021 Marvell
>>> + * Copyright (C) 2022 Allied Telesis Labs
>>> + */
>>> +
>>> +#include <dt-bindings/gpio/gpio.h>
>>> +#include <dt-bindings/interrupt-controller/arm-gic.h>
>>> +
>>> +/ {
>>> +    model = "Marvell AC5 SoC";
>>> +    compatible = "marvell,ac5";
>>> +    interrupt-parent = <&gic>;
>>> +    #address-cells = <2>;
>>> +    #size-cells = <2>;
>>> +
>>> +    cpus {
>>> +        #address-cells = <2>;
>>> +        #size-cells = <0>;
>>> +
>>> +        cpu-map {
>>> +            cluster0 {
>>> +                core0 {
>>> +                    cpu = <&cpu0>;
>>> +                };
>>> +                core1 {
>>> +                    cpu = <&cpu1>;
>>> +                };
>>> +            };
>>> +        };
>>> +
>>> +        cpu0: cpu@0 {
>>> +            device_type = "cpu";
>>> +            compatible = "arm,armv8";
>>> +            reg = <0x0 0x0>;
>>> +            enable-method = "psci";
>>> +            next-level-cache = <&l2>;
>>> +        };
>>> +
>>> +        cpu1: cpu@1 {
>>> +            device_type = "cpu";
>>> +            compatible = "arm,armv8";
>>> +            reg = <0x0 0x100>;
>>> +            enable-method = "psci";
>>> +            next-level-cache = <&l2>;
>>> +        };
>>> +
>>> +        l2: l2-cache {
>>> +            compatible = "cache";
>>> +        };
>>> +    };
>>> +
>>> +
>>> +    psci {
>>> +        compatible = "arm,psci-0.2";
>>> +        method = "smc";
>>> +    };
>>> +
>>> +    timer {
>>> +        compatible = "arm,armv8-timer";
>>> +        interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH>,
>>> +                 <GIC_PPI 8 IRQ_TYPE_LEVEL_HIGH>,
>>> +                 <GIC_PPI 10 IRQ_TYPE_LEVEL_HIGH>,
>>> +                 <GIC_PPI 7 IRQ_TYPE_LEVEL_HIGH>;
>>> +        clock-frequency = <25000000>;
>> I said no to this hack in a past version of this patch, and I'm going
>> to say it *again*.
> Sorry I must have missed it.
>> Please fix your firmware to program CNTFRQ_EL0, and
>> remove this useless property.
> I'm kind of at the mercy of what Marvell have provided for ATF. I am 
> working on the bootloader portion in parallel and am getting things 
> ready for submitting the u-boot support upstream. I was hoping to 
> leave ATF alone I can at least see if they haven't fixed this already 
> (the original dtsi I started with was fairly old) and if they haven't 
> I'll raise it via their support system.
Seems to work fine without the clock so I'll drop it.
>> You are also missing a PPI for the EL2 virtual timer which is present
>> on any ARMv8.1+ CPU (and since this system is using A55, it definitely
>> has it).
>>
>> [...]
> Will add.
I assume you're talking about the 5th PPI per the 
timer/arm,arch_timer.yaml ("hypervisor virtual timer irq"). Helpfully 
Marvell don't include the PPI interrupt numbers in their datasheet. But 
then I also notice that none of the other boards that have a 
"arm,armv8-timer" provide a 5th interrupt either, have I misunderstood 
something?
>>> +
>>> +        gic: interrupt-controller@80600000 {
>>> +            compatible = "arm,gic-v3";
>>> +            #interrupt-cells = <3>;
>>> +            interrupt-controller;
>>> +            /*#redistributor-regions = <1>;*/
>>> +            redistributor-stride = <0x0 0x20000>;    // 128kB stride
>> You don't need this at all. This is the architected value for GICv3.
> Will remove.
>>
>>> +            reg = <0x0 0x80600000 0x0 0x10000>, /* GICD */
>>> +                  <0x0 0x80660000 0x0 0x40000>; /* GICR */
>>> +            interrupts = <GIC_PPI 6 IRQ_TYPE_LEVEL_HIGH>;
>>> +        };
>>> +    };
>> Thanks,
>>
>>     M.
>>

  reply	other threads:[~2022-05-13  1:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12  4:24 [PATCH v7 0/3] arm64: mvebu: Support for Marvell 98DX2530 (and variants) Chris Packham
2022-05-12  4:24 ` [PATCH v7 1/3] dt-bindings: marvell: Document the AC5/AC5X compatibles Chris Packham
2022-05-13  9:12   ` Krzysztof Kozlowski
2022-05-12  4:25 ` [PATCH v7 2/3] arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board Chris Packham
2022-05-12  7:38   ` Marc Zyngier
2022-05-12 22:10     ` Chris Packham
2022-05-13  1:26       ` Chris Packham [this message]
2022-05-16  9:48         ` Marc Zyngier
2022-05-16 21:56           ` Chris Packham
2022-05-17  6:42             ` Marc Zyngier
2022-05-17 22:56               ` Chris Packham
2022-05-18  7:11                 ` Marc Zyngier
2022-05-12  4:25 ` [PATCH v7 3/3] arm64: marvell: enable the 98DX2530 pinctrl driver Chris Packham

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=a69eaf73-8c3c-dfd7-16e5-70460c68877e@alliedtelesis.co.nz \
    --to=chris.packham@alliedtelesis.co.nz \
    --cc=andrew@lunn.ch \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=kostap@marvell.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=robert.marko@sartura.hr \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=vadym.kochan@plvision.eu \
    --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).