public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 05/05] sh: Let SH_TIMER_CMT select GENERIC_TIME
Date: Thu, 16 Apr 2009 05:23:41 +0000	[thread overview]
Message-ID: <20090416052341.GB26667@linux-sh.org> (raw)
In-Reply-To: <20090415105038.29940.67915.sendpatchset@rx1.opensource.se>

On Wed, Apr 15, 2009 at 07:50:38PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@igel.co.jp>
> 
> Let SH_TIMER_CMT select GENERIC_TIME. This since GENERIC_TIME is
> required to build the CMT driver. Without this patch the TMU driver
> must be enabled for the CMT driver to build.
> 
> Signed-off-by: Magnus Damm <damm@igel.co.jp>
> ---
> 
>  arch/sh/Kconfig |    1 +
>  1 file changed, 1 insertion(+)
> 
> --- 0001/arch/sh/Kconfig
> +++ work/arch/sh/Kconfig	2009-02-04 19:29:12.000000000 +0900
> @@ -431,6 +431,7 @@ config SH_CMT
>  config SH_TIMER_CMT
>  	bool "CMT clockevents driver"
>  	depends on SYS_SUPPORTS_CMT && !SH_CMT
> +	select GENERIC_TIME
>  	select GENERIC_CLOCKEVENTS
>  
We can't do this yet, as the mtu2 sys_timer code is not GENERIC_TIME
ready. So if one uses that in conjunction with SH_TIMER_CMT, it will blow
up. Once the early platform stuff is merged and we can use the new CMT
code for jiffies, then I will change the Kconfig bits around to prevent
any sys_timer drivers being enabled, and at that point this can be
applied.

      reply	other threads:[~2009-04-16  5:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 10:50 [PATCH 05/05] sh: Let SH_TIMER_CMT select GENERIC_TIME Magnus Damm
2009-04-16  5:23 ` Paul Mundt [this message]

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=20090416052341.GB26667@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@vger.kernel.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