linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: multi_v7_defconfig: Enable shmobile platforms
Date: Fri, 29 Aug 2014 20:11:31 +0000	[thread overview]
Message-ID: <3598124.ze8sbSR9ui@wuerfel> (raw)
In-Reply-To: <1965890.bT7bZyQJt8@amdc1032>

On Friday 29 August 2014 20:05:49 Bartlomiej Zolnierkiewicz wrote:
> I've been looking lately into making it possible to easily go
> from multi_v7_defconfig config to a single platform one (in my
> case Exynos one) and removing the need to keep the latter (i.e.
> exynos_defconfig) in the kernel tree in the long-term.
> 
> Because of this I've noticed that some config options for platform
> specific hardware that are selected in multi_v7_defconfig don't
> have proper dependencies.  This results in more complex than
> necessary single platform configs (obtained from a multiplatform
> config) and unnecessarily bigger resulting kernel images.
> 
> Your patch also adds/uncovers some such config options.
> 
> Lets first look at sizes of resulting vmlinux images for single
> platform Exynos config before and after your patch:
> 
>   $ size vmlinux.*
>      text    data     bss     dec     hex filename
>   7817317  517188  278992 8613497  836e79 vmlinux.before
>   7978325  527012  279056 8784393  860a09 vmlinux.after
> 
>   (=> the patch results in 170kB bigger vmlinux size)
> 

Interesting work. We don't currently have a policy for this,
so we should first talk about whether the behavior that you
want is desirable. The alternative would be that everybody
who wants to build a platform-specific kernel out of
multi_v7_defconfig has to go through the extra work of not
only disabling the platforms but also the individual drivers
for the other platforms.

This is a bit tricky for drivers that may be shared between
a few platforms in multi_v7_defconfig but are meaningless
on the others. We could solve that by having more complex
dependencies for each of those drivers, but that is where
maintaining those gets really messy.

A related problem that I think is more significant is that
some platforms 'select' a particular driver and when you
disable the platform, that driver is suddenly removed from the
defconfig for all other platforms as well. This has bitten
us a few times in the past, and I'd really like to fix those
cases first.

	Arnd

  parent reply	other threads:[~2014-08-29 20:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28 14:00 [PATCH 1/2] ARM: multi_v7_defconfig: Enable shmobile platforms Geert Uytterhoeven
2014-08-28 14:00 ` [PATCH 2/2] [RFC] ARM: Set CONFIG_LOCALVERSION in multi v5/v7 defconfigs Geert Uytterhoeven
2014-08-28 23:23 ` [PATCH 1/2] ARM: multi_v7_defconfig: Enable shmobile platforms Simon Horman
2014-08-29 18:05 ` Bartlomiej Zolnierkiewicz
2014-08-29 18:08   ` Bartlomiej Zolnierkiewicz
2014-08-29 20:11   ` Arnd Bergmann [this message]
2014-08-30  9:10     ` Kukjin Kim
2014-09-01  8:58       ` Arnd Bergmann
2014-09-01 10:47       ` Bartlomiej Zolnierkiewicz
2014-08-30  9:32     ` Geert Uytterhoeven
2014-09-01  8:24       ` Arnd Bergmann
2014-09-01  1:54   ` Simon Horman
2014-09-01 12:42     ` Bartlomiej Zolnierkiewicz
2014-09-01 13:19       ` Simon Horman
2014-09-10  0:48 ` Simon Horman
2014-11-25 15:08   ` Geert Uytterhoeven

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=3598124.ze8sbSR9ui@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;
as well as URLs for NNTP newsgroup(s).