linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep.KarkadaNagesha@arm.com (Sudeep KarkadaNagesha)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM/ARM64 architected timer updates for v3.12
Date: Fri, 30 Aug 2013 11:00:05 +0100	[thread overview]
Message-ID: <52206D25.6080808@arm.com> (raw)
In-Reply-To: <521FCC0A.80302@linaro.org>

Ccing Catalin,Russell

On 29/08/13 23:32, Daniel Lezcano wrote:
> On 08/29/2013 07:13 PM, Sudeep KarkadaNagesha wrote:
>> Hi Daniel,
>>
>> These are the ARM/ARM64 arch timer updates for v3.12.
>> I have re-based the changes on tip/timers/core as there are conflicts
>> with memory mapped arch_timers support queued recently.
>> Since this series adds CPU PM notifiers for arch_timers, it is required
>> to enable ARM bL cpuidle drivers(already queued for v3.12)
>>
>> Regards,
>> Sudeep
>>
>> The following changes since commit cfb6d656d569510ac9239583ce09e4c92ad54719:
>>
>>   Merge branch 'timers/clockevents-next' of
>> git://git.linaro.org/people/dlezcano/clockevents into timers/core
>> (2013-08-21 14:59:23 +0200)
>>
>> are available in the git repository at:
>>
>>
>>   git://linux-arm.org/linux-skn.git timer_evtstrm
>>
>> for you to fetch changes up to f74f198e540c160b1db9470b679dbeb72339829b:
>>
>>   drivers: clocksource: add CPU PM notifier for ARM architected timer
>> (2013-08-29 17:43:08 +0100)
> 
> 
> Hi Sudeep,
> 
> I need the acked-by from Olof or Kevin for the arch/arm[64] changes.
> 
Hi Daniel,

I think the changes are more generic to arm/arm64, rather not SoC
specific. Catalin has reviewed the series. I can check with Russell(for
arm) and Catalin(for arm64) for Acks.
I do understand that it may be late for v3.12

Regards,
Sudeep

> Thanks
>   -- Daniel
> 
>> ----------------------------------------------------------------
>> Sudeep KarkadaNagesha (4):
>>    ARM/ARM64: arch_timer: add macros for bits in control register
>>    ARM: arch_timer: add support to configure and enable event stream
>>    ARM64: arch_timer: add support to configure and enable event stream
>>    drivers: clocksource: add CPU PM notifier for ARM architected timer
>>
>> Will Deacon (1):
>>    drivers: clocksource: add support for ARM architected timer event stream
>> q
>>  arch/arm/include/asm/arch_timer.h    | 36 ++++++++++++++++---
>>  arch/arm/include/uapi/asm/hwcap.h    |  1 +
>>  arch/arm/kernel/setup.c              |  1 +
>>  arch/arm64/include/asm/arch_timer.h  | 42 ++++++++++++++++++---
>>  arch/arm64/include/asm/hwcap.h       | 11 +++---
>>  arch/arm64/include/uapi/asm/hwcap.h  |  1 +
>>  arch/arm64/kernel/setup.c            | 11 ++++++
>>  drivers/clocksource/Kconfig          | 15 ++++++++
>>  drivers/clocksource/arm_arch_timer.c | 49 +++++++++++++++++++++++++
>>  include/clocksource/arm_arch_timer.h | 10 +++++
>>  10 files changed, 161 insertions(+), 16 deletions(-)
>>
>>
>>
> 
> 

      parent reply	other threads:[~2013-08-30 10:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 17:13 [GIT PULL] ARM/ARM64 architected timer updates for v3.12 Sudeep KarkadaNagesha
2013-08-29 22:32 ` Daniel Lezcano
2013-08-29 23:00   ` Olof Johansson
2013-08-30 10:00   ` Sudeep KarkadaNagesha [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=52206D25.6080808@arm.com \
    --to=sudeep.karkadanagesha@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).