From: Chanwoo Choi <cwchoi00@gmail.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: "myungjoo.ham@samsung.com" <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/8] PM / devfreq: Update the devfreq and devfreq-event device
Date: Tue, 3 Jan 2017 20:57:36 +0900 [thread overview]
Message-ID: <CAGTfZH0CEZguE1otuCSEOtuU+ed_cy_pAE59q02baA-p74K2Fg@mail.gmail.com> (raw)
In-Reply-To: <1482926212-19223-1-git-send-email-cw00.choi@samsung.com>
Dear Myungjoo,
Thanks for your review for patch1/2/3/4/5.
But, patch6/7/8 are not yet reviewed. The patch4 should be resent
according to your comment.
So, Could you please review these patch6/7/8?
2016-12-28 20:56 GMT+09:00 Chanwoo Choi <cw00.choi@samsung.com>:
> This patches update the devfreq and devfreq-event device. I add the summary
> of each patch as following.
>
> - Patch1 is documented for bus frequency scaling of Exynos5433's VDD_INT.
> The related-to patches[1] were merged by Exynos SoC maintainer.
> - Patch2 uses the regmap interface instead of raw_read/write function.
> - Patch3/4 print the useful log for exynos-bus.c and exynos-ppmu.c driver.
> - Patch5 fixes the checkpatch warning of devfreq.c.
> - Patch6/7 modify the name of sysfs entry for devfreq/devfreq-event device
> - Patch8 fixes the wrong description of govenro_userspace.c.
>
> Changes from v1:
> - Rebase these patches on v4.10-rc1.
> - Include the separate patch[2] in these patches.
>
> [1] https://lkml.org/lkml/2016/12/7/846
> - [PATCH v2 0/5] arm64: dts: Enable bus frequency scaling on Exynos5433-based TM2 board
> [2] https://lkml.org/lkml/2016/12/16/7
> - [PATCH] PM / devfreq: Fix the wrong description for userspace governor
>
>
> Depends on:
> - These patches depend on both v4.10-rc1 and patches[3].
>
> [3] https://lkml.org/lkml/2016/12/28/91
> - [PATCH v2 0/3] PM / devfreq: Fix the bug and add reviewer for devfreq support
>
> Chanwoo Choi (8):
> PM / devfreq: exynos-bus: Add the detailed correlation for Exynos5433
> PM / devfreq: exynos-ppmu: Use the regmap interface to handle the registers
> PM / devfreq: exynos-bus: Print the real clock rate of bus
> PM / devfreq: exynos-ppmu: Show the registred device for ppmu device
> PM / devfreq: Fix the checkpatch warnings
> PM / devfreq: Modify the device name as devfreq[X] for sysfs
> PM / devfreq: Simplify the sysfs name of devfreq-event device
> PM / devfreq: Fix the wrong description for userspace governor
>
> .../devicetree/bindings/devfreq/exynos-bus.txt | 14 +
> drivers/devfreq/devfreq-event.c | 2 +-
> drivers/devfreq/devfreq.c | 17 +-
> drivers/devfreq/event/exynos-ppmu.c | 331 +++++++++++++++------
> drivers/devfreq/exynos-bus.c | 8 +-
> drivers/devfreq/governor_userspace.c | 3 +-
> 6 files changed, 271 insertions(+), 104 deletions(-)
>
> --
> 1.9.1
>
--
Best Regards,
Chanwoo Choi
prev parent reply other threads:[~2017-01-03 11:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161228115654epcas1p1dbe96f4f79ee451bd8eac960f1ea80c5@epcas1p1.samsung.com>
2016-12-28 11:56 ` [PATCH v2 0/8] PM / devfreq: Update the devfreq and devfreq-event device Chanwoo Choi
[not found] ` <CGME20161228115654epcas1p1752ca85fc1cb3757a9b460584abcb7cc@epcas1p1.samsung.com>
2016-12-28 11:56 ` [PATCH v2 2/8] PM / devfreq: exynos-ppmu: Use the regmap interface to handle the registers Chanwoo Choi
2016-12-30 10:25 ` MyungJoo Ham
[not found] ` <CGME20161228115654epcas1p159c2daa73a697956085cb4b9fcd46e7d@epcas1p1.samsung.com>
2016-12-28 11:56 ` [PATCH v2 3/8] PM / devfreq: exynos-bus: Print the real clock rate of bus Chanwoo Choi
2016-12-30 10:33 ` MyungJoo Ham
[not found] ` <CGME20161228115654epcas1p1fcd9be231f97e6782e06d75ace95a9ba@epcas1p1.samsung.com>
2016-12-28 11:56 ` [PATCH v2 4/8] PM / devfreq: exynos-ppmu: Show the registred device for ppmu device Chanwoo Choi
2016-12-30 10:35 ` MyungJoo Ham
2016-12-30 12:00 ` Chanwoo Choi
[not found] ` <CGME20161228115654epcas1p1fd3636bca6d05331fcd9b629a8aeb921@epcas1p1.samsung.com>
2016-12-28 11:56 ` [PATCH v2 5/8] PM / devfreq: Fix the checkpatch warnings Chanwoo Choi
2016-12-30 10:38 ` MyungJoo Ham
[not found] ` <CGME20161228115654epcas1p17e52fdc6039cb252d130218325cf1186@epcas1p1.samsung.com>
2016-12-28 11:56 ` [PATCH v2 6/8] PM / devfreq: Modify the device name as devfreq[X] for sysfs Chanwoo Choi
[not found] ` <CGME20161228115654epcas1p1a55cebc1270e16435d13e6d4d2197b74@epcas1p1.samsung.com>
2016-12-28 11:56 ` [PATCH v2 7/8] PM / devfreq: Simplify the sysfs name of devfreq-event device Chanwoo Choi
[not found] ` <CGME20161228115654epcas1p1ac0c112753ca3dd694f604b84239bd18@epcas1p1.samsung.com>
2016-12-28 11:56 ` [PATCH v2 8/8] PM / devfreq: Fix the wrong description for userspace governor Chanwoo Choi
[not found] ` <CGME20161228115654epcas1p13fa3cb3615ddf89ebdf747c72b60d809@epcas1p1.samsung.com>
2016-12-28 11:56 ` [PATCH v2 1/8] PM / devfreq: exynos-bus: Add the detailed correlation for Exynos5433 Chanwoo Choi
2016-12-30 1:02 ` MyungJoo Ham
2017-01-03 11:57 ` Chanwoo Choi [this message]
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=CAGTfZH0CEZguE1otuCSEOtuU+ed_cy_pAE59q02baA-p74K2Fg@mail.gmail.com \
--to=cwchoi00@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.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).