public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 4/6] arm64: Add DTS support for FSL's LS2085A SoC
Date: Wed, 3 Sep 2014 18:53:40 +0100	[thread overview]
Message-ID: <20140903175340.GN3127@leverpostej> (raw)
In-Reply-To: <1409764991.21254.139.camel@smoke>

Hi Geoff,

On Wed, Sep 03, 2014 at 06:23:11PM +0100, Geoff Levand wrote:
> Hi Bhupesh,
> 
> On Thu, 2014-08-28 at 15:25 +0530, Bhupesh Sharma wrote:
> > This patch adds the device tree support for FSL LS2085A SoC
> > based on ARMv8 architecture.
> > +	cpus {
> > +		#address-cells = <2>;
> > +		#size-cells = <0>;
> > +
> > +		/* We have 4 clusters having 2 Cortex-A57 cores each */
> > +		cpu at 0 {
> > +			device_type = "cpu";
> > +			compatible = "arm,cortex-a57";
> > +			reg = <0x0 0x0>;
> > +		};
> 
> arm64 needs a cpu enable-method property.  Is your boot loader adding
> that?

That's the plan. If you take a look on the U-Boot mailing list you'll
see there are patches under review which do just that, along with the
basis of a PSCI 0.2 implementation.

Note that whether or not the in-kernel dts should have an enable-method
is under discussion in a subsequent (v3) posting [1,2] of this series.

> Be aware that if you have set it up this way, users will not be able to
> use this file with kexec's --dtb=FILE to specify a 2nd stage DT file.
> kexec will use a copy of the DT from the 1st stage in this case.

Surely the latter is the default and the former is the "trust me I know
what I'm doing" case?

In general there are other things you might need to fill in anyhow (like
dynamically populated memory), so I don't see that as a big isssue
(though admittedly painful if you're testing things in that area).

Mark.

[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/284076.html
[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/284106.html

  reply	other threads:[~2014-09-03 17:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28  9:55 [PATCH V2 0/6] ARM64: Add support for FSL's LS2085A SoC Bhupesh Sharma
2014-08-28  9:55 ` [PATCH V2 1/6] Documentation: DT: Add bindings for FSL NS16550A UART Bhupesh Sharma
2014-08-28  9:55 ` [PATCH V2 2/6] Documentation: DT: Add entry for FSL LS2085A SoC and Simulator model Bhupesh Sharma
2014-08-28  9:55 ` [PATCH V2 3/6] Documentation: DT: Add entry for FSL Management Complex Bhupesh Sharma
2014-08-28  9:55 ` [PATCH V2 4/6] arm64: Add DTS support for FSL's LS2085A SoC Bhupesh Sharma
2014-08-28 14:56   ` Mark Rutland
2014-08-29 15:51     ` bhupesh.sharma at freescale.com
2014-08-29 17:47       ` Mark Rutland
2014-08-29 18:07         ` bhupesh.sharma at freescale.com
2014-09-02 10:05           ` Catalin Marinas
2014-09-02 10:14             ` Catalin Marinas
2014-09-02 10:27               ` bhupesh.sharma at freescale.com
2014-09-02 10:19             ` Marc Zyngier
2014-09-03 17:23   ` Geoff Levand
2014-09-03 17:53     ` Mark Rutland [this message]
2014-09-03 18:17       ` Geoff Levand
2014-08-28  9:55 ` [PATCH V2 5/6] arm64: dts/Makefile: Add support for FSL's LS2085A simulator model Bhupesh Sharma
2014-08-28  9:55 ` [PATCH V2 6/6] arm64: Add support for FSL's LS2085A SoC in Kconfig and defconfig Bhupesh Sharma

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=20140903175340.GN3127@leverpostej \
    --to=mark.rutland@arm.com \
    --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