linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
	"gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
	"sebastian.hesselbarth@gmail.com"
	<sebastian.hesselbarth@gmail.com>,
	"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 v2 7/8] arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board
Date: Tue, 15 Mar 2022 15:28:50 +0100	[thread overview]
Message-ID: <YjCiot+PSv3ZRS4J@lunn.ch> (raw)
In-Reply-To: <7b78853e-71ec-7c57-4cac-5cd6303f3b13@alliedtelesis.co.nz>

On Tue, Mar 15, 2022 at 02:11:56AM +0000, Chris Packham wrote:
> 
> On 15/03/22 13:24, Andrew Lunn wrote:
> >> diff --git a/arch/arm64/boot/dts/marvell/armada-98dx2530.dtsi b/arch/arm64/boot/dts/marvell/armada-98dx2530.dtsi
> >> new file mode 100644
> >> index 000000000000..ebe464b9ebd2
> >> --- /dev/null
> >> +++ b/arch/arm64/boot/dts/marvell/armada-98dx2530.dtsi
> >> @@ -0,0 +1,343 @@
> >> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> >> +/*
> >> + * Device Tree For AC5.
> >> + *
> >> + * Copyright (C) 2021 Marvell
> >> + *
> >> + */
> >> +
> >> +/dts-v1/;
> >> +	memory@0 {
> >> +		device_type = "memory";
> >> +		reg = <0x2 0x00000000 0x0 0x40000000>;
> >> +		// linux,usable-memory = <0x2 0x00000000 0x0 0x80000000>;
> >> +	};
> > Is the memory part of the SoC, or is it on the board? Normally it is
> > on the board, so should be in the .dts file. But Apple M1 etc...

> I also wasn't sure about linux,usable-memory. It's commented out so it's 
> obviously doing nothing but should it? No other in-tree dts files have it.

Hi Chris

I've no idea what it means. Maybe search the SDK and see if they have
some code and what it does. But i would drop it.

     Andrew

  reply	other threads:[~2022-03-15 14:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 21:31 [PATCH v2 0/8] arm64: mvebu: Support for Marvell 98DX2530 (and variants) Chris Packham
2022-03-14 21:31 ` [PATCH v2 1/8] dt-bindings: pinctrl: mvebu: Document bindings for AC5 Chris Packham
2022-03-15  0:07   ` Andrew Lunn
2022-03-15  0:22     ` Chris Packham
2022-03-15  0:27       ` Andrew Lunn
2022-03-23 18:34         ` Rob Herring
2022-03-15 10:46   ` Krzysztof Kozlowski
2022-03-15 21:12     ` Chris Packham
2022-03-16  8:16       ` Krzysztof Kozlowski
2022-03-16 20:21         ` Chris Packham
2022-03-17  7:26           ` Krzysztof Kozlowski
2022-03-17 14:14             ` Andrew Lunn
2022-03-17 15:16               ` Krzysztof Kozlowski
2022-03-14 21:31 ` [PATCH v2 2/8] dt-bindings: net: mvneta: Add marvell,armada-ac5-neta Chris Packham
2022-03-15  0:10   ` Andrew Lunn
2022-03-14 21:31 ` [PATCH v2 3/8] dt-bindings: mmc: xenon: add AC5 compatible string Chris Packham
2022-03-15  0:14   ` Andrew Lunn
2022-03-14 21:31 ` [PATCH v2 4/8] pinctrl: mvebu: pinctrl driver for 98DX2530 SoC Chris Packham
2022-03-15  0:16   ` Andrew Lunn
2022-03-15 10:49   ` Krzysztof Kozlowski
2022-03-15 14:33     ` Andrew Lunn
2022-03-15 14:39       ` Krzysztof Kozlowski
2022-03-14 21:31 ` [PATCH v2 5/8] net: mvneta: Add support for 98DX2530 Ethernet port Chris Packham
2022-03-15  0:12   ` Andrew Lunn
2022-03-15  0:27     ` Chris Packham
2022-03-14 21:31 ` [PATCH v2 6/8] mmc: xenon: add AC5 compatible string Chris Packham
2022-03-15  0:14   ` Andrew Lunn
2022-03-14 21:31 ` [PATCH v2 7/8] arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board Chris Packham
2022-03-15  0:24   ` Andrew Lunn
2022-03-15  2:11     ` Chris Packham
2022-03-15 14:28       ` Andrew Lunn [this message]
2022-03-16 11:49   ` Marc Zyngier
2022-03-14 21:31 ` [PATCH v2 8/8] arm64: marvell: enable the 98DX2530 pinctrl driver Chris Packham
2022-03-15  0:25   ` Andrew Lunn

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=YjCiot+PSv3ZRS4J@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.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 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).