From: Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Ioana Ciornei <ioana.ciornei-3arQi8VN3Tc@public.gmane.org>
Cc: "mark.rutland-5wv7dgnIgG8@public.gmane.org"
<mark.rutland-5wv7dgnIgG8@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"catalin.marinas-5wv7dgnIgG8@public.gmane.org"
<catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
"will.deacon-5wv7dgnIgG8@public.gmane.org"
<will.deacon-5wv7dgnIgG8@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [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-2mNvjAGDOPl4towakvZX7o3W/0Ik+aLCnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
On Thu, Nov 16, 2017 at 02:24:49PM +0000, Ioana Ciornei wrote:
...
> > > + fsl_mc: fsl-mc@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@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@2 {
> > > + compatible = "fsl,qoriq-mc-dpmac";
> > > + reg = <2>;
> > > + };
> > > + dpmac3: dpmac@3 {
> > > + compatible = "fsl,qoriq-mc-dpmac";
> > > + reg = <3>;
> > > + };
> > > + dpmac4: dpmac@4 {
> > > + compatible = "fsl,qoriq-mc-dpmac";
> > > + reg = <4>;
> > > + };
> > > + dpmac5: dpmac@5 {
> > > + compatible = "fsl,qoriq-mc-dpmac";
> > > + reg = <5>;
> > > + };
> > > + dpmac6: dpmac@6 {
> > > + compatible = "fsl,qoriq-mc-dpmac";
> > > + reg = <6>;
> > > + };
> > > + dpmac7: dpmac@7 {
> > > + compatible = "fsl,qoriq-mc-dpmac";
> > > + reg = <7>;
> > > + };
> > > + dpmac8: dpmac@8 {
> > > + compatible = "fsl,qoriq-mc-dpmac";
> > > + reg = <8>;
> > > + };
> > > + dpmac9: dpmac@9 {
> > > + compatible = "fsl,qoriq-mc-dpmac";
> > > + reg = <9>;
> > > + };
> > > + dpmac10: dpmac@10 {
Just noticed this - the unit-address should be hex number, so it should
be dpmac@a rather than dpmac@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-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent 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
[not found] ` <1510147805-24873-1-git-send-email-ioana.ciornei-3arQi8VN3Tc@public.gmane.org>
2017-11-16 8:39 ` Shawn Guo
2017-11-16 14:24 ` Ioana Ciornei
[not found] ` <DB6PR0401MB2264A182C4048471B53BFF89E02E0-2mNvjAGDOPl4towakvZX7o3W/0Ik+aLCnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
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-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ioana.ciornei-3arQi8VN3Tc@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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).