From: john.stultz@linaro.org (John Stultz)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC, PATCH] clocksource: provide timekeeping for efm32 SoCs
Date: Wed, 25 Sep 2013 16:55:15 -0700 [thread overview]
Message-ID: <524377E3.4050806@linaro.org> (raw)
In-Reply-To: <524376A0.7020405@linaro.org>
On 09/25/2013 04:49 PM, Daniel Lezcano wrote:
> On 09/25/2013 05:32 PM, Uwe Kleine-K?nig wrote:
>> Hello Daniel,
>>
>> On Wed, Sep 25, 2013 at 04:33:24PM +0200, Daniel Lezcano wrote:
>>> On 09/16/2013 11:44 AM, Uwe Kleine-K?nig wrote:
>>>> diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
>>>> index 41c6946..410b152 100644
>>>> --- a/drivers/clocksource/Kconfig
>>>> +++ b/drivers/clocksource/Kconfig
>>>> @@ -70,6 +70,14 @@ config CLKSRC_DBX500_PRCMU_SCHED_CLOCK
>>>> help
>>>> Use the always on PRCMU Timer as sched_clock
>>>>
>>>> +config CLKSRC_EFM32
>>>> + bool "Clocksource for Energy Micro's EFM32 SoCs" if !ARCH_EFM32
>>>> + depends on OF && ARM && (ARCH_EFM32 || COMPILE_TEST)
>>>> + default ARCH_EFM32
>>>> + help
>>>> + Support to use the timers of EFM32 SoCs as clock source and clock
>>>> + event device.
>>>> +
>>> No option for the timer. It must be selected by the platform.
>> It is. If ARCH_EFM32=y there is no prompt and the "default ARCH_EFM32"
>> makes it true.
> ok, with that but if ARCH_EFM32=no, you can enable it manually. AFAIK,
> we want to prevent this and let the correct arch to enable it.
>
> John ?
Right until there's really a compelling reason (which I've still not
heard), I don't want to introduce independent clocksource options. Any
such options should be something like a platform or board config option.
thanks
-john
next prev parent reply other threads:[~2013-09-25 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 9:44 [RFC, PATCH] clocksource: provide timekeeping for efm32 SoCs Uwe Kleine-König
2013-09-25 14:33 ` Daniel Lezcano
2013-09-25 15:32 ` Uwe Kleine-König
2013-09-25 23:49 ` Daniel Lezcano
2013-09-25 23:55 ` John Stultz [this message]
2013-09-26 7:58 ` Uwe Kleine-König
2013-09-26 8:20 ` Uwe Kleine-König
2013-09-26 8:52 ` Daniel Lezcano
2013-09-26 9:05 ` Uwe Kleine-König
2013-10-01 8:08 ` Uwe Kleine-König
2013-10-01 15:57 ` Stephen Warren
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=524377E3.4050806@linaro.org \
--to=john.stultz@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).