From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] clocksource: defbool CLKSRC_QCOM=y on ARCH_QCOM and make it visible
Date: Wed, 25 Nov 2015 13:37:53 +0100 [thread overview]
Message-ID: <5655ABA1.6030206@linaro.org> (raw)
In-Reply-To: <3550727.W9y7mWx54D@wuerfel>
On 11/25/2015 11:17 AM, Arnd Bergmann wrote:
> On Wednesday 25 November 2015 11:10:49 Daniel Lezcano wrote:
>> On 11/25/2015 02:08 AM, Stephen Boyd wrote:
>>> We want to remove the ARCH_MSM* configs in mach-qcom/Kconfig
>>> because they are mostly proxy configs for selecting the right
>>> clocksource driver. Therefore, make CLKSRC_QCOM default to the
>>> value of ARCH_QCOM, but also make it visible if ARCH_QCOM=y so
>>> that we can turn it off when we don't want it.
>>
>> I have been removing the ARCH dependencies in the Kconfig file.
>>
>> Why do you have to turn it off manually ?
>
> The background is that this is used only on some of the older
> MSM SoCs, while the newer ones use the arch timer.
>
> We decided to remove the SoC-specific top-level options from
> mach-msm as they are becoming rather meaningless these days
> and just a burden to maintain at the rate that new variants
> get released, so being able to turn off this driver helps make
> the kernel slightly smaller if you are building a kernel for
> only the more recent models.
Ok, thanks for the clarification.
I don't really like this approach even if it is correct because it
breaks the current approach I am trying to make consistent across the
drivers.
I would like to have the COMPILE_TEST option available for all the
drivers and move this option under the menu config. This patch will
prevent to do this code factoring.
On the other side, this option is supposed to have a slightly smaller
kernel when it is not used. But when does it happen ? When
ARCH_MSM8X60=n and ARCH_MSM8960=n. With this patchset, I don't see the
ability to turn these SoCs off as the options are removed. So the
associated code is not removed, right ?
So why allow to turn off the timer but disallow that for the entire SoC ?
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2015-11-25 12:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 1:08 [PATCH 0/3] Remove ARCH_MSM* configs Stephen Boyd
2015-11-25 1:08 ` [PATCH 1/3] clocksource: defbool CLKSRC_QCOM=y on ARCH_QCOM and make it visible Stephen Boyd
2015-11-25 2:07 ` Stephen Boyd
2015-11-25 9:03 ` Arnd Bergmann
2015-11-25 10:10 ` Daniel Lezcano
2015-11-25 10:17 ` Arnd Bergmann
2015-11-25 12:37 ` Daniel Lezcano [this message]
2015-11-25 12:49 ` Arnd Bergmann
2015-11-25 13:22 ` Daniel Lezcano
2015-11-25 1:08 ` [PATCH 2/3] ARM: qcom_defconfig: Enable HAVE_ARM_ARCH_TIMER Stephen Boyd
2015-11-25 1:08 ` [PATCH 3/3] ARM: qcom: Drop ARCH_MSM* configs Stephen Boyd
2015-11-25 12:27 ` Daniel Lezcano
2015-11-25 12:51 ` Arnd Bergmann
2015-11-25 19:34 ` Stephen Boyd
2015-11-25 20:30 ` Arnd Bergmann
2015-11-25 20:39 ` Stephen Boyd
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=5655ABA1.6030206@linaro.org \
--to=daniel.lezcano@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).