public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] ARM: zynq: cpufreq support
Date: Fri, 28 Feb 2014 07:58:11 +0100	[thread overview]
Message-ID: <53103383.8090604@linaro.org> (raw)
In-Reply-To: <3402bb7c-3dec-403a-9356-65af803e1b0a@AM1EHSMHS017.ehs.local>

On 02/27/2014 06:52 PM, S?ren Brinkmann wrote:
> Hi Daniel, Michal,
>
> On Wed, 2014-02-19 at 03:14PM -0800, Soren Brinkmann wrote:
>> Hi,
>>
>> another iteration of this series. The patches are the same as in v3, but
>> the series shrank a bit. I rebased this series on tip/timers/core, hence
>> the two patches for the clockevent core fell out, since Thomas already
>> applied those.
>> Additionally I removed the patch 'clocksource/cadence_ttc: Use only one
>> counter'. Thomas brought up some questions regarding that patch which
>> need to be investigated. Since it is not required for the rest of this
>> series, I just dropped it for now.
>>
>> 	Thanks,
>> 	S?ren
>>
>> Soren Brinkmann (4):
>>    clocksource/cadence_ttc: Call clockevents_update_freq() with IRQs
>>      enabled
>>    clocksource/cadence_ttc: Overhaul clocksource frequency adjustment
>>    arm: zynq: Don't use arm_global_timer with cpufreq
>>    arm: zynq: Add support for cpufreq
>
> Any comments? I think most of these should be pretty straight forward
> and it would be nice to get some ACKs - or tell me what's wrong. :)
> 'clocksource/cadence_ttc: Overhaul clocksource frequency adjustment'
> might deserve a more thorough review.

Hi Soren,

I will be at Linaro Connect. Give me a couple of days, I will review 
them again.

Thanks
   -- Daniel


-- 
  <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  reply	other threads:[~2014-02-28  6:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 23:14 [PATCH v4 0/4] ARM: zynq: cpufreq support Soren Brinkmann
2014-02-19 23:14 ` [PATCH v4 1/4] clocksource/cadence_ttc: Call clockevents_update_freq() with IRQs enabled Soren Brinkmann
2014-02-19 23:14 ` [PATCH v4 2/4] clocksource/cadence_ttc: Overhaul clocksource frequency adjustment Soren Brinkmann
2014-02-19 23:14 ` [PATCH v4 3/4] arm: zynq: Don't use arm_global_timer with cpufreq Soren Brinkmann
2014-02-19 23:14 ` [PATCH v4 4/4] arm: zynq: Add support for cpufreq Soren Brinkmann
2014-02-27 17:52 ` [PATCH v4 0/4] ARM: zynq: cpufreq support Sören Brinkmann
2014-02-28  6:58   ` Daniel Lezcano [this message]
     [not found] ` <20140227175217.GW13293@xsjandreislx>
2014-02-28  6:26   ` Michal Simek

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=53103383.8090604@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --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