public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: rafael.j.wysocki@intel.com, linux-pm@vger.kernel.org
Cc: 최찬우 <cw00.choi@samsung.com>,
	"Javier Martinez Canillas" <j.canillas@partner.samsung.com>,
	"myungjoo.ham@gmail.com" <myungjoo.ham@gmail.com>
Subject: [PULL REQUEST] PM / devfreq, for Next-RC (fix, drv update)
Date: Mon, 03 Aug 2015 06:32:12 +0000 (GMT)	[thread overview]
Message-ID: <569864407.347861438583532089.JavaMail.weblogic@epmlwas06d> (raw)

Dear Rafael,

Here goes a pull request from devfreq:
1. Added PPMUv2 hardware support (for recent Exynos series)
2. Corrected documentation


Cheers,
MyungJoo
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The following changes since commit 74d33293e467df61de1b1d8b2fbe29e550dec33b:

  Linux 4.2-rc5 (2015-08-02 18:34:55 -0700)

are available in the git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/mzx/devfreq.git tags/pull_req_20150803

for you to fetch changes up to a622789aeebdeaa52d68bbc3930edbc3e820b54a:

  PM / devfreq: exynos-ppmu: Update documentation to support PPMUv2 (2015-08-03 14:33:52 +0900)

- ----------------------------------------------------------------
Pull Request of Devfreq Tree to Rafael from MyungJoo

- - Device driver update to support additional hardare
- - Documentation error fix

- ----------------------------------------------------------------
Chanwoo Choi (2):
      PM / devfreq: exynos-ppmu: Add the support of PPMUv2 for Exynos5433
      PM / devfreq: exynos-ppmu: Update documentation to support PPMUv2

Javier Martinez Canillas (1):
      PM / devfreq: event: Remove incorrect property in exynos-ppmu DT binding

 .../bindings/devfreq/event/exynos-ppmu.txt         |  43 +++++-
 drivers/devfreq/event/exynos-ppmu.c                | 170 ++++++++++++++++++++-
 drivers/devfreq/event/exynos-ppmu.h                |  70 +++++++++
 3 files changed, 273 insertions(+), 10 deletions(-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJVvwnMAAoJEBOhurvWBoCKfW4QAKuUatQl4gE3XIAs1Uhkz6LQ
U4HotOgXSFbeHhj+7Q2YLv1dE8R7l0CXxWkkg6j+/aiy2kdnshUNk07zx3asDLva
gAwb1RhKGRCGDa73QL7nf4ZlJuZvkpsYfyir7k0WpGKmL4793FbtxmaXSlvWWidg
U2F0OX+P+QkgwDKhW/nnyKcyi2mKyBeX+fkP3G3Z1AGI2fMaGAvBQBTAN7DlAKOG
pSeSpZSx+DJUAb5/WxbL/n3JyXUwuaIP4AXRiGz5JxiAULvMqaf0s9YwbQrWFDyN
nXp/OaMdqgJzJVz3tpNZGACuIpFmlFaJaWE6JXr7Avn7erqQ2eAckZrQbamqzXAh
47WDafgR9ChS5jaVz1r+JeOna0J9BJ5QKgviPAa+Qv5dFpQ/844fIpmGmMgYCDFz
EDY81KZ2RKfR1kwUs74zcfFFNTZwWP7pTJYdTtzNWYz8ZQTcszy36EDRBFV8+wNn
SDXdGdUlmsjPdcQ2hV+rU3mxDvcUHzP6ylR9XNUFo0hbGc01v1tf58u4Plg11O9q
vaRk3MwvGn9ahjLBvnAu8zH+kHGyI1YVMAa/HEMK0fr9RkGqDHgsIxDk8uL8zDKD
9x84m9FFS+ZYkHbAjlYVhggiWibTz9EXtCRIZCm9wzXrbkZDxkLshvPa1P0uBq+J
y6IMEl3eTm6Av2bYBGbZ
=8NFn
-----END PGP SIGNATURE-----

             reply	other threads:[~2015-08-03  6:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03  6:32 MyungJoo Ham [this message]
2015-08-08  1:42 ` [PULL REQUEST] PM / devfreq, for Next-RC (fix, drv update) Rafael J. Wysocki

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=569864407.347861438583532089.JavaMail.weblogic@epmlwas06d \
    --to=myungjoo.ham@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=j.canillas@partner.samsung.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=myungjoo.ham@gmail.com \
    --cc=rafael.j.wysocki@intel.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