public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Mayer <code@mmayer.net>
To: Ralf Baechle <ralf@linux-mips.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>
Cc: Markus Mayer <mmayer@broadcom.com>,
	MIPS Linux Kernel List <linux-mips@linux-mips.org>,
	Power Management List <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/4] cpufreq: bmips-cpufreq: Add CPUfreq driver for Broadcom's BMIPS SoCs
Date: Tue,  7 Feb 2017 13:58:52 -0800	[thread overview]
Message-ID: <20170207215856.8999-1-code@mmayer.net> (raw)

From: Markus Mayer <mmayer@broadcom.com>

Sorry for the new iteration. I found two more simplifications, so here
goes. Only patch 3/4 has changed.

This series adds a CPUfreq driver for the BMIPS SoCs. In the first
iteration only BMIPS5xxx SoCs are supported.

This series is based on pm/linux-next.

The series is also available at
https://github.com/mmayer/linux/tree/bmips-cpufreq-v3

Changes since v2:
  - remove local variables freq and cpu_freq in bmips_cpufreq_get()
  - assign global variable "priv" directly in bmips_cpufreq_probe()
    rather than setting driver_data and then retrieving it from there
    to set priv in bmips_cpufreq_init()

Changes since v1:
  - based on pm/linux-next rather than 4.10-rc1
  - sanitized bmips_stb_defconfig by running "make savedefconfig"; this
    also lead to an additional patch (1/4), which contains non-CPUfreq
    related updates that "make savedefconfig" performed
  - use gobal variable to store driver data rather than policy->driver_data
  - got rid of some code as a result of using said global variable
  - kzalloc -> kmalloc
  - removed policy->freq_table = NULL;

Markus Mayer (4):
  MIPS: BMIPS: Update defconfig
  BMIPS: Enable prerequisites for CPUfreq in MIPS Kconfig.
  cpufreq: bmips-cpufreq: CPUfreq driver for Broadcom's BMIPS SoCs
  MIPS: BMIPS: enable CPUfreq

 arch/mips/Kconfig                     |   2 +
 arch/mips/configs/bmips_stb_defconfig |  16 +--
 drivers/cpufreq/Kconfig               |  10 ++
 drivers/cpufreq/Makefile              |   1 +
 drivers/cpufreq/bmips-cpufreq.c       | 188 ++++++++++++++++++++++++++++++++++
 5 files changed, 211 insertions(+), 6 deletions(-)
 create mode 100644 drivers/cpufreq/bmips-cpufreq.c

-- 
2.7.4

             reply	other threads:[~2017-02-07 21:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 21:58 Markus Mayer [this message]
2017-02-07 21:58 ` [PATCH v3 1/4] MIPS: BMIPS: Update defconfig Markus Mayer
2017-02-07 21:58 ` [PATCH v3 2/4] BMIPS: Enable prerequisites for CPUfreq in MIPS Kconfig Markus Mayer
2017-02-08  2:07   ` Florian Fainelli
2017-02-07 21:58 ` [PATCH v3 3/4] cpufreq: bmips-cpufreq: CPUfreq driver for Broadcom's BMIPS SoCs Markus Mayer
2017-02-08  2:07   ` Florian Fainelli
2017-02-08  3:31   ` Viresh Kumar
2017-02-07 21:58 ` [PATCH v3 4/4] MIPS: BMIPS: enable CPUfreq Markus Mayer

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=20170207215856.8999-1-code@mmayer.net \
    --to=code@mmayer.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mmayer@broadcom.com \
    --cc=ralf@linux-mips.org \
    --cc=rjw@rjwysocki.net \
    --cc=viresh.kumar@linaro.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