From: Andrew Lunn <andrew@lunn.ch>
To: "Marek Behún" <marek.behun@nic.cz>
Cc: arm@kernel.org, Gregory CLEMENT <gregory.clement@bootlin.com>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 mvebu-dt64 3/3] arm64: dts: marvell: add DTS for Turris Mox
Date: Thu, 29 Aug 2019 03:09:08 +0200 [thread overview]
Message-ID: <20190829010908.GC32178@lunn.ch> (raw)
In-Reply-To: <20190828151243.23542-4-marek.behun@nic.cz>
On Wed, Aug 28, 2019 at 05:12:43PM +0200, Marek Beh�n wrote:
> This adds support for the Turris Mox board from CZ.NIC.
>
> Turris Mox is as modular router based on the Armada 3720 SOC (same as
> EspressoBin).
>
> The basic board can be extended by different modules.
> If those are connected, U-Boot lets the kernel know via device-tree.
>
> Since modules can be connected in different order and some modules can
> be connected multiple times (up to three modules containing 8-port
> ethernet switch in DSA configuration can be connected) we decided
> against using device-tree overlays, because it got complicated rather
> quickly. (For example the SFP module can be connected directly to the
> CPU, or after a switch module. There are four cases and all would need
> different SFP overlay. There are two types of switch modules (8-port
> with pass-through and 4-port with no pass-through). For those we would
> again need at least 6 more overlays.)
>
> We therefore decided to put all the possibly connected devices in one
> device-tree and disable them by default. When U-Boot finds out which
> modules are connected, it fixes the loaded device-tree accordingly just
> before boot. By Rob Herring's suggestion we also made it so that U-Boot
> completely removes nodes which are disabled after this fixup.
>
> Signed-off-by: Marek Beh�n <marek.behun@nic.cz>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Gregory CLEMENT <gregory.clement@bootlin.com>
> Cc: Andrew Lunn <andrew@lunn.ch>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2019-08-29 1:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 15:12 [PATCH v2 mvebu-dt64 0/3] Add Turris Mox device-tree Marek Behún
2019-08-28 15:12 ` [PATCH v2 mvebu-dt64 1/3] arm64: dts: marvell: armada-37xx: add SPI CS1 pinctrl Marek Behún
2019-08-28 15:12 ` [PATCH v2 mvebu-dt64 2/3] dt-bindings: marvell: document Turris Mox compatible Marek Behún
2019-08-28 15:12 ` [PATCH v2 mvebu-dt64 3/3] arm64: dts: marvell: add DTS for Turris Mox Marek Behún
2019-08-29 1:09 ` Andrew Lunn [this message]
2019-08-30 20:20 ` [PATCH v2 mvebu-dt64 0/3] Add Turris Mox device-tree Gregory CLEMENT
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=20190829010908.GC32178@lunn.ch \
--to=andrew@lunn.ch \
--cc=arm@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=marek.behun@nic.cz \
--cc=robh@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).