From: Venkappa Mala <venkappa.m@samsung.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 5/5] drivers: clocksource: add CPU PM notifier for ARM architected timer
Date: Thu, 19 Feb 2015 16:03:01 +0000 (UTC) [thread overview]
Message-ID: <loom.20150219T164240-40@post.gmane.org> (raw)
In-Reply-To: <CAPKp9uZj3tUVKf=mMRU+5hS0Ut31rrG5NHzo8=6Tw1ar+3+vZw@mail.gmail.com>
Sudeep Holla <sudeep.holla <at> arm.com> writes:
> Are you targeting this on ARM64 platform ?
> If so, I don't understand how is the arch timer context is lost as the
cpuidle
> driver is not merge to 3.10 stable kernel ?
For time being, you can ignore about ARM64.
let's have a discussion on ARMv7 first.
I have enabled generic arch arm timer in kernel 3.10 frame work to
validate vDSO (ARM: vDSO -> still, it did not merge in the vanilla kernel)
on ARMv7. As part of this, i have noticed that the contex lost is
happening. After pulling the patch, the issue is resolved, timer/counter
is up and running. In future, someone wants to enable arch timer in 3.10,
then I anticipate that the patch needs to be merged in vanilla kernel.
correct me if I am wrong.
BR,
Venkappa
prev parent reply other threads:[~2015-02-19 16:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 10:44 [PATCH v5 0/5] ARM/ARM64 architected timer updates Sudeep KarkadaNagesha
2013-08-28 10:44 ` [PATCH v5 1/5] ARM/ARM64: arch_timer: add macros for bits in control register Sudeep KarkadaNagesha
2013-08-28 10:44 ` [PATCH v5 2/5] ARM: arch_timer: add support to configure and enable event stream Sudeep KarkadaNagesha
2013-08-29 11:24 ` Catalin Marinas
2013-08-28 10:44 ` [PATCH v5 3/5] ARM64: " Sudeep KarkadaNagesha
2013-08-29 11:22 ` Catalin Marinas
2013-08-28 10:44 ` [PATCH v5 4/5] drivers: clocksource: add support for ARM architected timer " Sudeep KarkadaNagesha
2013-08-29 11:19 ` Catalin Marinas
2013-08-28 10:44 ` [PATCH v5 5/5] drivers: clocksource: add CPU PM notifier for ARM architected timer Sudeep KarkadaNagesha
2013-08-28 10:55 ` Sudeep KarkadaNagesha
2015-02-19 13:03 ` Venkappa Mala
2015-02-19 14:16 ` Sudeep Holla
2015-02-19 16:03 ` Venkappa Mala [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=loom.20150219T164240-40@post.gmane.org \
--to=venkappa.m@samsung.com \
--cc=linux-kernel@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
Powered by JetHome