From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: yamada.masahiro@socionext.com
Cc: arnd@arndb.de, linux-arm-kernel@lists.infradead.org,
arm@kernel.org, mmarek@suse.com, olof@lixom.net,
linux-kbuild@vger.kernel.org, jamie@jamieiles.com,
agross@codeaurora.org, kernel@pengutronix.de,
gregory.clement@free-electrons.com, linux-sh@vger.kernel.org,
tsahee@annapurnalabs.com, linux-arm-msm@vger.kernel.org,
linus.walleij@linaro.org, galak@codeaurora.org,
plagnioj@jcrosoft.com, dinguyen@opensource.altera.com,
baohua@kernel.org, shiraz.linux.kernel@gmail.com,
rjui@broadcom.com, patrice.chotard@st.com, kernel@stlinux.com,
soren.brinkmann@xilinx.com, horms@verge.net.au,
michal.simek@xilinx.com, heiko@sntech.de,
linux-rockchip@lists.infradead.org, linux-soc@vger.kernel.org,
davidb@codeaurora.org, sbranden@broadcom.com, vireshk@kernel.org,
alexandre.belloni@free-electrons.com, kyungmin.park@samsung.com,
mappyland78@gmail.com, k.kozlowski@samsung.com, bcm-kernel-fee
Subject: Re: [PATCH] ARM: use "depends on" for SoC configs instead of "if" after prompt
Date: Mon, 16 Nov 2015 11:06:22 +0000 [thread overview]
Message-ID: <20151116110622.GL8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <d5271606263b496c841abd62647f9db0@SOC-EX02V.e01.socionext.com>
On Mon, Nov 16, 2015 at 10:32:51AM +0000, yamada.masahiro@socionext.com wrote:
> Hi Arnd,
>
>
> > On Monday 16 November 2015 12:06:10 Masahiro Yamada wrote:
> > > Many ARM sub-architectures use prompts followed by "if" conditional,
> > > but it is wrong.
> > >
> > > Please notice the difference between
> > >
> > > config ARCH_FOO
> > > bool "Foo SoCs" if ARCH_MULTI_V7
> > >
> > > and
> > >
> > > config ARCH_FOO
> > > bool "Foo SoCs"
> > > depends on ARCH_MULTI_V7
> > >
> > > These two are *not* equivalent!
> > >
> > > In the former statement, it is not ARCH_FOO, but its prompt that
> > > depends on ARCH_MULTI_V7. So, it is completely valid that ARCH_FOO is
> > > selected by another, but ARCH_MULTI_V7 is still disabled. As it is not
> > > unmet dependency, Kconfig never warns. This is probably not what you
> > > want.
> >
> > Did you encounter a case where someone actually did a 'select' on one of
> > those symbols? I probably introduced a lot of them and did not expect that
> > to happen.
>
> No, for ARM sub-architectures.
> But, yes for the ARM core part.
>
>
> For example, the following entry in arch/arm/Kconfig is suspicous.
>
> config PCI
> bool "PCI support" if MIGHT_HAVE_PCI
> help
> Find out whether you have a PCI motherboard. PCI is the name of a
> bus system, i.e. the way the CPU talks to the other stuff inside
> your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
> VESA. If you have PCI, say Y, otherwise N.
>
>
>
>
> Try "make ARCH=arm footbridge_defconfig" and check the .config file.
>
> It defines CONFIG_PCI=y, but not CONFIG_MIGHT_HAVE_PCI.
> I am not sure this is a sane .config or not.
It's correct. "MIGHT_HAVE_PCI" is used by platforms which _might_ _have_
_PCI_, not by platforms which _do_ _have_ _PCI_. Platforms which _do_
_have_ _PCI_ select PCI directly, and because "MIGHT_HAVE_PCI" is not
set, users are not offered an option that they can never disable.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-11-16 11:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 3:06 [PATCH] ARM: use "depends on" for SoC configs instead of "if" after prompt Masahiro Yamada
[not found] ` <1447643170-23773-1-git-send-email-yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org>
2015-11-16 9:31 ` Maxime Ripard
2015-11-16 10:05 ` Arnd Bergmann
2015-11-16 10:32 ` yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A
2015-11-16 11:06 ` Russell King - ARM Linux [this message]
2015-11-16 10:38 ` Nicolas Ferre
2015-11-16 11:12 ` Heiko Stübner
2015-11-16 12:26 ` Patrice Chotard
2015-11-16 12:59 ` Liviu Dudau
2015-11-16 23:49 ` Krzysztof Kozlowski
2015-11-17 10:42 ` Matthias Brugger
2015-11-17 18:04 ` Simon Horman
2015-11-23 18:10 ` Gregory CLEMENT
2015-11-24 9:30 ` Shawn Guo
2015-11-24 15:58 ` Thierry Reding
2015-11-25 2:09 ` yamada.masahiro
2015-11-25 12:13 ` Krzysztof Hałasa
2015-11-30 10:43 ` Maxime Coquelin
2015-12-01 21:46 ` Arnd Bergmann
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=20151116110622.GL8644@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=agross@codeaurora.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=baohua@kernel.org \
--cc=davidb@codeaurora.org \
--cc=dinguyen@opensource.altera.com \
--cc=galak@codeaurora.org \
--cc=gregory.clement@free-electrons.com \
--cc=heiko@sntech.de \
--cc=horms@verge.net.au \
--cc=jamie@jamieiles.com \
--cc=k.kozlowski@samsung.com \
--cc=kernel@pengutronix.de \
--cc=kernel@stlinux.com \
--cc=kyungmin.park@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mappyland78@gmail.com \
--cc=michal.simek@xilinx.com \
--cc=mmarek@suse.com \
--cc=olof@lixom.net \
--cc=patrice.chotard@st.com \
--cc=plagnioj@jcrosoft.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=shiraz.linux.kernel@gmail.com \
--cc=soren.brinkmann@xilinx.com \
--cc=tsahee@annapurnalabs.com \
--cc=vireshk@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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