Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752152AbdI0IJc convert rfc822-to-8bit (ORCPT ); Wed, 27 Sep 2017 04:09:32 -0400 Received: from mailout1.samsung.com ([203.254.224.24]:12098 "EHLO mailout1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751830AbdI0IJY (ORCPT ); Wed, 27 Sep 2017 04:09:24 -0400 X-AuditID: b6c32a38-d89ff70000001124-d9-59cb5cb268d9 Mime-Version: 1.0 Subject: RE: Re: [PATCH v2 0/8] PM / devfreq: Use OPP interface to handle the frequency Reply-To: myungjoo.ham@samsung.com From: MyungJoo Ham To: Chanwoo Choi , Kyungmin Park CC: "rafael.j.wysocki@intel.com" , "chanwoo@kernel.org" , Inki Dae , "linux-pm@vger.kernel.org" , "linux-kernel@vger.kernel.org" X-Priority: 3 X-Content-Kind-Code: NORMAL In-Reply-To: <59CAFEA7.10007@samsung.com> X-Drm-Type: N,general X-EPLocale: ko_KR.EUC-KR X-EPWebmail-Msg-Type: personal X-Msg-Generator: Mail X-Msg-Type: PERSONAL X-Reply-Demand: N Illegal-Object: Syntax error in X-Sender: address found on vger.kernel.org: X-Sender: =?utf-8?B?U2Ftc3VuZyBFbGVjdHJvbmljcxtBcnRpZmljaWFsIEludA==?= ^-Extraneous program text X-Sender-IP: 10.113.73.204 X-Local-Sender: =?UTF-8?B?7ZWo66qF7KO8G0FydGlmaWNpYWwgSW50ZWxsaWdlbmNlIDNMYWIoUy9X?= =?UTF-8?B?7IS87YSwKRvsgrzshLHsoITsnpAbUHJpbmNpcGFsIEVuZ2lu?= =?UTF-8?B?ZWVy?= X-Global-Sender: =?UTF-8?B?TXl1bmdKb28gSGFtG0FydGlmaWNpYWwgSW50ZWxsaWdlbmNlIDNMYWIu?= =?UTF-8?B?G1NhbXN1bmcgRWxlY3Ryb25pY3MbUHJpbmNpcGFsIEVuZ2lu?= =?UTF-8?B?ZWVy?= X-Sender-Code: =?UTF-8?B?QzEwGxtDMTBWODI5MQ==?= Message-ID: <20170927080922epcms1p3c8f87f8f55d753f57afe053d5750ebfc@epcms1p3> Date: Wed, 27 Sep 2017 08:09:22 +0000 X-CMS-MailID: 20170927080922epcms1p3c8f87f8f55d753f57afe053d5750ebfc Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="utf-8" X-MTR: 20170927080922epcms1p3c8f87f8f55d753f57afe053d5750ebfc CMS-TYPE: 101P X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupik+LIzCtJLcpLzFFi42LZdlhTT3dTzOlIg38dshYTb1xhsbj+5Tmr xaT7E1gszja9Ybe4vGsOm8Xn3iOMFo9XvGV3YPdYvOclk8emVZ1sHn1bVjF6fN4kF8ASlWqT kZqYklqkkJqXnJ+SmZduq+QdHO8cb2pmYKhraGlhrqSQl5ibaqvk4hOg65aZA3SBkkJZYk4p UCggsbhYSd/Opii/tCRVISO/uMRWKdrQ0EjP0MBcz8jISM/EONbKyBSoJCE1Y+bf9ewFj8Ur bux/ydbA2C7WxcjBISFgIrH/oXgXIxeHkMAORonTD9awgMR5BQQl/u4Q7mLk5BAWiJTYt/MU I4gtJKAk0XBzHzNEXF+i48E2sDibgK7E1g13WUBsEYFQid0L+phBZjILtDJJtD15DFYkIcAr MaP9KQuELS2xfflWsDingKbEmsZdrBBxUYmbq9+yQ9gSEndeX2CCsOUkpn1dwwxT8/7YfKiZ IhKt985CxQUlHvzczQiyWEKglVHizpZnUIOkJG4tvsYEkVjGKLH48lN2CGc5o0T7ko1skKDQ l9i53RmkgVfAV2LJ9MdsIDaLgKrExp4vUFe4SLyesANsG7OAtsSyha+ZQVqZgT5Yv0sfosRW ovdSIxtECZ/Eu689rDDP75j3BGqMmsSh3UvYJzAqz0KE9SwkQ2chDF3AyLyKUSy1oDg3PbXY sMBErzgxt7g0L10vOT93EyM4HWpZ7GDcc87nEKMAB6MSDy9DyKlIIdbEsuLK3EOMEhzMSiK8 u0JPRwrxpiRWVqUW5ccXleakFh9iNAX6bSKzlGhyPjBV55XEG5pYGpiYGQGTnKWhoZI4r+j6 axFCAumJJanZqakFqUUwfUwcnFINjE2fHm0MVJknUKIQxXn9WoCu9us3m6Oyfr5Qnvto63Yn 950NWU08yz1ZXoUaFLp7hzcIn51hu4YvYvXnO0mJG0oqdlwwS12wLP1OXq7sp1X727c+n3Hu mFkAu8me2VU/n8yb1c1/otZ0kXHAk4luXeEnNe6H9ksuKdlut77i2SrDXCPeuZ8dGZVYijMS DbWYi4oTAUYK+7KdAwAA DLP-Filter: Pass X-CFilter-Loop: Reflected X-CMS-RootMailID: 20170921003355epcas1p1d1bbb04ff7a7c46946f62a91883bd6a6 X-RootMTR: 20170921003355epcas1p1d1bbb04ff7a7c46946f62a91883bd6a6 References: <59CAFEA7.10007@samsung.com> <1505954032-3327-1-git-send-email-cw00.choi@samsung.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2273 Lines: 85 > 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.