From: Adrian Bunk <bunk@kernel.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org,
David Brownell <david-b@pacbell.net>
Subject: Re: [PATCH v2] gpiolib: Allow user-selection
Date: Sun, 6 Jul 2008 22:52:12 +0300 [thread overview]
Message-ID: <20080706195212.GF21669@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <200807031233.04229.mb@bu3sch.de>
On Thu, Jul 03, 2008 at 12:33:03PM +0200, Michael Buesch wrote:
>...
> --- linux-next.orig/drivers/gpio/Kconfig 2008-07-03 11:31:08.000000000 +0200
> +++ linux-next/drivers/gpio/Kconfig 2008-07-03 11:36:14.000000000 +0200
> @@ -2,15 +2,40 @@
> # GPIO infrastructure and expanders
> #
>
> -config HAVE_GPIO_LIB
> +config ARCH_WANT_OPTIONAL_GPIOLIB
> bool
> help
> + Select this config option from the architecture Kconfig, if
> + it is possible to use gpiolib on the architecture, but let the
> + user decide whether to actually build it or not.
> + Select this instead of ARCH_REQUIRE_GPIOLIB, if your architecture does
> + not depend on GPIOs being available, but rather let the user
> + decide whether he needs it or not.
> +
> +config ARCH_REQUIRE_GPIOLIB
> + bool
> + select GPIOLIB
> + help
> Platforms select gpiolib if they use this infrastructure
> for all their GPIOs, usually starting with ones integrated
> into SOC processors.
> + Selecting this from the architecture code will cause the gpiolib
> + code to always get built in.
> +
> +
> +
> +menuconfig GPIOLIB
> + bool "GPIO Support"
> + depends on ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB
> + select GENERIC_GPIO
> + help
> + This enables GPIO support through the generic GPIO library.
> + You only need to enable this, if you also want to enable
> + one or more of the GPIO expansion card drivers below.
> +
> + If unsure, say N.
>...
The implementation of ARCH_REQUIRE_GPIOLIB does not match the description.
Matching the description would be:
menuconfig GPIOLIB
bool "GPIO Support" if !ARCH_REQUIRE_GPIOLIB
depends on ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB
default ARCH_REQUIRE_GPIOLIB
select GENERIC_GPIO
help
...
> --- linux-next.orig/arch/arm/configs/am200epdkit_defconfig 2008-07-03 11:31:05.000000000 +0200
> +++ linux-next/arch/arm/configs/am200epdkit_defconfig 2008-07-03 11:36:14.000000000 +0200
> @@ -668,7 +668,7 @@
> #
> # CONFIG_SPI is not set
> # CONFIG_SPI_MASTER is not set
> -CONFIG_HAVE_GPIO_LIB=y
> +CONFIG_ARCH_REQUIRE_GPIOLIB=y
>...
Please don't do this kind of defconfig updates - it doesn't bring any
advantage but can create tons of patch conflicts.
The next time a defconfig gets updated it will anyway automatically be
fixed, and for defconfigs that aren't updated it doesn't create any
problems to keep them as they are today until they might one day get
updated.
> Greetings Michael.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-07-06 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 10:33 Michael Buesch
2008-07-06 19:52 ` Adrian Bunk [this message]
2008-07-06 20:01 ` Michael Buesch
2008-07-06 20:13 ` Adrian Bunk
2008-07-06 20:20 ` Michael Buesch
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=20080706195212.GF21669@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®