linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: SoC changes for v3.17 (round 3)
Date: Wed, 23 Jul 2014 22:31:41 +0200	[thread overview]
Message-ID: <201407232231.41787.arnd@arndb.de> (raw)
In-Reply-To: <20140722205706.GA23220@titan.lakedaemon.net>

On Tuesday 22 July 2014, Jason Cooper wrote:
> All,
> 
> Here's the cpufreq changes I mentioned over the weekend.  It's been in
> -next for a while.  Once I get the new version of cpuidle from ThomasP,
> I'll push that as quickly as possible.

Just for my information, is this coordinated with the cpufreq maintainers?
I remember being asked to ensure all cpufreq/cpuidle stuff has an Ack
from them, even stuff that doesn't touch drivers/cpufreq at all.

The contents look good to me. I can merge them if there are no objections
from Viresh, feel free to send the next batch already without waiting
for me to pull.

> As usual (do I need to type this each time any more? :) ), this is an
> incremental pull request from tags/mvebu-soc-3.17-2 up to
> tags/mvebu-soc-3.17-3 on the mvebu/soc branch.

It certainly helps me to have this information, but you can write it
more briefly, e.g. "based on tags/mvebu-soc-3.17-2".

	Arnd
 
> The following changes since commit ba364fc752daeded072a5ef31e43b84cb1f9e5fd:
> 
>   ARM: Kirkwood: Remove mach-kirkwood (2014-07-13 22:13:39 +0000)
> 
> are available in the git repository at:
> 
>   git://git.infradead.org/linux-mvebu.git tags/mvebu-soc-3.17-3
> 
> for you to fetch changes up to ba3ec5780bba27819bbc4f669e6c77418a00f14b:
> 
>   Merge branch 'mvebu/soc-cpufreq' into mvebu/soc (2014-07-22 20:46:48 +0000)
> 
> ----------------------------------------------------------------
> 
> mvebu SoC changes for v3.17 (round 3)
> 
>  - mvebu:
>     - Add cpufreq support for Armada XP
> 
> ----------------------------------------------------------------
> Jason Cooper (1):
>       Merge branch 'mvebu/soc-cpufreq' into mvebu/soc
> 
> Thomas Petazzoni (3):
>       ARM: mvebu: ensure CPU clocks are enabled
>       ARM: mvebu: extend PMSU code to support dynamic frequency scaling
>       clk: mvebu: extend clk-cpu for dynamic frequency scaling
> 
>  .../devicetree/bindings/clock/mvebu-cpu-clock.txt  |   5 +-
>  arch/arm/mach-mvebu/platsmp.c                      |   1 +
>  arch/arm/mach-mvebu/pmsu.c                         | 162 +++++++++++++++++++++
>  drivers/clk/mvebu/clk-cpu.c                        |  80 +++++++++-
>  include/linux/mvebu-pmsu.h                         |  20 +++
>  5 files changed, 261 insertions(+), 7 deletions(-)
>  create mode 100644 include/linux/mvebu-pmsu.h
> 

  reply	other threads:[~2014-07-23 20:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 20:57 [GIT PULL] ARM: mvebu: SoC changes for v3.17 (round 3) Jason Cooper
2014-07-23 20:31 ` Arnd Bergmann [this message]
2014-07-23 23:41   ` Jason Cooper
2014-07-23 23:45     ` Olof Johansson
2014-07-24  0:08       ` Jason Cooper

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=201407232231.41787.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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).