Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp6424672yba; Tue, 14 May 2019 07:21:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqwsvOPO0lg6vJ1BQPe6ml/ldo3HhWlTIarFrbJPkZwAkLwF9LFnObRNxQFfSNk7vLmpAHo0 X-Received: by 2002:a63:4a66:: with SMTP id j38mr19322778pgl.199.1557843704807; Tue, 14 May 2019 07:21:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557843704; cv=none; d=google.com; s=arc-20160816; b=xs4KyArfEdoJNkJT5QlKlFyT026aT8yfje+6P/Yt5l7ktCHMtWjW1hJs/FvIRzM9YE ugpqLr15/0Ji5kx9rFG+E1sqKAZ4Aw4gThKa+xLbcaJ+aOwE+OrdINfJXQdfAyXQFAFK fSI0njblozDnhAtZXucm8unvBi0BJ7y+bfXAIJCJ4rtZQT//OOfUFgPRRbtwzTUf7LFv rDIeK8P99+nI2Mj84fN/EUF18LCgTTYuoGJSTpctjTNtDmwu1PwX4aoLh3LInG65LGvW jdeGIZ0r5sxXoumuIf0wJk3jnAX7yQ6D2VtfKl9/DuTleFSY9dE7VQAQ1y8KP2JaSL2I jHkw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=ITS3zBwB+n/SCtTVGR5gpCm7E8hsahuYP/jkp4b4pGM=; b=BBC00COPRLNfSIG2pb6RiBR0JQ4jHcOhelItjoeBa1s0PxkrnorOpkRZMTZGuyMv7C 1q4ooUwtoA38gblKIb7IQThuzzpC5lezdg4fj8mNzHXzPlX4TI2+A1Z3la6JsLaoAp6I 8GHoprIWEvG+TRlCQlJitvpo42iSrqwv4/nmm7+dtZMJq+fHa8qZPzF/i/O5+oHCO8sU 861atYwHksFciChysHXCMhFb8eyDmmwUmNfMCg26NxOn1JzoI2Q0by9gAb8WqOFRVPe1 vakvmO6YyLGw6Pe4uu7df00BGQ2MQLSDREh9YsqtEv5LYhxE3BE1zxSxGJDH9+3okrRQ 2+zg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p7si20187842pgi.276.2019.05.14.07.21.28; Tue, 14 May 2019 07:21:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726195AbfENOT4 (ORCPT + 99 others); Tue, 14 May 2019 10:19:56 -0400 Received: from foss.arm.com ([217.140.101.70]:56820 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725854AbfENOT4 (ORCPT ); Tue, 14 May 2019 10:19:56 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id AE7A7374; Tue, 14 May 2019 07:19:55 -0700 (PDT) Received: from queper01-lin (queper01-lin.cambridge.arm.com [10.1.195.48]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 2E98B3F703; Tue, 14 May 2019 07:19:53 -0700 (PDT) Date: Tue, 14 May 2019 15:19:51 +0100 From: Quentin Perret To: Eduardo Valentin Cc: rui.zhang@intel.com, javi.merino@kernel.org, viresh.kumar@linaro.org, amit.kachhap@gmail.com, rjw@rjwysocki.net, will.deacon@arm.com, catalin.marinas@arm.com, daniel.lezcano@linaro.org, dietmar.eggemann@arm.com, ionela.voinescu@arm.com, mka@chromium.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v3 3/3] thermal: cpu_cooling: Migrate to using the EM framework Message-ID: <20190514141949.352gjengdyg67w7s@queper01-lin> References: <20190503094409.3499-1-quentin.perret@arm.com> <20190503094409.3499-4-quentin.perret@arm.com> <20190514034056.GA5621@localhost.localdomain> <20190514071506.ykjg67elsydaehlz@queper01-ThinkPad-T460s> <20190514141736.GB16968@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190514141736.GB16968@localhost.localdomain> User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 14 May 2019 at 07:17:37 (-0700), Eduardo Valentin wrote: > Hey Quentin, > > On Tue, May 14, 2019 at 08:15:08AM +0100, Quentin Perret wrote: > > Hi Eduardo, > > > > On Monday 13 May 2019 at 20:40:59 (-0700), Eduardo Valentin wrote: > > > On Fri, May 03, 2019 at 10:44:09AM +0100, Quentin Perret wrote: > > > > The newly introduced Energy Model framework manages power cost tables in > > > > a generic way. Moreover, it supports a several types of models since the > > > > tables can come from DT or firmware (through SCMI) for example. On the > > > > other hand, the cpu_cooling subsystem manages its own power cost tables > > > > using only DT data. > > > > > > > > In order to avoid the duplication of data in the kernel, and in order to > > > > enable IPA with EMs coming from more than just DT, remove the private > > > > tables from cpu_cooling.c and migrate it to using the centralized EM > > > > framework. > > > > > > > > The case where the thermal subsystem is used without an Energy Model > > > > (cpufreq_cooling_ops) is handled by looking directly at CPUFreq's > > > > frequency table which is already a dependency for cpu_cooling.c anyway. > > > > Since the thermal framework expects the cooling states in a particular > > > > order, bail out whenever the CPUFreq table is unsorted, since that is > > > > fairly uncommon in general, and there are currently no users of > > > > cpu_cooling for this use-case. > > > > > > Will this break DT in any way? After this change, are the existing DTs > > > still compatible with this cpu cooling? > > > > Yes, all existing DTs stay compatible with this CPU cooling. The EM can > > still be built using the 'dynamic-power-coefficient' DT property thanks > > to the recently introduced dev_pm_opp_of_register_em() helper, see > > a4f342b9607d ("PM / OPP: Introduce a power estimation helper"). And all > > relevant cpufreq drivers have already been updated to use that function. > > I see.. > > > > > So, this patch should cause no functional change for all existing users. > > It's really just plumbing. I can probably explain that better in this > > commit message rather than the cover letter if you feel it is necessary. > > > > Yes I would prefer if this info goes into the commit message. No problem, will do in v4. Thanks, Quentin