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: [RFC PATCH] arm64: defconfig: add config fragment for Freescale SoCs
Date: Sat, 16 Apr 2016 18:50:53 +0200	[thread overview]
Message-ID: <4532019.nAsqsHX23H@wuerfel> (raw)
In-Reply-To: <20160414170433.GF15182@e104818-lin.cambridge.arm.com>

On Thursday 14 April 2016 18:04:33 Catalin Marinas wrote:
> 
> > Allowing us to have a freescale.config gives us the flexibility of
> > adding Freescale specific options without having to keep this in
> > some other external repo.  It also keeps vendor specific clutter
> > out of the base defconfig.  With the number of new armv8 chips 
> > coming out the single defconfig is going to produce increasingly
> > large kernels, since all drivers are built-in.
> 
> As I said, for the time being please add all the sane the options to
> defconfig. I want to be able to build a defconfig and run on all
> supported SoCs.

I'd suggest making the non-essential drivers loadable modules though,
in particular the sensor drivers.

There are two block device drivers included here (SoC specific
front-ends for AHCI and SDHCI), I'm not sure about what to do with
them, but we should try to do it consistently, either making
them all built-in to simplify booting from them without a ramdisk,
or try to make them all modules as well.

	Arnd

  reply	other threads:[~2016-04-16 16:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 14:21 [RFC PATCH] arm64: defconfig: add config fragment for Freescale SoCs Stuart Yoder
2016-04-14 17:04 ` Catalin Marinas
2016-04-16 16:50   ` Arnd Bergmann [this message]
2016-04-18 12:38     ` Catalin Marinas
2016-04-17  9:10   ` Martinez Kristofer
2016-04-17 18:12     ` Catalin Marinas
2016-04-18 13:28     ` Stuart Yoder
2016-04-19 16:09   ` Stuart Yoder

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=4532019.nAsqsHX23H@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