devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Yang <leoli@freescale.com>
To: Stuart Yoder <stuart.yoder@freescale.com>
Cc: Rob Herring <robherring2@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Shaohui Xie <Shaohui.Xie@freescale.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Huan Wang <alison.wang@freescale.com>,
	Sharma Bhupesh <bhupesh.sharma@freescale.com>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	Singh Jaiprakash <jaiprakash.singh@freescale.com>,
	Will Deacon <will.deacon@arm.com>,
	"Lian M.H." <Minghuan.Lian@freescale.com>,
	Scott Wood <scottwood@freescale.com>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Liu Gang <Gang.Liu@freescale.com>,
	Olof Johansson <olof@lixom.net>,
	Badola Nikhil-B46172 <nikhil.badola@freescale.com>,
	Bhupesh SHARMA <bhupesh.linux@gmail.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Lu Y.B." <yangbo.lu@freescale.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 07/10] dts/ls2085a: Update DTSI to add support of various peripherals
Date: Thu, 1 Oct 2015 16:42:05 -0500	[thread overview]
Message-ID: <CADRPPNRz-yM_48HvHYv3r31u_b_tHkAjg5H5r+V2mE2=oJTGDA@mail.gmail.com> (raw)
In-Reply-To: <CY1PR0301MB0748A8F37E3FBE1922AF9D3F874C0@CY1PR0301MB0748.namprd03.prod.outlook.com>

On Thu, Oct 1, 2015 at 3:05 PM, Stuart Yoder <stuart.yoder@freescale.com> wrote:
> Hi Rob,
>
> Had a question about your comments on the patch below.
>
> You singled out 3 nodes (gic,uart,clockgen) and said "This should be under a bus node."
>
> What is special about those 3 nodes types?  There are a bunch of other memory
> mapped SoC devices as well in the DTS.
>
> I skimmed the dts files under arch/arm64 and it looks like most have a simple-bus
> SoC node like this where SoC devices are under:
>
>         soc {
>                 #address-cells = <2>;
>                 #size-cells = <2>;
>                 compatible = "simple-bus";
>                 ranges;
>
> Is that what you are looking for-- for all SoC devices?

I think the key is to have the soc node and have all the on-chip
devices defined underneath it.

I read the following from the booting-without-of.txt document:

  f) the /soc<SOCname> node

  This node is used to represent a system-on-a-chip (SoC) and must be
  present if the processor is a SoC. The top-level soc node contains
  information that is global to all devices on the SoC. The node name
  should contain a unit address for the SoC, which is the base address
  of the memory-mapped register set for the SoC. The name of an SoC
  node should start with "soc", and the remainder of the name should
  represent the part number for the soc.  For example, the MPC8540's
  soc node would be called "soc8540".

A lot of device trees didn't follow the soc<SOCname> naming scheme and
just used "soc" as the node name.  I am not sure if we want to enforce
the naming in the future or update the document to make it more relax.

Regards,
Leo

  parent reply	other threads:[~2015-10-01 21:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1441350322-4671-1-git-send-email-bhupesh.sharma@freescale.com>
2015-09-04 21:02 ` [PATCH v2 07/10] dts/ls2085a: Update DTSI to add support of various peripherals Li Yang
2015-09-05  8:37   ` Sharma Bhupesh
2015-09-06 20:57     ` Rob Herring
2015-09-06 21:03       ` Sharma Bhupesh
2015-09-07 20:58         ` Rob Herring
2015-09-09  3:55           ` Sharma Bhupesh
     [not found] ` <CAL_Jsq+9izV8vkrF1tK96M-VRGTMJ+GN5o=RsnCBDcnh-at5kA@mail.gmail.com>
     [not found]   ` <CALRxmdC9ZzGiw6CVnVTqhH1xvA-P9s8cpYbk8DoVq7CodFS0VA@mail.gmail.com>
     [not found]     ` <CY1PR0301MB0748A8F37E3FBE1922AF9D3F874C0@CY1PR0301MB0748.namprd03.prod.outlook.com>
2015-10-01 21:42       ` Li Yang [this message]
2015-10-01 21:58         ` Scott Wood
2015-10-01 22:41           ` Li Yang
2015-10-01 23:18             ` Scott Wood

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='CADRPPNRz-yM_48HvHYv3r31u_b_tHkAjg5H5r+V2mE2=oJTGDA@mail.gmail.com' \
    --to=leoli@freescale.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=Gang.Liu@freescale.com \
    --cc=Minghuan.Lian@freescale.com \
    --cc=Shaohui.Xie@freescale.com \
    --cc=alison.wang@freescale.com \
    --cc=arnd@arndb.de \
    --cc=bhupesh.linux@gmail.com \
    --cc=bhupesh.sharma@freescale.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jaiprakash.singh@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=nikhil.badola@freescale.com \
    --cc=olof@lixom.net \
    --cc=robherring2@gmail.com \
    --cc=scottwood@freescale.com \
    --cc=stuart.yoder@freescale.com \
    --cc=will.deacon@arm.com \
    --cc=yangbo.lu@freescale.com \
    /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).