linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: ls1088a: add fsl-mc hardware resource manager node
Date: Fri, 17 Nov 2017 20:35:32 +0800	[thread overview]
Message-ID: <20171117123530.GA25390@dragon> (raw)
In-Reply-To: <DB6PR0401MB2264A182C4048471B53BFF89E02E0@DB6PR0401MB2264.eurprd04.prod.outlook.com>

On Thu, Nov 16, 2017 at 02:24:49PM +0000, Ioana Ciornei wrote:
...
> > > +	fsl_mc: fsl-mc at 80c000000 {
> > 
> > The unit-address of the node should be somehow related to 'reg'
> > property.  Can you please help me understand how they are related?
> 
> The unit-address of the fsl-mc node is the base address of the MC portal described in the first region of the 'reg' property and formed using the 2 address cells.
> Hope this helps.

Ah, sorry, I forgot that the address-cells is 2.

>  
> > 
> > > +		compatible = "fsl,qoriq-mc";
> > > +		reg = <0x00000008 0x0c000000 0 0x40>,	 /* MC portal base */
> > > +		      <0x00000000 0x08340000 0 0x40000>; /* MC control reg */
> > > +		msi-parent = <&its>;
> > > +		#address-cells = <3>;
> > > +		#size-cells = <1>;
> > > +
> > > +		/*
> > > +		 * Region type 0x0 - MC portals
> > > +		 * Region type 0x1 - QBMAN portals
> > > +		 */
> > > +		ranges = <0x0 0x0 0x0 0x8 0x0c000000 0x4000000
> > > +			  0x1 0x0 0x0 0x8 0x18000000 0x8000000>;
> > > +
> > > +		dpmacs {
> > > +			#address-cells = <1>;
> > > +			#size-cells = <0>;
> > > +
> > > +			dpmac1: dpmac at 1 {
> > > +				compatible = "fsl,qoriq-mc-dpmac";
> > > +				reg = <1>;
> > > +			};
> > 
> > Please have a newline in between nodes.
> 
> Will do. 
> 
> Should I send a rework of this patch right away or better to wait for the merge window to close?

Either way is fine, as I will rebase my branch to v4.15-rc1 after merge
window closes.

> > > +			dpmac2: dpmac at 2 {
> > > +				compatible = "fsl,qoriq-mc-dpmac";
> > > +				reg = <2>;
> > > +			};
> > > +			dpmac3: dpmac at 3 {
> > > +				compatible = "fsl,qoriq-mc-dpmac";
> > > +				reg = <3>;
> > > +			};
> > > +			dpmac4: dpmac at 4 {
> > > +				compatible = "fsl,qoriq-mc-dpmac";
> > > +				reg = <4>;
> > > +			};
> > > +			dpmac5: dpmac at 5 {
> > > +				compatible = "fsl,qoriq-mc-dpmac";
> > > +				reg = <5>;
> > > +			};
> > > +			dpmac6: dpmac at 6 {
> > > +				compatible = "fsl,qoriq-mc-dpmac";
> > > +				reg = <6>;
> > > +			};
> > > +			dpmac7: dpmac at 7 {
> > > +				compatible = "fsl,qoriq-mc-dpmac";
> > > +				reg = <7>;
> > > +			};
> > > +			dpmac8: dpmac at 8 {
> > > +				compatible = "fsl,qoriq-mc-dpmac";
> > > +				reg = <8>;
> > > +			};
> > > +			dpmac9: dpmac at 9 {
> > > +				compatible = "fsl,qoriq-mc-dpmac";
> > > +				reg = <9>;
> > > +			};
> > > +			dpmac10: dpmac at 10 {

Just noticed this - the unit-address should be hex number, so it should
be dpmac at a rather than dpmac at 10, I think.

Shawn

> > > +				compatible = "fsl,qoriq-mc-dpmac";
> > > +				reg = <0xa>;
> > > +			};
> > > +		};
> > > +	};
> > > +
> > >  	psci {
> > >  		compatible = "arm,psci-0.2";
> > >  		method = "smc";
> > > --
> > > 1.9.1
> > >
> > >
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2017-11-17 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 13:30 [PATCH] arm64: dts: ls1088a: add fsl-mc hardware resource manager node Ioana Ciornei
2017-11-16  8:39 ` Shawn Guo
2017-11-16 14:24   ` Ioana Ciornei
2017-11-17 12:35     ` Shawn Guo [this message]
2017-11-17 13:59       ` Ioana Ciornei

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=20171117123530.GA25390@dragon \
    --to=shawnguo@kernel.org \
    --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).