From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] cleanup mach-s5p*
Date: Tue, 27 Aug 2013 20:45:01 +0200 [thread overview]
Message-ID: <1800157.XgqPQtAyXL@wuerfel> (raw)
In-Reply-To: <14202744.Ci7A03X8EJ@flatron>
On Tuesday 27 August 2013 02:08:16 Tomasz Figa wrote:
>
> Well, if we could drop legacy board file support for them and keep them as
> DT only, support for them could be reasonably simple. Basically the code
> in arch/arm would be limited to a single .c file per SoC (e.g. mach-
> s5pv210-dt.c), a bunch of SoC-level .dtsi files and a bunch of board dts
> files.
Sounds good.
> IMHO the best thing we could do would be creating a single mach-samsung,
> where all the DT-only platforms could be located, including Exynos after
> some remaining consolidation.
Yes, that seems like a reasonable goal for the long run. I guess the best
way to get there might be to move the s5pxxxx platforms into mach-exynos
one by one and make sure they can coexist in a multiplatform kernel.
Consolidating s3c24xx and exynos into a single platform is less interesting
because they won't run the same kernel anyway, but I also don't see any
reason against doing it. Not sure how s3c64xx would fit in then, since
it's ARMv6 but somewhat closer to the s3c24xx code base than to exynos.
Arnd
prev parent reply other threads:[~2013-08-27 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 0:52 [RFC] cleanup mach-s5p* Kukjin Kim
2013-08-26 11:54 ` Marek Szyprowski
2013-08-26 17:58 ` Arnd Bergmann
2013-08-27 0:08 ` Tomasz Figa
2013-08-27 18:45 ` Arnd Bergmann [this message]
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=1800157.XgqPQtAyXL@wuerfel \
--to=arnd@arndb.de \
--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