From: Srinivas KANDAGATLA <srinivas.kandagatla@st.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-doc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org,
Rob Herring <rob.herring@calxeda.com>,
Stuart Menefy <stuart.menefy@st.com>,
John Stultz <john.stultz@linaro.org>,
Grant Likely <grant.likely@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v5] clocksource:arm_global_timer: Add ARM global timer support.
Date: Tue, 25 Jun 2013 09:40:20 +0100 [thread overview]
Message-ID: <51C95774.9060709@st.com> (raw)
In-Reply-To: <51C8C172.8020207@codeaurora.org>
Thankyou for the comments,
On 24/06/13 23:00, Stephen Boyd wrote:
> On 06/24/13 14:08, Srinivas KANDAGATLA wrote:
>> On 24/06/13 21:06, Stephen Boyd wrote:
>>> On 06/24/13 08:53, Srinivas KANDAGATLA wrote:
>
>
> I think the problem is your clockevent has no rating. Please give it a
> rating (300?) so that it prevents the dummy from taking over. You don't
> need to worry about disabling the local timer API, it will register a
> harmless clockevent with a low rating (100) that should be ignored.
>
I think I forgot to add rating in my last attempt to use cpu notifier.
With rating set to 300, the driver works fine with cpu notifiers.
Will send a new patch.
Thanks,
srini
next prev parent reply other threads:[~2013-06-25 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 15:53 [PATCH v5] clocksource:arm_global_timer: Add ARM global timer support Srinivas KANDAGATLA
2013-06-24 20:01 ` Thomas Gleixner
2013-06-24 21:10 ` Srinivas KANDAGATLA
2013-06-24 20:06 ` Stephen Boyd
2013-06-24 21:08 ` Srinivas KANDAGATLA
2013-06-24 22:00 ` Stephen Boyd
2013-06-25 8:40 ` Srinivas KANDAGATLA [this message]
2013-06-24 22:08 ` Stephen Boyd
2013-06-25 8:38 ` Srinivas KANDAGATLA
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=51C95774.9060709@st.com \
--to=srinivas.kandagatla@st.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=sboyd@codeaurora.org \
--cc=stuart.menefy@st.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
/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).