From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: rjw@rjwysocki.net
Cc: 최찬우 <cw00.choi@samsung.com>,
linux-pm@vger.kernel.org, rafael.j.wysocki@intel.com,
크쉬시토프 <k.kozlowski@samsung.com>
Subject: [PULL Request] Devfreq for next (4.7)
Date: Tue, 03 May 2016 02:56:36 +0000 (GMT) [thread overview]
Message-ID: <1799748329.331081462244196087.JavaMail.weblogic@ep2mlwas05b> (raw)
Dear Rafael,
Here goes a pull request targetting Linux 4.7 (next)
Cheers,
MyungJoo
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The following changes since commit 04974df8049fc4240d22759a91e035082ccd18b4:
Linux 4.6-rc6 (2016-05-01 15:52:31 -0700)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/mzx/devfreq.git tags/PR_4.7_20160503
for you to fetch changes up to 83cb0e4d837af4348cc218638e9d6daddd21d260:
PM / devfreq: style/typo fixes (2016-05-03 11:22:10 +0900)
- ----------------------------------------------------------------
Pull Request for PM/Linux, targetting Linux-next (4.7)
Updates:
- - Passive governor: for SoC subsystems that may either
have an independent voltage rail or have a parent subsystem
or collegue subsystem sharing a voltage rail, when there
is a parent of a collegue that is going to be the owner
of the voltage rail, the dependent subsystem may use the
passive governor.
- - Consolidated exynos bus/mem-if driver: now we have a single
driver that supports (almost) all Exynos SoC's bus/mem-if subsystems.
- - New devfreq drivers included: Exynos NoC probe
- ----------------------------------------------------------------
Chanwoo Choi (13):
PM / devfreq: exynos: Add generic exynos bus frequency driver
PM / devfreq: exynos: Add documentation for generic exynos bus frequency driver
PM / devfreq: Add devfreq_get_devfreq_by_phandle()
PM / devfreq: Add new DEVFREQ_TRANSITION_NOTIFIER notifier
PM / devfreq: Add new passive governor
PM / devfreq: exynos: Add support of bus frequency of sub-blocks using passive governor
PM / devfreq: exynos: Update documentation for bus devices using passive governor
PM / devfreq: exynos: Add the detailed correlation between sub-blocks and power line
PM / devfreq: exynos: Remove unused exynos4/5 busfreq driver
MAINTAINERS: Add samsung bus frequency driver entry
PM / devfreq: event: Add new Exynos NoC probe driver
PM / devfreq: event: Find the instance of devfreq-event device by using phandle
PM / devfreq: exynos: Add the detailed correlation for Exynos5422 bus
MyungJoo Ham (1):
PM / devfreq: style/typo fixes
.../bindings/devfreq/event/exynos-nocp.txt | 26 +
.../devicetree/bindings/devfreq/exynos-bus.txt | 409 ++++++++
MAINTAINERS | 9 +
drivers/devfreq/Kconfig | 36 +-
drivers/devfreq/Makefile | 4 +-
drivers/devfreq/devfreq-event.c | 5 +
drivers/devfreq/devfreq.c | 207 +++-
drivers/devfreq/event/Kconfig | 8 +
drivers/devfreq/event/Makefile | 2 +
drivers/devfreq/event/exynos-nocp.c | 304 ++++++
drivers/devfreq/event/exynos-nocp.h | 78 ++
drivers/devfreq/exynos-bus.c | 570 +++++++++++
drivers/devfreq/exynos/Makefile | 3 -
drivers/devfreq/exynos/exynos4_bus.c | 1055 --------------------
drivers/devfreq/exynos/exynos4_bus.h | 110 --
drivers/devfreq/exynos/exynos5_bus.c | 431 --------
drivers/devfreq/exynos/exynos_ppmu.c | 119 ---
drivers/devfreq/exynos/exynos_ppmu.h | 86 --
drivers/devfreq/governor_passive.c | 205 ++++
include/linux/devfreq.h | 99 ++
20 files changed, 1942 insertions(+), 1824 deletions(-)
create mode 100644 Documentation/devicetree/bindings/devfreq/event/exynos-nocp.txt
create mode 100644 Documentation/devicetree/bindings/devfreq/exynos-bus.txt
create mode 100644 drivers/devfreq/event/exynos-nocp.c
create mode 100644 drivers/devfreq/event/exynos-nocp.h
create mode 100644 drivers/devfreq/exynos-bus.c
delete mode 100644 drivers/devfreq/exynos/Makefile
delete mode 100644 drivers/devfreq/exynos/exynos4_bus.c
delete mode 100644 drivers/devfreq/exynos/exynos4_bus.h
delete mode 100644 drivers/devfreq/exynos/exynos5_bus.c
delete mode 100644 drivers/devfreq/exynos/exynos_ppmu.c
delete mode 100644 drivers/devfreq/exynos/exynos_ppmu.h
create mode 100644 drivers/devfreq/governor_passive.c
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJXKBH2AAoJEBOhurvWBoCKGv8P/1iG1JlzvUy7SrhysGm7btWv
ps9HOrHuhav35YZwtSGezrC9/yFZ7eyR7mwwXBPyY7bIEkCC2Ybax/GY8p+pQrQu
smHogoOSh+BSOqBvnv6DFnFjlKaNTC3pWznkuelPAzK1NemYrOevNnBUIJkluwRe
p/U3aN7234Y+Ciw+uyVdCuz5jiOuYrtg23JORhf1muzVjS/WQY8aUQS2xm2D9Y26
6jIMvghl5epSZgJ2Fpkv6BH3KCIvPxJqthfadiJnU/hT51vwGrUTMsQ3180Iweuo
q2zpAqamHKwAU4NrcLn6ifSSpdTEAR3R/lsVgzfxGLCGbfXtkA3FT1ePissCUPVl
Cm4YB8+jSWmHCWRVD2zMFEkRzYAdl4uXwZCnOlS04Opr3myQ7xeArP5FAOnLhpiJ
E6RGukHL1IZU1BFQfuVXjexh8nc8HtR02Vyey4UB8qBOsif5bqVXWAu3XAoWmYvu
D6JPCNZzljHyYRBkYoiEmlU8HTc2EkRlgdbbf54Q/holBeh2TEczZXm9v1cvhjhy
CCsS2fhBnOezWGJqxMMzNytu692D4YdJeIU89SQvVvuo8A4T2JsId8UXBxj7Tajh
0jg5EO9UQ/yx6Sw2mf2GAqFqItJErYPB0+hzT8bOVv6N/PLqQbUxPfLjRI9u9jBZ
HQQwpdnc9IJTQyzMRLZu
=OTWS
-----END PGP SIGNATURE-----
next reply other threads:[~2016-05-03 2:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 2:56 MyungJoo Ham [this message]
2016-05-04 20:56 ` [PULL Request] Devfreq for next (4.7) 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=1799748329.331081462244196087.JavaMail.weblogic@ep2mlwas05b \
--to=myungjoo.ham@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
/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).