public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: stefan@agner•ch (Stefan Agner)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC 2/7] clocksource: add dependencies for Vybrid pit clocksource
Date: Mon, 13 Oct 2014 11:46:06 +0200	[thread overview]
Message-ID: <98ca2b7a76dc786a36cf6c4113ca751f@agner.ch> (raw)
In-Reply-To: <20141012181821.GQ31554@pengutronix.de>

Am 2014-10-12 20:18, schrieb Uwe Kleine-K?nig:
> Hello,
> 
> On Sun, Oct 12, 2014 at 08:13:56PM +0200, Stefan Agner wrote:
>> Add the minimal dependencies required to use the Vybrid PIT
>> clocksource driver. Those are not part of the SoC dependencies.
>>
>> Signed-off-by: Stefan Agner <stefan@agner•ch>
>> ---
>>  drivers/clocksource/Kconfig | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
>> index cfd6519..26464dd 100644
>> --- a/drivers/clocksource/Kconfig
>> +++ b/drivers/clocksource/Kconfig
>> @@ -146,6 +146,8 @@ config FSL_FTM_TIMER
>>
>>  config VF_PIT_TIMER
>>  	bool
>> +	select CLKSRC_MMIO
>> +	select CLKSRC_OF
>>  	help
>>  	  Support for Period Interrupt Timer on Freescale Vybrid Family SoCs.
> This one seems to qualify as a fix for the MMU stuff, right?

Well, this appeared when working on the !MMU stuff. Because on the MMU
SoC, CLKSRC_OF is selected by ARCH_MULTIPLATFORM and CLKSRC_MMIO is
selected by ARCH_MXC, it would not be a problem for MMU SOC_VF610. But I
guess we should try to define dependencies on the lowest level, so it is
probably a general fix?

--
Stefan

  reply	other threads:[~2014-10-13  9:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12 18:13 [RFC 0/7] ARM: vf610m4: Add Vybrid Cortex-M4 support Stefan Agner
2014-10-12 18:13 ` [RFC 1/7] ARM: vf610: add low level debug support for !MMU Stefan Agner
2014-10-12 18:48   ` Arnd Bergmann
2014-10-13  9:26     ` Stefan Agner
2014-10-12 18:13 ` [RFC 2/7] clocksource: add dependencies for Vybrid pit clocksource Stefan Agner
2014-10-12 18:18   ` Uwe Kleine-König
2014-10-13  9:46     ` Stefan Agner [this message]
2014-10-13 10:57       ` Uwe Kleine-König
2014-10-12 18:13 ` [RFC 3/7] ARM: vf610m4: add new machine and SoC for Vybrid on Cortex-M4 Stefan Agner
2014-10-12 18:51   ` Arnd Bergmann
2014-10-13 10:03     ` Stefan Agner
2014-10-13 10:57       ` Arnd Bergmann
2014-10-12 18:13 ` [RFC 4/7] ARM: dts: add support for Vybrid running " Stefan Agner
2014-10-12 18:56   ` Arnd Bergmann
2014-10-13 10:41     ` Stefan Agner
2014-10-13 10:32   ` Mark Rutland
2014-10-13 11:08     ` Stefan Agner
2014-10-13 11:24       ` Arnd Bergmann
2014-10-13 16:11         ` Stefan Agner
2014-10-13 19:54           ` Arnd Bergmann
2014-10-13 21:20             ` Stefan Agner
2014-10-14 10:01               ` Arnd Bergmann
2014-10-12 18:13 ` [RFC 5/7] irqchip: nvic: increase number of external interrupts to 112 Stefan Agner
2014-10-12 18:14 ` [RFC 6/7] ARM: vf610m4: HACK: get dtb pointer from SRC_GPR3 Stefan Agner
2014-10-12 19:00   ` Arnd Bergmann
2014-10-13 10:10     ` Stefan Agner
2014-10-12 18:14 ` [RFC 7/7] ARM: vf610m4: add defconfig for Linux on Vybrids Cortex-M4 Stefan Agner
2014-11-28 14:17 ` [RFC 0/7] ARM: vf610m4: Add Vybrid Cortex-M4 support Andreas Färber
2014-11-28 16:00   ` Stefan Agner

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=98ca2b7a76dc786a36cf6c4113ca751f@agner.ch \
    --to=stefan@agner$(echo .)ch \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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