All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@marvell.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Bjorn Helgaas <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: [query] how to use "ranges" in device tree
Date: Thu, 16 Apr 2015 21:59:38 +0800	[thread overview]
Message-ID: <20150416215938.347caa68@xhacker> (raw)

Hi all,

I didn't fully understand the "ranges" usage, here is one situation which I dunno
how to handle.

In arch/arm/boot/dts/berlin2q.dtsi, we describe the /soc ranges as

ranges = <0 0xf7000000 0x1000000>;

That's fine. Now there's a pci device based on pcie-designware.c which prefer
put "config" space in reg. But the config space starts at 0xe0000000, due to
the /soc ranges, the "config" space following pcie node is not correct in fact.

soc {
	ranges = <0 0xf7000000 0x1000000>;
	...
	pcie: pcie@e40000 {
		compatible = "...";
		reg = <0xe40000 0x10000>, <0xe0000000 0x8000000>;
		reg-names = "dbi", "pad", "config";
		...
	};
	...
};

How to define the "config" space in this situation? Did we need to change
the /soc ranges as the following?

soc {
	ranges;
}

Thanks in advance,
Jisheng

WARNING: multiple messages have this Message-ID (diff)
From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [query] how to use "ranges" in device tree
Date: Thu, 16 Apr 2015 21:59:38 +0800	[thread overview]
Message-ID: <20150416215938.347caa68@xhacker> (raw)

Hi all,

I didn't fully understand the "ranges" usage, here is one situation which I dunno
how to handle.

In arch/arm/boot/dts/berlin2q.dtsi, we describe the /soc ranges as

ranges = <0 0xf7000000 0x1000000>;

That's fine. Now there's a pci device based on pcie-designware.c which prefer
put "config" space in reg. But the config space starts at 0xe0000000, due to
the /soc ranges, the "config" space following pcie node is not correct in fact.

soc {
	ranges = <0 0xf7000000 0x1000000>;
	...
	pcie: pcie at e40000 {
		compatible = "...";
		reg = <0xe40000 0x10000>, <0xe0000000 0x8000000>;
		reg-names = "dbi", "pad", "config";
		...
	};
	...
};

How to define the "config" space in this situation? Did we need to change
the /soc ranges as the following?

soc {
	ranges;
}

Thanks in advance,
Jisheng

             reply	other threads:[~2015-04-16 14:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 13:59 Jisheng Zhang [this message]
2015-04-16 13:59 ` [query] how to use "ranges" in device tree Jisheng Zhang
2015-04-16 22:59 ` Jaehoon Chung
2015-04-16 22:59   ` Jaehoon Chung
2015-04-17  2:24   ` Jisheng Zhang
2015-04-17  2:24     ` Jisheng Zhang
2015-04-17  3:50     ` Jisheng Zhang
2015-04-17  3:50       ` Jisheng Zhang
2015-04-17  8:32       ` Arnd Bergmann
2015-04-17  8:32         ` Arnd Bergmann
2015-04-17  8:45         ` Jisheng Zhang
2015-04-17  8:45           ` Jisheng Zhang
2015-04-17  9:38           ` Arnd Bergmann
2015-04-17  9:38             ` Arnd Bergmann
2015-04-17  8:38       ` Sebastian Hesselbarth
2015-04-17  8:38         ` Sebastian Hesselbarth
2015-04-17  8:51         ` Jisheng Zhang
2015-04-17  8:51           ` Jisheng Zhang

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=20150416215938.347caa68@xhacker \
    --to=jszhang@marvell.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sebastian.hesselbarth@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.