All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Govindraj Raja <govindraj.raja@imgtec.com>,
	linux-kernel@vger.kernel.org, linux-mips@linux-mips.org,
	devicetree@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	Andrew Bresticker <abrestic@chromium.org>,
	James Hartley <James.Hartley@imgtec.com>,
	Damien Horsley <Damien.Horsley@imgtec.com>,
	James Hogan <James.Hogan@imgtec.com>,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	Ezequiel Garcia <ezequiel.garcia@imgtec.com>
Subject: Re: [PATCH v4 0/7] Clocksource changes for Pistachio CPUFreq.
Date: Tue, 04 Aug 2015 11:48:35 +0200	[thread overview]
Message-ID: <55C08A73.60505@linaro.org> (raw)
In-Reply-To: <20150728095128.GA23771@linux-mips.org>

On 07/28/2015 11:51 AM, Ralf Baechle wrote:
> Daniel,
>
> On Mon, Jul 27, 2015 at 03:00:11PM +0100, Govindraj Raja wrote:
>
>> From: Ezequiel Garcia <ezequiel.garcia@imgtec.com>
>>
>> The purpose of this patchset is to support CPUFreq on Pistachio SoC.
>> However, given Pistachio uses the MIPS GIC clocksource and clockevent drivers
>> (clocked from the CPU), adding CPUFreq support needs some work.
>>
>> This patchset changes the MIPS GIC clockevent driver to update the frequency of
>> the per-cpu clockevents using a clock notifier.
>>
>> Then, we add a clocksource driver for IMG Pistachio SoC, based on the
>> general purpose timers. The SoC only provides four timers, so we can't
>> use them to implement the four clockevents and the clocksource.
>>
>> However, we can use one of these timers to provide a clocksource and a
>> sched clock. Given the general purpose timers are clocked from the peripheral
>> system clock tree, they are not affected by CPU rate changes.
>>
>> Patches 1 to 3 are just style cleaning and preparation work.
>> Patch 4 adds the clockevent frequency update.
>> Patches 5 and 6 add the new clocksource driver.
>> Patch 7 introduces an option to enable the timer based clocksource on Pistachio.
>
> if you're happy with this series feel free to add my ack to patch 7/7
> which is the only one that touches arch/mips.
>
> Alternatively I can carry this in the MIPS tree which would have tbe
> benefit of better testing.

Ok, go ahead.

For the series 1-4: Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>



-- 
  <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:[~2015-08-04  9:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 14:00 [PATCH v4 0/7] Clocksource changes for Pistachio CPUFreq Govindraj Raja
2015-07-27 14:00 ` Govindraj Raja
2015-07-27 14:00 ` [PATCH v4 1/7] clocksource: mips-gic: Enable the clock before using it Govindraj Raja
2015-07-27 14:00   ` Govindraj Raja
2015-08-04  9:23   ` Daniel Lezcano
2015-07-27 14:00 ` [PATCH v4 2/7] clocksource: mips-gic: Add missing error returns checks Govindraj Raja
2015-07-27 14:00   ` Govindraj Raja
2015-07-27 14:00   ` Govindraj Raja
2015-07-27 14:00 ` [PATCH v4 3/7] clocksource: mips-gic: Split clocksource and clockevent initialization Govindraj Raja
2015-07-27 14:00   ` Govindraj Raja
2015-07-27 14:00 ` [PATCH v4 4/7] clocksource: mips-gic: Update clockevent frequency on clock rate changes Govindraj Raja
2015-07-27 14:00   ` Govindraj Raja
2015-07-28  9:51 ` [PATCH v4 0/7] Clocksource changes for Pistachio CPUFreq Ralf Baechle
2015-07-28  9:51   ` Ralf Baechle
2015-07-28  9:51   ` Ralf Baechle
2015-08-04  9:48   ` Daniel Lezcano [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=55C08A73.60505@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=Damien.Horsley@imgtec.com \
    --cc=James.Hartley@imgtec.com \
    --cc=James.Hogan@imgtec.com \
    --cc=abrestic@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel.garcia@imgtec.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=govindraj.raja@imgtec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.