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 4/6] arm64: Add DTS support for FSL's LS2085A SoC
Date: Fri, 15 Aug 2014 17:12:46 +0100	[thread overview]
Message-ID: <20140815161246.GB21908@leverpostej> (raw)
In-Reply-To: <3b8cefe8260e444da5174d1b0d60b073@BY2PR0301MB0743.namprd03.prod.outlook.com>

Hi Stuart,

On Fri, Aug 15, 2014 at 04:37:06PM +0100, Stuart Yoder wrote:
> > > +/ {
> > > +	compatible = "fsl,ls2085a";
> > > +	interrupt-parent = <&gic>;
> > > +	#address-cells = <2>;
> > > +	#size-cells = <2>;
> > > +
> > > +	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>;
> > > +			enable-method = "spin-table";
> > > +			cpu-release-addr = <0x0 0x8000fff8>;
> > > +		};
> > 
> > I would strongly recommend having a unique cpu-release-addr for each
> > CPU.
> 
> We could do that, but we were just following existing practice in
> existing arch/arm64 device trees.  The 3 existing platforms upstream
> right now all have have the same cpu-release-addr value:
>    apm-storm.dtsi
>    foundation-v8.dts
>    rtsm_ve-aemv8a.dts

In general, following existing examples is a good idea. I'm not faulting
you for that.

Unfortunately there are plenty of bad examples in DTS in the kernel.

W.R.T. unique addresses for spin-table this is something we learnt after
those dts files were upstreamed. It's not possible to change those dts
files in the kernel without breaking older firmwares/bootwrappers which
don't patch the DTB.

Cheers,
Mark.

  reply	other threads:[~2014-08-15 16:12 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15  9:49 [PATCH 0/6] ARM64: Add support for FSL's LS2085A SoC Bhupesh Sharma
2014-08-15  9:49 ` [PATCH 1/6] Documentation: DT: Add bindings for FSL NS16550A UART Bhupesh Sharma
2014-08-15 10:46   ` Mark Rutland
2014-08-15 14:42     ` [PATCH 1/6] Documentation: DT: Add bindings for FSL NS16550A The UART bhupesh.sharma at freescale.com
2014-08-15 15:03       ` Mark Rutland
2014-08-20  9:08         ` bhupesh.sharma at freescale.com
2014-08-20 11:31           ` Mark Rutland
2014-08-20 12:20             ` bhupesh.sharma at freescale.com
2014-08-15  9:49 ` [PATCH 2/6] Documentation: DT: Add entry for FSL LS2085A SoC and Simulator model Bhupesh Sharma
2014-08-15  9:49 ` [PATCH 3/6] Documentation: DT: Add entry for FSL Management Complex Bhupesh Sharma
2014-08-15 11:00   ` Mark Rutland
2014-08-15 13:12     ` Stuart Yoder
2014-08-15 13:35     ` Kumar Gala
2014-08-15  9:49 ` [PATCH 4/6] arm64: Add DTS support for FSL's LS2085A SoC Bhupesh Sharma
2014-08-15 10:12   ` Catalin Marinas
2014-08-15 12:53     ` Stuart Yoder
2014-08-15 13:10       ` Catalin Marinas
2014-08-15 14:31         ` bhupesh.sharma at freescale.com
2014-08-15 15:28           ` Catalin Marinas
2014-08-15 15:57             ` Stuart Yoder
2014-08-15 16:22               ` Mark Rutland
2014-08-15 16:25               ` Catalin Marinas
2014-08-15 16:44                 ` Stuart Yoder
2014-08-15 10:23   ` Mark Rutland
2014-08-15 15:21     ` arnab.basu at freescale.com
2014-08-15 15:26       ` Kumar Gala
2014-08-15 15:41         ` Stuart Yoder
2014-08-15 15:43           ` Kumar Gala
2014-08-15 15:49             ` Stuart Yoder
2014-08-15 16:02               ` Catalin Marinas
2014-08-15 15:37     ` Stuart Yoder
2014-08-15 16:12       ` Mark Rutland [this message]
2014-08-15 12:13   ` Marc Zyngier
2014-08-15 13:29   ` Kumar Gala
2014-08-15 14:26     ` bhupesh.sharma at freescale.com
2014-08-15 14:40       ` Kumar Gala
2014-08-15 16:19         ` Stuart Yoder
2014-08-15  9:49 ` [PATCH 5/6] arm64: dts/Makefile: Add support for FSL's LS2085A simulator model Bhupesh Sharma
2014-08-15  9:49 ` [PATCH 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=20140815161246.GB21908@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