From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [v3] Add basic address decoding support for Marvell 370/XP
Date: Tue, 21 Aug 2012 13:50:45 +0200 [thread overview]
Message-ID: <20120821135045.58e2a633@skate> (raw)
In-Reply-To: <CABJ1b_RVaSjsneDCvejSMot0ZHDr1dmeroVRDUNMF2y83UGXNA@mail.gmail.com>
Le Tue, 21 Aug 2012 12:37:24 +0200,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> a ?crit :
> I have reworked addr-map to allow for both Armada 370/XP and Orion SoCs
> merging into mach-mvebu. Instead of reusing PLAT_ORION this is totally
> independent but reusing as much code as possible. I can send it hopefully
> today if I get it cleaned up. I also have irq-mvebu, irq-orion, and time-mvebu
> patches that merge code. With that patches booting Dove into mach-mvebu
> works until DMA kicks in because XOR hasn't event touched for DT support
> and is still missing.
>
> Armada 370/XP should still work as they do with current patches in for-3.7
> with little changes in DT. But that of course must be tested by you.
Ok, I will look at your code, but the purpose of
PLAT_ORION/PLAT_ORION_LEGACY was not only to re-use the addr-map code,
but also to allow drivers to access the header files containing their
platform_data structure and other stuff (i.e, all the header files from
arch/arm/plat-orion/include/). How do you handle this problem if
MACH_MVEBU is not a PLAT_ORION platform?
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-21 11:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 9:42 [v3] Add basic address decoding support for Marvell 370/XP Thomas Petazzoni
2012-08-06 9:42 ` [PATCH 1/5] arm: plat-orion: use 'void __iomem *' in addr-map code Thomas Petazzoni
2012-08-06 9:42 ` [PATCH 2/5] arm: plat-orion: introduce PLAT_ORION_LEGACY hidden config option Thomas Petazzoni
2012-08-06 9:42 ` [PATCH 3/5] arm: plat-orion: make bridge_virt_base non-const to support DT use case Thomas Petazzoni
2012-08-06 9:42 ` [PATCH 4/5] arm: mvebu: add basic address decoding support to Armada 370/XP Thomas Petazzoni
2012-08-06 9:42 ` [PATCH 5/5] arm: mvebu: add address decoding controller to the DT Thomas Petazzoni
2012-08-16 13:28 ` [v3] Add basic address decoding support for Marvell 370/XP Jason Cooper
2012-08-16 18:37 ` Jason Cooper
2012-08-17 13:21 ` Thomas Petazzoni
2012-08-19 1:23 ` Jason Cooper
2012-08-19 14:16 ` Arnd Bergmann
2012-08-21 9:46 ` Thomas Petazzoni
2012-08-21 10:37 ` Sebastian Hesselbarth
2012-08-21 11:50 ` Thomas Petazzoni [this message]
2012-08-21 12:45 ` Sebastian Hesselbarth
2012-08-27 23:35 ` Fix orion_nand build on ARCH_MVEBU Thomas Petazzoni
2012-08-27 23:35 ` [PATCH] mtd: orion_nand: remove <mach/hardware.h> include Thomas Petazzoni
2012-08-27 23:35 ` Thomas Petazzoni
2012-08-28 9:11 ` Andrew Lunn
2012-08-28 9:11 ` Andrew Lunn
2012-08-28 9:31 ` Sebastian Hesselbarth
2012-08-28 9:31 ` Sebastian Hesselbarth
2012-08-28 12:22 ` Thomas Petazzoni
2012-08-28 12:22 ` Thomas Petazzoni
2012-08-28 18:12 ` Jason Cooper
2012-08-28 18:12 ` Jason Cooper
2012-08-29 15:46 ` Artem Bityutskiy
2012-08-29 15:46 ` Artem Bityutskiy
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=20120821135045.58e2a633@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 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.