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] ARM: EXYNOS: Add ARCH_EXYNOS and reorganize arch/arm/mach-exynos
Date: Mon, 03 Oct 2011 16:04:11 +0200	[thread overview]
Message-ID: <3709260.I9R44Iti1S@wuerfel> (raw)
In-Reply-To: <4E89AD44.80609@samsung.com>

On Monday 03 October 2011 21:40:36 Kukjin Kim wrote:
> Yes, absolutely. As I said, the 'mach-exynos' can support upcoming 
> Samsung EXYNOS SoCs and the way is better than making mach-exynos5.
> 
> My bigger plan is finally to make current directories to 3 mach- dir. 
> (mach-s3c, mach-s5p, and mach-exynos) and 1 plat-samsung directory. Of 
> course, the mach- directories can be reduced later.
>
> Firstly, as you can see, I'm merging plat-s3c24xx and plat-s5p into one 
> plat-samsung directory and actually the <plat/*.h> files and dev-*.c 
> files have been moved into plat-samsung. Maybe I can finish it during 
> 3.2-rc.

Ok, sounds good. So for my understanding: is s5p a completely separate
line from exynos, or are they more of an evolutionary succession where
you draw the line between the last uniprocessor and the first SMP
chip?
 
> Secondary, upcoming Samsung EXYNOS SoCs will be supported in mach-exynos 
> directory and this patch is required to that. For example, the EXYNOS5 
> SoCs (Cortex A15) will be supported in that with other EXYNOS4 SoCs soon 
> and of course it reduces code duplication 

My feeling is that it would be nicer to just add exynos5 to the mach-exynos4
directory for now, in the same way that omap3/4/5 are in the mach-omap2
directory. We can do a big rename later once the reorganization of code
within those directories that you explained above is complete.

If you still want to do the big rename right now, I would suggest doing
it at the end of the 3.2 merge window, so that all other patches that
might need to touch the mach-exynos4 directory can go in first.

	Arnd

  reply	other threads:[~2011-10-03 14:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-02  9:25 [PATCH] ARM: EXYNOS: Add ARCH_EXYNOS and reorganize arch/arm/mach-exynos Kukjin Kim
2011-10-03  4:02 ` Kyungmin Park
2011-10-03  9:33   ` Arnd Bergmann
2011-10-03 12:40     ` Kukjin Kim
2011-10-03 14:04       ` Arnd Bergmann [this message]
2011-10-04 12:45         ` Kukjin Kim

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=3709260.I9R44Iti1S@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