linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antoine Tenart <antoine.tenart@free-electrons.com>
To: sebastian.hesselbarth@gmail.com
Cc: Antoine Tenart <antoine.tenart@free-electrons.com>,
	zmxu@marvell.com, jszhang@marvell.com,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/6] ARM: berlin: add cpufreq support
Date: Thu, 17 Sep 2015 12:14:59 +0200	[thread overview]
Message-ID: <1442484905-15656-1-git-send-email-antoine.tenart@free-electrons.com> (raw)

Hi,

This series adds the cpufreq support to the Berlin SoCs, using
cpufreq-dt.

First, the cpuclk clock is added to the BG2Q clock driver. This clock
has a divider fixed to 1, so we use a fixed factor clock here.

Then register a platform device for cpufreq-dt.

I also added the OPP table definition in the BG2Q, BG2 and BG2CD device
trees. When using a BG2Q, some bootloaders may update this table when
booting (mine doesn't).

Tested on a BG2Q DMP.

Thanks,

Antoine

Changes since v2:
	- rebased on top of v4.3-rc1

Changes since v1:
        - added the BG2 and BG2CD support
        - moved MAX_CLKS out of the Berlin clk driver
        - reordered the patches

Antoine Tenart (6):
  clk: berlin: move MAX_CLKS out of drivers/clk/berlin
  clk: berlin: add cpuclk
  ARM: berlin: dts: add the cpufreq-dt bindings on the BG2Q
  ARM: berlin: dts: add the cpufreq-dt bindings on the BG2
  ARM: berlin: dts: add the cpufreq-dt bindings on the BG2CD
  ARM: berlin: register cpufreq-dt

 arch/arm/boot/dts/berlin2.dtsi       | 10 ++++++++++
 arch/arm/boot/dts/berlin2cd.dtsi     |  8 ++++++++
 arch/arm/boot/dts/berlin2q.dtsi      | 11 +++++++++++
 arch/arm/mach-berlin/berlin.c        |  6 ++++++
 drivers/clk/berlin/bg2.c             |  1 -
 drivers/clk/berlin/bg2q.c            | 13 ++++++-------
 include/dt-bindings/clock/berlin2.h  |  2 ++
 include/dt-bindings/clock/berlin2q.h |  3 +++
 8 files changed, 46 insertions(+), 8 deletions(-)

-- 
2.5.2


             reply	other threads:[~2015-09-17 10:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 10:14 Antoine Tenart [this message]
2015-09-17 10:15 ` [PATCH v3 1/6] clk: berlin: move MAX_CLKS out of drivers/clk/berlin Antoine Tenart
2015-09-17 10:15 ` [PATCH v3 2/6] clk: berlin: add cpuclk Antoine Tenart
2015-09-17 10:15 ` [PATCH v3 3/6] ARM: berlin: dts: add the cpufreq-dt bindings on the BG2Q Antoine Tenart
2015-09-17 10:15 ` [PATCH v3 4/6] ARM: berlin: dts: add the cpufreq-dt bindings on the BG2 Antoine Tenart
2015-09-17 10:15 ` [PATCH v3 5/6] ARM: berlin: dts: add the cpufreq-dt bindings on the BG2CD Antoine Tenart
2015-09-17 10:15 ` [PATCH v3 6/6] ARM: berlin: register cpufreq-dt Antoine Tenart
2015-09-20 18:23 ` [PATCH v3 0/6] ARM: berlin: add cpufreq support Sebastian Hesselbarth

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=1442484905-15656-1-git-send-email-antoine.tenart@free-electrons.com \
    --to=antoine.tenart@free-electrons.com \
    --cc=jszhang@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=zmxu@marvell.com \
    /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).