linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] ARM: dove: add MBus DT node
Date: Mon, 29 Jul 2013 10:52:28 -0300	[thread overview]
Message-ID: <20130729135227.GA2417@localhost> (raw)
In-Reply-To: <51F661DE.1070106@gmail.com>

Hi Sebastian,

(Ccing devicetree ML)

On Mon, Jul 29, 2013 at 02:36:46PM +0200, Sebastian Hesselbarth wrote:
> On 07/29/2013 02:31 PM, Sebastian Hesselbarth wrote:
> > This adds a MBus node including ranges and pcie apertures required later.
> >
> > Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> > ---
> >   arch/arm/boot/dts/dove.dtsi |   19 +++++++++++++++++++
> >   1 file changed, 19 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/dove.dtsi b/arch/arm/boot/dts/dove.dtsi
> > index 397674c..bdda016 100644
> > --- a/arch/arm/boot/dts/dove.dtsi
> > +++ b/arch/arm/boot/dts/dove.dtsi
> > @@ -29,6 +29,20 @@
> >   		marvell,tauros2-cache-features = <0>;
> >   	};
> >
> > +	mbus {
> > +		compatible = "marvell,dove-mbus", "marvell,mbus", "simple-bus";
> > +		#address-cells = <2>;
> > +		#size-cells = <1>;
> > +		pcie-mem-aperture = <0xe0000000 0x10000000>; /* 256M MEM space */
> > +		pcie-io-aperture  = <0xf2000000 0x00200000>; /*   2M I/O space */
> 
> Actually, current v9 of the mbus patch set still requires "controller"
> property to match the corresponding controller node. I had a short
> discussion with Ezequiel to possibly just use of_find_compatible_node
> and blindly assumed post-v8 will already use it.
> 

Ah, regarding this: despite your good arguin against the 'controller' property approach,
I still feel a bit inclined for it, as I like the way it tightly-binds the two nodes.

Maybe the devicetree maintainers can give their opinions on that matter?

Otherwise, it'll just stay as it is :-)
-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  reply	other threads:[~2013-07-29 13:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 12:31 [PATCH 0/5] ARM: dove: switch to DT MBus Sebastian Hesselbarth
2013-07-29 12:31 ` [PATCH 1/5] ARM: dove: use preprocessor on device tree files Sebastian Hesselbarth
2013-07-29 12:31 ` [PATCH 2/5] ARM: dove: add MBUS_ID macro to Dove DT Sebastian Hesselbarth
2013-07-29 12:31 ` [PATCH 3/5] ARM: dove: add MBus DT node Sebastian Hesselbarth
2013-07-29 12:36   ` Sebastian Hesselbarth
2013-07-29 13:52     ` Ezequiel Garcia [this message]
2013-07-29 14:23       ` Sebastian Hesselbarth
2013-07-29 14:51         ` Ezequiel Garcia
2013-07-29 12:31 ` [PATCH 4/5] ARM: dove: relocate internal registers device nodes Sebastian Hesselbarth
2013-07-29 14:41   ` Ezequiel Garcia
2013-07-29 12:31 ` [PATCH 5/5] ARM: dove: switch to DT probed mbus address windows Sebastian Hesselbarth
2013-07-29 14:32 ` [PATCH 0/5] ARM: dove: switch to DT MBus Ezequiel Garcia
2013-08-06 17:06 ` Jason Cooper

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=20130729135227.GA2417@localhost \
    --to=ezequiel.garcia@free-electrons.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;
as well as URLs for NNTP newsgroup(s).