From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] arm: dts: Convert mvebu device tree files to 64 bits
Date: Thu, 21 Mar 2013 20:18:07 +0100 [thread overview]
Message-ID: <20130321201807.7cb04978@skate> (raw)
In-Reply-To: <201303211903.52383.arnd@arndb.de>
Dear Arnd Bergmann,
On Thu, 21 Mar 2013 19:03:52 +0000, Arnd Bergmann wrote:
> On Thursday 21 March 2013, Rob Herring wrote:
> > > soc {
> > > - #address-cells = <1>;
> > > - #size-cells = <1>;
> > > + #address-cells = <2>;
> > > + #size-cells = <2>;
> >
> > If all the addresses for the soc bus are below 4GB or even within a 4GB
> > range if using the ranges property, then changing all this and
> > everything below it is kind of pointless.
>
> Good point. We'll probably also have to change it all again when we add a new
> binding for that bus in 3.10, so it makes sense to change it only once.
In the mean time can we do something like:
soc {
compatible = "simple-bus";
range = <...>;
[... all the peripherals ...]
};
with the range = <...> property converting the peripheral registers
base address (expressed as offsets in the reg = <...> properties of the
subnodes) into the absolute physical address?
I'm planning to work on the DT binding for the mvebu-mbus driver as
soon as the PCIe driver gets accepted, but it would be good to have an
intermediate solution to get the LPAE support in.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-03-21 19:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 16:26 [PATCH 0/5] arm: mvebu: Enable LPAE support for Armada XP SoCs Gregory CLEMENT
2013-03-21 16:26 ` [PATCH 1/5] arm: mvebu: Aligne the internal registers virtual base to support LPAE Gregory CLEMENT
2013-03-21 16:26 ` [PATCH 2/5] arm: mvebu: Select DMA_BOUNCE when LPAE is selected in Kconfig Gregory CLEMENT
2013-03-21 18:19 ` Rob Herring
2013-03-21 19:18 ` Andrew Lunn
2013-03-22 11:32 ` Russell King - ARM Linux
2013-03-21 16:26 ` [PATCH 3/5] arm: mvebu: Enable pj4b on LPAE compilations Gregory CLEMENT
2013-03-21 16:26 ` [PATCH 4/5] arm: dts: Add a 64 bits version of the skeleton device tree Gregory CLEMENT
2013-03-21 16:26 ` [PATCH 5/5] arm: dts: Convert mvebu device tree files to 64 bits Gregory CLEMENT
2013-03-21 17:59 ` Rob Herring
2013-03-21 19:03 ` Arnd Bergmann
2013-03-21 19:18 ` Thomas Petazzoni [this message]
2013-03-21 21:31 ` Arnd Bergmann
2013-03-21 22:30 ` Sebastian Hesselbarth
2013-03-21 20:15 ` Andrew Lunn
2013-03-21 20:22 ` Thomas Petazzoni
2013-03-21 20:30 ` Jason Cooper
2013-03-21 20:37 ` Andrew Lunn
2013-03-21 21:08 ` Thomas Petazzoni
2013-03-21 21:16 ` Thomas Petazzoni
2013-03-21 20:55 ` Jason Gunthorpe
2013-03-21 21:15 ` Thomas Petazzoni
2013-03-21 21:35 ` Lior Amsalem
2013-03-21 21:46 ` Jason Gunthorpe
2013-03-21 21:58 ` Lior Amsalem
2013-03-22 6:55 ` Arnd Bergmann
2013-03-21 21:41 ` Jason Gunthorpe
2013-03-21 22:26 ` Sebastian Hesselbarth
2013-03-22 9:55 ` Arnd Bergmann
2013-03-21 21:25 ` Andrew Lunn
2013-03-22 6:28 ` Andrew Lunn
2013-03-22 17:43 ` Jason Gunthorpe
2013-03-22 19:33 ` Arnd Bergmann
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=20130321201807.7cb04978@skate \
--to=thomas.petazzoni@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).