From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] AT91: add AT91SAM9X5 dummy configuration variable
Date: Tue, 5 Jul 2011 13:25:47 +0200 [thread overview]
Message-ID: <201107051325.47417.arnd@arndb.de> (raw)
In-Reply-To: <20110705053229.GC27909@game.jcrosoft.org>
On Tuesday 05 July 2011, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > You have convinced me.
> > But I will have to remove the other dependencies that I mentioned before
> > in the thread.
> >
> > We can drop this patch.
> I prefer to hide the platform specific driver other wise we will have a huge
> menu entry in Kconfig with unrelated drivers that can not be used at all on
> the selected mach
I fear it's too late for that. You already have to decide on many thousands
of configuration options, most of which are totally irrelevant for a
particular system.
IMHO, the two much better ways to deal with SOC-specific device drivers
are defconfig files and/or specific defaults, like
config ABX500_CORE
bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
default ARCH_U300 || ARCH_U8500
This lets everybody choose whether they would like to build the driver
or not, which is very useful for allyesconfig/allnoconfig/randconfig
builds. At the same time, the default gets it right in almost all
other cases.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: "Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
balbi@ti.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, avictor.za@gmail.com
Subject: Re: [PATCH] AT91: add AT91SAM9X5 dummy configuration variable
Date: Tue, 5 Jul 2011 13:25:47 +0200 [thread overview]
Message-ID: <201107051325.47417.arnd@arndb.de> (raw)
In-Reply-To: <20110705053229.GC27909@game.jcrosoft.org>
On Tuesday 05 July 2011, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > You have convinced me.
> > But I will have to remove the other dependencies that I mentioned before
> > in the thread.
> >
> > We can drop this patch.
> I prefer to hide the platform specific driver other wise we will have a huge
> menu entry in Kconfig with unrelated drivers that can not be used at all on
> the selected mach
I fear it's too late for that. You already have to decide on many thousands
of configuration options, most of which are totally irrelevant for a
particular system.
IMHO, the two much better ways to deal with SOC-specific device drivers
are defconfig files and/or specific defaults, like
config ABX500_CORE
bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
default ARCH_U300 || ARCH_U8500
This lets everybody choose whether they would like to build the driver
or not, which is very useful for allyesconfig/allnoconfig/randconfig
builds. At the same time, the default gets it right in almost all
other cases.
Arnd
next prev parent reply other threads:[~2011-07-05 11:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 11:35 [PATCH] AT91: add AT91SAM9X5 dummy configuration variable Nicolas Ferre
2011-06-28 11:35 ` Nicolas Ferre
2011-06-28 10:35 ` Felipe Balbi
2011-06-28 10:35 ` Felipe Balbi
2011-06-28 12:13 ` Nicolas Ferre
2011-06-28 12:13 ` Nicolas Ferre
2011-06-28 12:26 ` Felipe Balbi
2011-06-28 12:26 ` Felipe Balbi
2011-06-28 16:02 ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-28 16:02 ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-29 9:30 ` Felipe Balbi
2011-06-29 9:30 ` Felipe Balbi
2011-06-29 15:24 ` Nicolas Ferre
2011-06-29 15:24 ` Nicolas Ferre
2011-06-29 15:39 ` Felipe Balbi
2011-06-29 15:39 ` Felipe Balbi
2011-07-02 9:49 ` Arnd Bergmann
2011-07-02 9:49 ` Arnd Bergmann
2011-07-04 9:23 ` Nicolas Ferre
2011-07-04 9:23 ` Nicolas Ferre
2011-07-05 5:32 ` Jean-Christophe PLAGNIOL-VILLARD
2011-07-05 5:32 ` Jean-Christophe PLAGNIOL-VILLARD
2011-07-05 11:25 ` Arnd Bergmann [this message]
2011-07-05 11:25 ` Arnd Bergmann
2011-06-28 16:03 ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-28 16:03 ` Jean-Christophe PLAGNIOL-VILLARD
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=201107051325.47417.arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.