From: Arnd Bergmann <arnd@arndb.de>
To: Rob Herring <robherring2@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
Kukjin Kim <kgene.kim@samsung.com>,
linaro-dev@lists.linaro.org, Jason Cooper <jason@lakedaemon.net>,
Nicolas Pitre <nico@fluxnic.net>,
Tony Lindgren <tony@atomide.com>,
Magnus Damm <magnus.damm@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
linux-kernel@vger.kernel.org,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Deepak Saxena <dsaxena@linaro.org>,
Olof Johansson <olof@lixom.net>,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
David Brown <davidb@codeaurora.org>,
shawn.guo@linaro.org,
"Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: Making ARM multiplatform kernels DT-only?
Date: Fri, 4 May 2012 18:56:08 +0000 [thread overview]
Message-ID: <201205041856.08413.arnd@arndb.de> (raw)
In-Reply-To: <4FA40642.5040203@gmail.com>
On Friday 04 May 2012, Rob Herring wrote:
> On 05/04/2012 07:20 AM, Arnd Bergmann wrote:
> > On Thursday 03 May 2012, Russell King - ARM Linux wrote:
> > My plan is to have multiplatform kernels in parallel with what we have now,
> > so we can avoid breaking working machines but also play with multiplatform
> > configurations at the same time for a subset of the platforms and with
> > certain restrictions (not all board files, not all drivers, no generic
> > early printk, ...).
> >
>
> Many of the headers are simply platform_data structs which may still be
> needed on DT platforms, but could be moved elsewhere
Yes, as Russell pointed out, these really should go to
include/linux/platform_data/. My patchset take a few shortcuts there right
now, adding an ugly hack to redirect the header files from their current
locations so I can avoid all the hard work to do that.
> >
> >> We still have irqs.h being SoC dependent, and we still haven't taken
> >> debug-macros.S far enough along to get rid of that.
> >
> > I believe the irqs.h conflict is only for the NR_IRQS constant, all other
> > defines in there should only be used inside of the mach-* directory,
> > or not at all for fully DT-based platforms.
>
> A DT-enabled platform does not need irqs.h or NR_IRQS. SPARSE_IRQ should
> be selected for DT. However, some DT enabled platforms don't have all
> irq chips converted to domains and may still need to set the mach .nr_irqs.
Ah, good to know. I hadn't realized that the #include <mach/irqs.h> in asm/irq.h
is already conditional.
Arnd
next prev parent reply other threads:[~2012-05-04 18:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 13:50 Arnd Bergmann
2012-05-03 13:45 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-03 14:04 ` Russell King - ARM Linux
2012-05-03 13:52 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04 6:31 ` Deepak Saxena
2012-05-04 7:27 ` Russell King - ARM Linux
2012-05-04 12:20 ` Arnd Bergmann
2012-05-04 16:39 ` Rob Herring
2012-05-04 16:56 ` Russell King - ARM Linux
2012-05-04 16:40 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04 16:51 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04 18:56 ` Arnd Bergmann [this message]
2012-05-03 14:18 ` Russell King - ARM Linux
2012-05-03 14:23 ` Magnus Damm
2012-05-03 16:27 ` Arnd Bergmann
2012-05-04 9:22 ` Arnaud Patard
2012-05-04 12:34 ` Arnd Bergmann
2012-05-10 10:55 ` Ben Dooks
2012-05-10 11:02 ` Russell King - ARM Linux
2012-05-03 14:46 ` Sascha Hauer
2012-05-04 16:24 ` Arnd Bergmann
2012-05-05 8:09 ` Sascha Hauer
2012-05-05 13:17 ` Arnd Bergmann
2012-05-14 8:54 ` Arnd Bergmann
2012-05-04 5:38 ` Deepak Saxena
2012-05-04 7:39 ` Russell King - ARM Linux
2012-05-04 14:20 ` Wookey
2012-05-04 14:35 ` Russell King - ARM Linux
2012-05-04 15:17 ` Arnd Bergmann
2012-05-04 16:05 ` Wookey
2012-05-04 18:49 ` Arnd Bergmann
2012-05-04 20:03 ` Linus Walleij
2012-05-04 20:42 ` Christian Robottom Reis
2012-05-04 21:05 ` Arnd Bergmann
2012-05-04 22:43 ` Russell King - ARM Linux
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=201205041856.08413.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=davidb@codeaurora.org \
--cc=dsaxena@linaro.org \
--cc=haojian.zhuang@gmail.com \
--cc=jason@lakedaemon.net \
--cc=kgene.kim@samsung.com \
--cc=linaro-dev@lists.linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=marc.zyngier@arm.com \
--cc=nico@fluxnic.net \
--cc=nicolas.ferre@atmel.com \
--cc=olof@lixom.net \
--cc=plagnioj@jcrosoft.com \
--cc=robherring2@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome