From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: Chanwoo Choi <cw00.choi@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Cc: "rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"chanwoo@kernel.org" <chanwoo@kernel.org>,
Inki Dae <inki.dae@samsung.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Re: [PATCH v2 0/8] PM / devfreq: Use OPP interface to handle the frequency
Date: Wed, 27 Sep 2017 08:09:22 +0000 [thread overview]
Message-ID: <20170927080922epcms1p3c8f87f8f55d753f57afe053d5750ebfc@epcms1p3> (raw)
In-Reply-To: <59CAFEA7.10007@samsung.com>
> Hi Myungjoo,
>
> Could you please review this patchset?
I ignored your v2 patchset because of the follow-up message:
| Re: [PATCH v2 8/8] PM / devfreq: exynos-bus: Register cooling device
|
| Dear all,
|
| Please ignore this patch. It has some problem.
| I'll fix and resend this patch on v2.
I thought you'd send another series with [PATCH v3 x/8]...
(I've just noticed that [PATCH v2.1] was sent yesterday.
Is the patchsetv2 ready with the replacement of 8th commit?)
Cheers,
MyungJoo
ps. you know I'm going to be away for a long vacation
starting this week.
I can't gurantee that I'll see all of the set before the vacation.
>
> On 2017년 09월 21일 09:33, Chanwoo Choi wrote:
> > These patches makes the devfreq to use the OPP interface and clean-up codes.
> > - patch 1~5 are related to the OPP interfaces.
> > - patch 6 removes the unneeded code.
> > - patch 7 clean-up for the governor name.
> > - patch 8 registers the cooling device for exynos-bus.
> >
> > [Detaild Descripion]
> > The commit a76caf55e5b3 ("thermal: Add devfreq cooling") provides
> > the devfreq cooling device by using the OPP interface such as
> > dev_pm_opp_disable() and dev_pm_opp_enable(). It means that
> > the OPP interface is able to change the available status of the frequency.
> >
> > Firstly, the existing devfreq doesn't use the OPP interface when showing
> > the minimum and maximum frequency through the following sysfs nodes:
> > It shows the wrong frequency value because min_freq/max_freq don't
> > consider the frequency status by handling OPP interface
> > (opp_dev_pm_opp_{disable|add}()). So, these patches fix this issue.
> > - /sys/class/devfreq/devfreqX/min_freq
> > - /sys/class/devfreq/devfreqX/max_freq
> >
> > Second, the 'available_frequencies' should show the all supported frequencis
> > even if the specific frequency is not available. It doesn't matter whether
> > frequneyc is available or not. Because the role of 'available_frequencies'
> > shows the all frequencies. Also, these patches fix this issue.
> > - /sys/class/devfreq/devfreqX/available_frequencies
> >
> > Third, update_devfreq() get the available next frequency by using
> > the devfreq_recommended_opp() in order to consider the disabled OPP.
next prev parent reply other threads:[~2017-09-27 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170921003355epcas1p1d1bbb04ff7a7c46946f62a91883bd6a6@epcas1p1.samsung.com>
2017-09-21 0:33 ` Chanwoo Choi
[not found] ` <CGME20170921003355epcas1p42e0547938d45c32c3064895140bf5848@epcas1p4.samsung.com>
2017-09-21 0:33 ` [PATCH v2 1/8] PM / devfreq: Set min/max_freq when adding the devfreq device Chanwoo Choi
[not found] ` <CGME20170921003355epcas1p4ecc54d2b7437b4e0d052d9b99647930e@epcas1p4.samsung.com>
2017-09-21 0:33 ` [PATCH v2 2/8] Revert "PM / devfreq: Add show_one macro to delete the duplicate code" Chanwoo Choi
[not found] ` <CGME20170921003355epcas1p24e2126b498dedf4c1112bac783de187b@epcas1p2.samsung.com>
2017-09-21 0:33 ` [PATCH v2 3/8] PM / devfreq: Show the available min/max frequency through sysfs node Chanwoo Choi
[not found] ` <CGME20170921003356epcas1p4c6e4da1fab6f56468ecca9e5889faa43@epcas1p4.samsung.com>
2017-09-21 0:33 ` [PATCH v2 4/8] PM / devfreq: Show the all available frequencies Chanwoo Choi
[not found] ` <CGME20170921003356epcas1p3de34905f87bca5760f80d196a004e1a0@epcas1p3.samsung.com>
2017-09-21 0:33 ` [PATCH v2 5/8] PM / devfreq: Get the available next frequency on update_devfreq() Chanwoo Choi
[not found] ` <CGME20170921003356epcas1p246204a12c12e4c9ed94771dc25ce143d@epcas1p2.samsung.com>
2017-09-21 0:33 ` [PATCH v2 6/8] PM / devfreq: Remove unneeded conditional statement Chanwoo Choi
[not found] ` <CGME20170921003356epcas1p20d38fddcbcf1534de97af75345927f7a@epcas1p2.samsung.com>
2017-09-21 0:33 ` [PATCH v2 7/8] PM / devfreq: Define the constant governor name Chanwoo Choi
[not found] ` <CGME20170921003356epcas1p34bf88ccd1b9630577a83f14f0c291b1d@epcas1p3.samsung.com>
2017-09-21 0:33 ` [PATCH v2 8/8] PM / devfreq: exynos-bus: Register cooling device Chanwoo Choi
2017-09-21 4:57 ` Chanwoo Choi
[not found] ` <CGME20170926023151epcas1p41f999f2804facb4548b2d42ac3a00601@epcas1p4.samsung.com>
2017-09-26 2:31 ` [PATCH v2.1] " Chanwoo Choi
2017-09-27 1:28 ` [PATCH v2 0/8] PM / devfreq: Use OPP interface to handle the frequency Chanwoo Choi
[not found] ` <CGME20170921003355epcas1p1d1bbb04ff7a7c46946f62a91883bd6a6@epcms1p3>
2017-09-27 8:09 ` MyungJoo Ham [this message]
2017-09-27 8:15 ` Chanwoo Choi
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=20170927080922epcms1p3c8f87f8f55d753f57afe053d5750ebfc@epcms1p3 \
--to=myungjoo.ham@samsung.com \
--cc=chanwoo@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=inki.dae@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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
all inboxes | Powered by JetHome®