LKML Archive on
help / color / mirror / Atom feed
From: Thomas Gleixner <>
To: Pavel Pisa <>
Cc: Ingo Molnar <>,,
	Sascha Hauer <>
Subject: Re: [PATCH query] arm: i.MX/MX1 clock event source
Date: Wed, 24 Jan 2007 12:37:06 +0100	[thread overview]
Message-ID: <1169638626.21181.170.camel@localhost.localdomain> (raw)
In-Reply-To: <>

On Wed, 2007-01-24 at 03:00 +0100, Pavel Pisa wrote:
> stays NULL after clock event registration. Interrupts
> runs, but my code doesnot call any function. The notification
> chain and clock events list seems to be filled correctly.
> I have added 
>         clockevent_imx.cpumask = cpumask_of_cpu(0);

Correct. I probably should disable the check for UP.

> to ensure that clock are not used for affinity
> mask reasons. I have tried even exchange clock 
> event forcibly at the end of clockevent_imx initialization.
> But it only resulted in asking timer to switch off
> into unused mode.
> I have added next hack into IRQ
>                                 write_seqlock(&xtime_lock);
>                                 timer_tick();
>                                 write_sequnlock(&xtime_lock);
> which stays enabled until imx_set_mode() is called first time,
> The system boots after this modification, but imx_set_mode()
> is never called and there is no switch to high resolution mode.

You should not set up the timer at all. The setup of the timer happens
from the registration. 

We need to know, why the timer is not picked from the tick code in the
first place and why set_mode() is not called.


  reply	other threads:[~2007-01-24 11:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21  0:01 Pavel Pisa
2007-01-22 19:59 ` Ingo Molnar
2007-01-23  2:52   ` Pavel Pisa
2007-01-24  2:00     ` Pavel Pisa
2007-01-24 11:37       ` Thomas Gleixner [this message]
2007-01-26 19:34         ` [PATCH updated] " Pavel Pisa

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1169638626.21181.170.camel@localhost.localdomain \ \ \ \ \ \
    --subject='Re: [PATCH query] arm: i.MX/MX1 clock event source' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).