From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: arm: mvebu: Add basic address decoding support for Marvell 370/XP
Date: Sat, 4 Aug 2012 18:27:30 +0200 [thread overview]
Message-ID: <20120804182730.1ef77f23@skate> (raw)
In-Reply-To: <201208031423.10561.arnd@arndb.de>
Le Fri, 3 Aug 2012 14:23:09 +0000,
Arnd Bergmann <arnd@arndb.de> a ?crit :
> On Friday 03 August 2012, Thomas Petazzoni wrote:
> > Here is a small patch set that introduces basic support for address
> > decoding on Armada 370 and Armada XP. The aim of this basic support
> > is essentially to be able to configure a window to remap the
> > BootROM, which is needed to startup the secondary CPUs for the SMP
> > support.
> >
> > As we had discussed already, the address decoding configuration is
> > not described in the Device Tree, it is for now hardcoded on a
> > per-SoC basis. We might later discuss how to extend this to the
> > Device Tree.
>
> Makes sense. I wonder if there is a proper way to describe the
> setting in the device tree anyway, given that there is more than one
> valid option to do it.
Well, we could do something like:
addr-decoding at d0020000 {
compatible = "marvell,armada-addr-decoding-controller";
reg = <0xd0020000 0x258>;
window at 0 {
/* Window number */
cell-index = <0>;
/* Physical address and size at which the device will be mapped. */
reg = <0xfff00000 0x100000>;
/* Which device is being mapped. Can either have 1
integer (for "big" devices) or 2 integers (for devices
in the "Device Bus") */
marvell,target = <0x1 0x1d>;
/* Optional. Remapping address */
marvell,remap = <...>;
};
window at 12 {
cell-index = <12>;
reg = <0x... 0x....>;
marvell,target = <0x4>;
};
};
This is just a rough draft, just written in the mail, I haven't even
tried writing code that would work with it, but it should be relatively
easy to do.
Would that make sense? Of course, suggestions welcome, I'm not an
expert on how to decide what is the best DT encoding for such data.
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:[~2012-08-04 16:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 13:10 arm: mvebu: Add basic address decoding support for Marvell 370/XP Thomas Petazzoni
2012-08-03 13:10 ` [PATCH 1/4] arm: plat-orion: introduce PLAT_ORION_LEGACY hidden config option Thomas Petazzoni
2012-08-03 13:26 ` Gregory CLEMENT
2012-08-03 13:10 ` [PATCH 2/4] arm: plat-orion: make bridge_virt_base non-const to support DT use case Thomas Petazzoni
2012-08-03 13:27 ` Gregory CLEMENT
2012-08-03 13:41 ` Arnd Bergmann
2012-08-03 13:48 ` Thomas Petazzoni
2012-08-03 13:10 ` [PATCH 3/4] arm: mvebu: add basic address decoding support to Armada 370/XP Thomas Petazzoni
2012-08-03 13:28 ` Gregory CLEMENT
2012-08-03 13:10 ` [PATCH 4/4] arm: mvebu: add address decoding controller to the DT Thomas Petazzoni
2012-08-03 13:29 ` Gregory CLEMENT
2012-08-03 14:23 ` arm: mvebu: Add basic address decoding support for Marvell 370/XP Arnd Bergmann
2012-08-04 16:27 ` Thomas Petazzoni [this message]
2012-08-04 16:50 ` 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=20120804182730.1ef77f23@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).