From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762142AbdJRBbG (ORCPT ); Tue, 17 Oct 2017 21:31:06 -0400 Received: from mailout3.samsung.com ([203.254.224.33]:41231 "EHLO mailout3.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762121AbdJRBbE (ORCPT ); Tue, 17 Oct 2017 21:31:04 -0400 X-AuditID: b6c32a38-d71ff70000001124-ed-59e6aed5c65e MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset="utf-8" Message-id: <59E6AED6.70703@samsung.com> Date: Wed, 18 Oct 2017 10:31:02 +0900 From: Chanwoo Choi Organization: Samsung Electronics User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 To: myungjoo.ham@gmail.com Cc: Kyungmin Park , "Rafael J . Wysocki" , chanwoo@kernel.org, =?UTF-8?B?64yA7J246riw?= , LKML , Linux PM list Subject: Re: [PATCH v4 3/8] PM / devfreq: Use the available min/max frequency In-reply-to: X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNKsWRmVeSWpSXmKPExsWy7bCmnu7Vdc8iDZ5NUbWYeOMKi8Wk+xNY LM42vWG3uLxrDpvF594jjBbPN3WyWjxe8Zbdgd1j56y77B6L97xk8ti0qpPNo2/LKkaPz5vk AlijUm0yUhNTUosUUvOS81My89JtlbyD453jTc0MDHUNLS3MlRTyEnNTbZVcfAJ03TJzgM5Q UihLzCkFCgUkFhcr6dvZFOWXlqQqZOQXl9gqRRsaGukZGpjrGRkZ6ZkYx1oZmQKVJKRmnJi/ ibHgjkLFzc/rGRsYv0l2MXJySAiYSBy+uJapi5GLQ0hgB6NE84UORgjnO6PEvGtXWWCqTp+d zAaR2MAosWj9fEaQBK+AoMSPyfeAijg4mAXkJY5cygYJMwtoSrz4MokFov4eo8SZ2ZdZIOo1 JN7OecIIUs8ioCoxf7UeSJhNQEti/4sbbCA2v4CixNUfj8HGiwpESOyc/40dxBYRkJJ4+fEU 2KXMAr8YJR7/vgeWEBbwl1j4/AYriM0pECzx9P4jsMUSAmfYJB5cOcEG8YGLRNP248wQtrDE q+Nb2EGOkBCQlrh01Baivp1RYvOce1DNHYwS91c2skI0GEuc6mpkgniNT+Ld1x5WiGZeiY42 IQjTQ2L6GS+IakeJ/fMOsEI8P4dJ4uSeX+wTGOVmIYXXLER4zUIKrwWMzKsYxVILinPTU4sN C0z0ihNzi0vz0vWS83M3MYITnpbFDsY953wOMQpwMCrx8P5QfBYpxJpYVlyZe4hRgoNZSYT3 +FqgEG9KYmVValF+fFFpTmrxIUZTYHBPZJYSTc4HJuO8knhDE0sDEzMjYPKyNDRUEucVXX8t QkggPbEkNTs1tSC1CKaPiYNTqoGxkz8rPHwl94sP9c7pvYxhpdr30gxS24NZTzsU6S3Ztupf e+PUtz6Nuspi3Ic3znYXeV+45G20o16fVLguq8lumRZvD50A0z/H/l6qOhN2USiW9Zals9e2 CvHfbExJKzL9Oy5GyKlkaz1nSc5b9Yfta9qRftWIBVdaVz2/ZLH92rLuee7RG5RYijMSDbWY i4oTAUOrJxqOAwAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrNLMWRmVeSWpSXmKPExsVy+t9jQd2r655FGpxaLG4x8cYVFotJ9yew WJxtesNucXnXHDaLz71HGC2eb+pktXi84i27A7vHzll32T0W73nJ5LFpVSebR9+WVYwenzfJ BbBGcdmkpOZklqUW6dslcGWcmL+JseCOQsXNz+sZGxi/SXYxcnJICJhInD47ma2LkYtDSGAd o8T7eSuYQBK8AoISPybfY+li5OBgFpCXOHIpG8JUl5gyJRei/AGjxIUtDYwQ5RoSb+c8YQSp YRFQlZi/Wg8kzCagJbH/xQ02EJtfQFHi6o/HYCWiAhES3ScqQcIiAlISLz+eYgIZySzwi1Hi 8Z85YFuFBXwlbq8LgFg1j0ni+uG3YKs4BYIl3radZprAKDALyaGzEA6dhXDoAkbmVYySqQXF uem5xUYFhnmp5XrFibnFpXnpesn5uZsYgUG+7bBW3w7G+0viDzEKcDAq8fD+UHwWKcSaWFZc mXuIUYKDWUmE9/haoBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXHe23nHIoUE0hNLUrNTUwtSi2Cy TBycUg2M6+M1GV7vuTF38SETYcZ3jZ6vbt5Z1hNi1LL6wEbVAIFDlULt5ptOtqdoX8oqV8ju VAw8tsQlg/3OhXzTf8Zb15ir6jz8ki0+I/PrcZPXSquW/cgV8J7DvODfhf2T391u69dsLjfy 8fj9dtaS71Erw0wXPJvpcu3uSsarf2rd1ivwn9aRe+UwTYmlOCPRUIu5qDgRAHexzlJuAgAA X-CMS-MailID: 20171018013101epcas1p13a444a2f3b506a62e3e4db63dc8dda5e X-Msg-Generator: CA X-Sender-IP: 182.195.42.142 X-Local-Sender: =?UTF-8?B?7LWc7LCs7JqwG1RpemVuIFBsYXRmb3JtIExhYihTL1fshLw=?= =?UTF-8?B?7YSwKRvsgrzshLHsoITsnpAbU2VuaW9yIEVuZ2luZWVy?= X-Global-Sender: =?UTF-8?B?Q2hhbndvbyBDaG9pG1RpemVuIFBsYXRmb3JtIExhYi4bU2Ft?= =?UTF-8?B?c3VuZyBFbGVjdHJvbmljcxtTZW5pb3IgRW5naW5lZXI=?= X-Sender-Code: =?UTF-8?B?QzEwG1RFTEUbQzEwVjgxMTE=?= CMS-TYPE: 101P DLP-Filter: Pass X-CFilter-Loop: Reflected X-CMS-RootMailID: 20171013074833epcas1p433f03287f42a5b6dc16e796efa2a3bf3 X-RootMTR: 20171013074833epcas1p433f03287f42a5b6dc16e796efa2a3bf3 References: <1507880904-31956-1-git-send-email-cw00.choi@samsung.com> <1507880904-31956-4-git-send-email-cw00.choi@samsung.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 2017년 10월 17일 23:43, MyungJoo Ham wrote: > On Fri, Oct 13, 2017 at 4:48 PM, Chanwoo Choi wrote: >> The commit a76caf55e5b35 ("thermal: Add devfreq cooling") is able >> to disable OPP as a cooling device. In result, both update_devfreq() >> and {min|max}_freq_show() have to consider the 'opp->available' >> status of each OPP. >> >> So, this patch adds the 'scaling_{min|max}_freq' to struct devfreq >> in order to indicate the available mininum and maximum frequency >> by adjusting OPP interface such as dev_pm_opp_{disable|enable}(). >> The 'scaling_{min|max}_freq' are used for on both update_devfreq() >> and {min|max}_freq_show(). >> >> Signed-off-by: Chanwoo Choi >> --- >> drivers/devfreq/devfreq.c | 36 ++++++++++++++++++++++++++++-------- >> include/linux/devfreq.h | 4 ++++ >> 2 files changed, 32 insertions(+), 8 deletions(-) >> >> diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c >> index b6ba24e5db0d..9de013ffeb67 100644 >> --- a/drivers/devfreq/devfreq.c >> +++ b/drivers/devfreq/devfreq.c > [] >> @@ -494,6 +499,19 @@ static int devfreq_notifier_call(struct notifier_block *nb, unsigned long type, >> int ret; >> >> mutex_lock(&devfreq->lock); >> + >> + devfreq->scaling_min_freq = find_available_min_freq(devfreq); >> + if (!devfreq->scaling_min_freq) { >> + mutex_unlock(&devfreq->lock); >> + return -EINVAL; >> + } >> + >> + devfreq->scaling_max_freq = find_available_max_freq(devfreq); >> + if (!devfreq->max_freq) { > > 1. s/max_freq/scaling/max_freq/ ?? My mistake. The scaling_max_freq is right. I'll fix it. > > 2. what if thermal is not active or has never triggered any event and > the user has never stated max/min? (making scaling_*_freq zero) The devfreq-cooling.c of tmu uses the OPP interface and then OPP interface affect the scaling_min/max_freq of devfreq through dev_pm_opp_disable/enable(). So, even if 'thermal is not active or has never triggered any event', devfreq will use the OPP interface as a mandatory. In result, I think that devfreq should maintain the correct frequency of scaling_min/max_freq indicating the 'limit minimum/maximum frequency requested by OPP interface' instead of zero. So, I'll change the description of scaling_min/max_freq as following: (by devfreq-cooling -> by OPP interface) On v4: + * @scaling_min_freq: Limit minimum frequency requested by devfreq-cooling + * @scaling_max_freq: Limit maximum frequency requested by devfreq-cooling On v5: + * @scaling_min_freq: Limit minimum frequency requested by OPP interface + * @scaling_max_freq: Limit maximum frequency requested by OPP interface And, this patch showed the wrong value of min/max_freq_show() by my mistake. I showed the 'min/max_freq' directly through min/max_freq_show() without comparing with scaling_min/max_freq. So, I'll fix this issue as following: --------------- On v5: static ssize_t min_freq_show(struct device *dev, struct device_attribute *attr, char *buf) { - return sprintf(buf, "%lu\n", to_devfreq(dev)->min_freq); + struct devfreq *df = to_devfreq(dev); + + return sprintf(buf, "%lu\n", MAX(df->scaling_min_freq, df->min_freq)); } static ssize_t max_freq_store(struct device *dev, struct device_attribute *attr, @@ -1161,7 +1183,9 @@ static ssize_t max_freq_store(struct device *dev, struct device_attribute *attr, static ssize_t max_freq_show(struct device *dev, struct device_attribute *attr, char *buf) { - return sprintf(buf, "%lu\n", to_devfreq(dev)->max_freq); + struct devfreq *df = to_devfreq(dev); + + return sprintf(buf, "%lu\n", MIN(df->scaling_max_freq, df->max_freq)); --------------- > >> + mutex_unlock(&devfreq->lock); >> + return -EINVAL; >> + } >> + >> ret = update_devfreq(devfreq); >> mutex_unlock(&devfreq->lock); >> > > > -- Best Regards, Chanwoo Choi Samsung Electronics