public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] s3cmci: port DMA code to dmaengine API
Date: Tue, 20 May 2014 14:26:27 +0200	[thread overview]
Message-ID: <5135756.ICUSXn8hND@wuerfel> (raw)
In-Reply-To: <CA+E=qVe0GONTbpe4E_dhg7kwUzG4QpTkxGbBQ2Z00M1B_octQw@mail.gmail.com>

On Tuesday 20 May 2014 14:55:40 Vasily Khoruzhick wrote:
> On Tue, May 20, 2014 at 2:51 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> >> Let's just leave channel number hardcoded, how it was before conversion.
> >> It doesn't seem to be a good idea to clean non-DT machine code now, since
> >> it's better to put some effort into converting s3c2410 and s3c244{0,2} to DT.
> >
> > Ok, fair enough.
> >
> > I'm actually more interested in making s3c24xx multiplatform capable than
> > moving it to DT, but we that requires a few other patches as well, and
> > we can fix this one along with those.
> 
> Hm, but s3c2410, s3c2440 and s3c2442 are armv4t. Is it possible at all
> to make them multiplatform?

Yes, of course. We can run any combination of armv4, armv4t and armv5
CPUs in a multiplatform, we just can't combine them with armv6, armv6k
or armv7.

There is an interesting dependency here: for armv6/v7, we have multiple
Samsung platforms that are mutually exclusive as long as they use ATAGS
based boot: s3c64xx, s5p64xx, s5pc100, s5pv210 and exynos, because the
plat-samsung directory uses mutually exclusive options to pick which set
of mach/*.h headers it uses. The plan here is to move s5pv210 to DT
(same as Exynos already is) and delete s5p64xx and s5pc100, which don't
seem to be used by anybody really. Then all that is left is s3c64xx
using board files and all the non-DT code from plat-samsung becomes
s3c64xx-only.

For s3c24xx, we don't have that problem at all, we can just build
plat-samsung with the s3c24xx headers into the same kernel as things
like mxs, imx1/2, kirkwood, orion, or versatile.

	Arnd

      reply	other threads:[~2014-05-20 12:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 18:03 [PATCH] s3cmci: port DMA code to dmaengine API Vasily Khoruzhick
2014-05-19 18:18 ` Arnd Bergmann
2014-05-19 18:54   ` Vasily Khoruzhick
2014-05-19 19:02     ` Arnd Bergmann
2014-05-19 19:39       ` Vasily Khoruzhick
2014-05-20 10:22       ` Vasily Khoruzhick
2014-05-20 10:39         ` Arnd Bergmann
2014-05-20 11:36           ` Vasily Khoruzhick
2014-05-20 11:51             ` Arnd Bergmann
2014-05-20 11:55               ` Vasily Khoruzhick
2014-05-20 12:26                 ` 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=5135756.ICUSXn8hND@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