From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] arm64: Add Juno SoC device tree.
Date: Fri, 31 Oct 2014 17:29:18 +0100 [thread overview]
Message-ID: <20141031162918.GG32139@lunn.ch> (raw)
In-Reply-To: <1414771460-7340-4-git-send-email-Liviu.Dudau@arm.com>
On Fri, Oct 31, 2014 at 04:04:20PM +0000, Liviu Dudau wrote:
> This adds support for USB, 100MB Ethernet port, timers, I2C,
> and watchdog timer. Missing for now are the SMMU nodes, HDLCD
> and PCIe.
Hi Liviu
I know nothing about Juno, but i do help maintain the Marvell SoC
device tree files.
It seems pretty normal to split device tree descriptions into a
generic .dtsi SoC part and a number of .dts board files, one per
board, and including the SoC .dtsi file.
Is it likely another board will be designed using the same SoC?
Andrew
next prev parent reply other threads:[~2014-10-31 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 16:04 [PATCH 0/3] arm64: Add support for Juno development board Liviu Dudau
2014-10-31 16:04 ` [PATCH 1/3] arm64: defconfig: Enable support for generic EHCI and OHCI platforms Liviu Dudau
2014-10-31 16:04 ` [PATCH 2/3] arm64: Create link to include/dt-bindings to enable C preprocessor use Liviu Dudau
2014-10-31 16:04 ` [PATCH 3/3] arm64: Add Juno SoC device tree Liviu Dudau
2014-10-31 16:29 ` Andrew Lunn [this message]
2014-10-31 17:16 ` Liviu Dudau
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=20141031162918.GG32139@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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).