From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 9/9] ARM: ux500: always select ABX500_CORE
Date: Fri, 03 May 2013 13:28:38 +0200 [thread overview]
Message-ID: <15723843.9mConxltov@wuerfel> (raw)
In-Reply-To: <CACRpkdY+5gdh1G7N+_Spg=iNZ0QMZ=ZXuhsVPuMEt62NxPhRxA@mail.gmail.com>
On Friday 03 May 2013 10:14:28 Linus Walleij wrote:
>
> I do not necessarily agree with this commit message.
>
> The only mess I see is that this very patch is missing...
>
> If we look at this:
>
> config UX500_SOC_DB8500
> bool
> select CPU_FREQ_TABLE if CPU_FREQ
> select MFD_DB8500_PRCMU
> select PINCTRL_DB8500
> select PINCTRL_DB8540
> select PINCTRL_AB8500
> select PINCTRL_AB8505
> select PINCTRL_AB9540
> select PINCTRL_AB8540
> select REGULATOR
> select REGULATOR_DB8500_PRCMU
>
> The PRCMU, the PINCTRL drivers, and the PRCMU regulators
> are necessary to boot the system correctly, by which I mean
> necessary so as not to cause potential damage to the hardware.
>
> The PRCMU is a system controller without which the system
> cannot really be brought up, and the ABx500's are the PMICs
> which are developed in pair with the SoC and they are in practice
> Siamese twins, there is no chance you can build a Ux500 system
> without both of them. It just won't even start. There are deep
> dependencies between the PRCMU and the ABx500, as the
> PRCMU firmware will talk directly to the ABx500 without the
> kernel intervening. I.e. the whole set of hardware has to be
> there.
>
> While I understand that from a compile-time point of view it does
> not seem nice, and all things would be separate units that you
> plug in, from a run-time and system architecture point of view it
> makes a lot of sense to select these. Worlds collide...
>
> Apart from that:
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
If they are completely essential, we should not have an entry
like
config AB8500_CORE
bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
select POWER_SUPPLY
select MFD_CORE
select IRQ_DOMAIN
help
Select this option to enable access to AB8500 power management
chip. This connects to U8500 either on the SSP/SPI bus (deprecated
since hardware version v1.0) or the I2C bus via PRCMU. It also adds
the irq_chip parts for handling the Mixed Signal chip events.
This chip embeds various other multimedia funtionalities as well.
(and more of the same) in drivers/mfd/Kconfig. The rule is that you either
make a Kconfig option user-selectable or make it always selected by another
option.
My preference would be to make it user-selectable and enable it only in
the defconfig, but if that can damage the hardware, we should not actually
provide a named option.
Arnd
next prev parent reply other threads:[~2013-05-03 11:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 21:02 [PATCH 0/9] arm-soc: randconfig fixes Arnd Bergmann
2013-05-02 21:02 ` [PATCH 1/9] ARM: tegra: Tegra114 needs CPU_FREQ_TABLE Arnd Bergmann
2013-05-03 4:57 ` Viresh Kumar
2013-05-03 11:20 ` Arnd Bergmann
2013-05-03 12:06 ` Viresh Kumar
2013-05-02 21:02 ` [PATCH 2/9] ARM: OMAP: build SMP code only for OMAP4/5 Arnd Bergmann
2013-05-02 23:30 ` Tony Lindgren
2013-05-02 21:02 ` [PATCH 3/9] ARM: imx: build CPU suspend code only when needed Arnd Bergmann
2013-05-02 21:02 ` [PATCH 4/9] ARM: SPEAr: conditionalize l2x0 support Arnd Bergmann
2013-05-02 21:02 ` [PATCH 5/9] ARM: imx: reset_controller may be disabled Arnd Bergmann
2013-05-02 21:02 ` [PATCH 6/9] ARM: SPEAr: conditionalize SMP code Arnd Bergmann
2013-05-02 21:02 ` [PATCH 7/9] ARM: OMAP: don't select SERIAL_OMAP unconditionally Arnd Bergmann
2013-05-02 23:32 ` Tony Lindgren
2013-05-03 20:34 ` Arnd Bergmann
2013-05-03 21:04 ` Tony Lindgren
2013-05-02 21:02 ` [PATCH 8/9] ARM: SIRF: select SMP_ON_UP only on SMP builds Arnd Bergmann
2013-05-02 21:02 ` [PATCH 9/9] ARM: ux500: always select ABX500_CORE Arnd Bergmann
2013-05-03 8:14 ` Linus Walleij
2013-05-03 11:28 ` Arnd Bergmann [this message]
2013-05-03 12:13 ` Linus Walleij
2013-05-03 12:48 ` Arnd Bergmann
2013-05-03 13:33 ` Linus Walleij
2013-05-03 13:56 ` Arnd Bergmann
2013-05-03 14:06 ` Linus Walleij
2013-05-03 14:20 ` Arnd Bergmann
2013-05-03 18:43 ` Linus Walleij
2013-05-03 19:38 ` Arnd Bergmann
2013-05-03 4:55 ` [PATCH 0/9] arm-soc: randconfig fixes Viresh Kumar
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=15723843.9mConxltov@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