mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Mark Rutland <Mark.Rutland@arm.com>,
	device tree <devicetree@vger.kernel.org>,
	Pawel Moll <Pawel.Moll@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	Will Deacon <Will.Deacon@arm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Kumar Gala <galak@codeaurora.org>,
	LAKML <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/3] arm64: Add Juno SoC device tree.
Date: Fri, 31 Oct 2014 17:16:58 +0000	[thread overview]
Message-ID: <20141031171658.GK1069@e106497-lin.cambridge.arm.com> (raw)
In-Reply-To: <20141031162918.GG32139@lunn.ch>

On Fri, Oct 31, 2014 at 04:29:18PM +0000, Andrew Lunn wrote:
> 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

Hi Andrew,

> 
> 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.

Agree.

> 
> Is it likely another board will be designed using the same SoC?

There is at least one revision of the SoC happening, but hopefully
it should be compatible with the current DT. ARM usually creates
CoreTiles for the CPUs and uses the VExpress motherboard as the
"expansion board" sort of setup.

Juno is new in this area in that is an 'all-in-one' board. I don't
think we will ever see another board with the Juno chip because
ARM doesn't sell chips, but there might be future ARM boards that
will share features with Juno, so refactoring will be necessary.
Unfortunately, I don't have any insights into the future so I
cannot properly prepare for such case, hence the one file submission.

Best regards,
Liviu

> 
>    Andrew
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

-- 
====================
| I would like to |
| fix the world,  |
| but they're not |
| giving me the   |
 \ source code!  /
  ---------------
    ¯\_(ツ)_/¯


      reply	other threads:[~2014-10-31 17:17 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
2014-10-31 17:16     ` Liviu Dudau [this message]

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=20141031171658.GK1069@e106497-lin.cambridge.arm.com \
    --to=liviu.dudau@arm.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=Mark.Rutland@arm.com \
    --cc=Pawel.Moll@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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
all inboxes | Powered by JetHome®