From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists.infradead.org
Subject: Making ARM multiplatform kernels DT-only?
Date: Fri, 4 May 2012 18:51:28 +0200 [thread overview]
Message-ID: <20120504165128.GI7788@game.jcrosoft.org> (raw)
In-Reply-To: <20120504165603.GK897@n2100.arm.linux.org.uk>
On 17:56 Fri 04 May , Russell King - ARM Linux wrote:
> On Fri, May 04, 2012 at 11:39:30AM -0500, Rob Herring wrote:
> > Many of the headers are simply platform_data structs which may still be
> > needed on DT platforms, but could be moved elsewhere.
>
> Those should be in include/linux/platform.
>
> > >> Then there's also the problem of uncompress.h. The last piece of the
> > >> puzzle is the common clock stuff.
> >
> > The smp/hotplug/localtimer related functions are still global. Marc Z
> > has posted patches for this, but I haven't seen recent activity. This
> > and clocks were the 2 main issues I saw trying to build 2 platforms
> > together. highbank and picoxcell could be built together since only
> > highbank has clocks and smp.
> >
> > gpio.h is still required, but empty for most platforms.
>
> Those empty gpio.h files are definitely a candidate for going into
> arch/arm/include/mach/gpio.h, and then all those 12-byte mach/gpio.h can
> be deleted (13 files).
>
> We've not had any progress on the gpio.h issue since I did the last round
> of cleanup; the next stage was to persuade SoC maintainers to get rid of
> their optimized versions which aren't compatible with multi-platform
> kernels.
>
> I don't know if folk are expecting me to push that forwards or whether
> there's someone else working on that aspect of it...
>
> So this issue really does need to be progressed too.
same with CLOCK_TICK_RATE
at91 (expect at91x40) and imx we drop it but nearly on the other platform
did not
Best Regards,
J.
next prev parent reply other threads:[~2012-05-04 16:51 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 13:50 Making ARM multiplatform kernels DT-only? 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 [this message]
2012-05-04 18:56 ` Arnd Bergmann
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 (Rtp)
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=20120504165128.GI7788@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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).