Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp105746pxm; Tue, 22 Feb 2022 18:00:20 -0800 (PST) X-Google-Smtp-Source: ABdhPJwYM4Q/QR/Ir2uD0i6wUw1trBEpSO4m3ToeXUbwQp0YSn52nfU2wODJOQ6y+IWEinW9NKmw X-Received: by 2002:a17:907:3115:b0:6b5:6ebd:d785 with SMTP id wl21-20020a170907311500b006b56ebdd785mr21604800ejb.592.1645581619832; Tue, 22 Feb 2022 18:00:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645581619; cv=none; d=google.com; s=arc-20160816; b=FPFRuyqmWZqzvqm0bp4L4ddUNO6UkmUMloJalg5+y+nErmFVrOxzCS4WY3fBZYeSrx w0xp0LE9o3tRBP0a3yl1cGq5yHFvw0Y+gyUWsRO12bGfManguX0RpwD1orLblpJJXqxn DBMEtrkU+PCS9afVKeavuDi9czmJLUfmh7hkLM8zChLUkysX2VxahPWuE2CWJyWvydNv v6NSczpxKZz1bga8jR43P6q3uLVwf+BPoLetOOzvgF74cidEKRXgMZh9Ohoaolqc0ZRi SWY0Mrjt+olj7LJVGrcMRQiVl/EmXR+7nYxgolfKl72hlulEbiNGTTm+NOcYoMPJmngU LTrw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=k4nfTmVrUlOu+T9aryMcgGSOPsQxaYdJvdIROnK5XAo=; b=bwityaPnm/cGe910K97cC/E5xf9Y8tBe7KU03ybLqeVe+JURNZujujtwbgLX4OlpvU 8ZYh1Qp9jefxpVUh6NVgRsEbh22o7VaOjSG5bYXl/7zACggf80xTc88rujUBWHrXGeKL PGYOxStmiYG8s07nDZRRojC6bRuAjd6SH7nEusiv79TjJ3HVVRxz3Vz/urAVamVv0lHO I2HZliKJXzW6WZVR5HaBjQJDnwuBo9Q5s3BaQYM01BJTP52mLg7A3BbeQCRsBFUcmqlx hQbuNGPBbekT8b/5DOML63rshUhaS8X5iUTlOcb6Q3CWhVi0NK8t0KOXmPOMQDZztTHi GFVA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 11si11289165eje.377.2022.02.22.17.59.56; Tue, 22 Feb 2022 18:00:19 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234998AbiBVSc1 (ORCPT + 99 others); Tue, 22 Feb 2022 13:32:27 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51932 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234810AbiBVSc0 (ORCPT ); Tue, 22 Feb 2022 13:32:26 -0500 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id AE9D53465D; Tue, 22 Feb 2022 10:31:59 -0800 (PST) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 0C847106F; Tue, 22 Feb 2022 10:31:59 -0800 (PST) Received: from [10.57.9.152] (unknown [10.57.9.152]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 1BFED3F66F; Tue, 22 Feb 2022 10:31:56 -0800 (PST) Message-ID: <27df4e4f-b6d7-9a58-f2dd-d6afa748e217@arm.com> Date: Tue, 22 Feb 2022 18:31:55 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [PATCH 1/2] thermal: cooling: Check Energy Model type in cpufreq_cooling and devfreq_cooling Content-Language: en-US To: Daniel Lezcano Cc: amit.kachhap@gmail.com, viresh.kumar@linaro.org, rafael@kernel.org, amitk@kernel.org, rui.zhang@intel.com, dietmar.eggemann@arm.com, Pierre.Gondois@arm.com, Matthias Kaehlcke , Doug Anderson , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org References: <20220207073036.14901-1-lukasz.luba@arm.com> <20220207073036.14901-2-lukasz.luba@arm.com> <4e090ffe-c19b-8e2c-0396-72dc33361f35@arm.com> <211a3606-2f4c-227b-33aa-177ef68a49a3@arm.com> <3d1719ca-d4a4-f904-e284-b857414669ba@linaro.org> From: Lukasz Luba In-Reply-To: <3d1719ca-d4a4-f904-e284-b857414669ba@linaro.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/22/22 18:12, Daniel Lezcano wrote: > > Hi Lukasz, > > I don't think it makes sense to remove the support of the energy model > if the units are abstracts. > > IIUC, regarding your previous answer, we don't really know what will do > the SoC vendor with these numbers and likely they will provide > consistent abstract values which won't prevent a correct behavior. > > What would be the benefit of giving inconsistent abstract values which > will be unusable except of giving a broken energy model? The power values in the EM which has abstract scale, would make sense to EAS, but not for IPA or DTPM. Those platforms which want to enable EAS, but don't need IPA, would register such '' EM. > > Your proposed changes would be acceptable if the energy model has a > broken flag IMO That is doable. I can add that flag, so we can call it 'artificial' EM (when this new flag is set). Let me craft the RFC patch with this new flag proposal then. Do you agree? Can I also add you as 'Suggested-by'? Thank you for coming back to me with the comments.