Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp1346232pxu; Fri, 16 Oct 2020 09:40:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxO3oAGM1F66T67zFpNfsR/tVSkZp3GoVEKVgv4bBBT1JzKeVDuvqy5ijJhTrwY5ZW3POm6 X-Received: by 2002:aa7:d690:: with SMTP id d16mr4999852edr.301.1602866455175; Fri, 16 Oct 2020 09:40:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602866455; cv=none; d=google.com; s=arc-20160816; b=KYn6oUdtQ8Sfgvk7dLQiW9VJC3DRgr2NBrCEKck6ga8w2fI17CheUUk1cvpmvFUqI0 ix33IbhRhsp3+k1QDqBCF9I4AyOwtTvbUYP65W4HwunYBRMshYKpjnnaLr7KU1AOW0Rz svoZ4tdlfDtCYIwvwf8h9mFkskwOGZvZvSmG+P9lLwYWMRZoicSQgcn6U6u6BeqXzBeQ eVnWL08Vdr7t8BC1wQk4kuFlhlMg37l7sWt4zmPdWRMEN8v96uyj5y/F7VSfyen9vrSs sIi+SwSaX8QTDLeRMT7HST+yLlz3vHetW0ckVo6IRXOnmH9XO2FxGOjN39Y07FMimpVC WlvA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=idIwMLR1qbs0LEcD4O/aA7HLr22tz18ZNCJ0k8fk7cI=; b=MGUkbAhVAV8VtaH60fjtgaInay2I/sZCaWff0u1w3Ov6ySPg63RyB9LlOAzNw2HMQp N0G7vJHhjJFbTb+FpgTpF2HRFx5QGarorAMqdK1t1aOqPEQ75fdio0Ggqmlh4CsjX5PR x+V4ufr6UXBqrQDXuKLchkiz16sd0q1+noMteh1EJd/Nhzb/X8S/7pBXbt8RryHh+dpm XlaosYg8LSpPilNpoWHDKcsXiR1EdnEmi4YrUPP4nd3/Pbp4vxUPDnumulX2i5pho6qp KMpCGZENhqBu5T77BOUH7uoiQ5hmHRfDq12fUVz7KDHXxYKGSBmVIS/XFD2vGj7okn0T vruQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=bfcdoIjs; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id oi22si2301078ejb.466.2020.10.16.09.40.31; Fri, 16 Oct 2020 09:40:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=bfcdoIjs; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2409124AbgJPQCZ (ORCPT + 99 others); Fri, 16 Oct 2020 12:02:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40556 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2409115AbgJPQCZ (ORCPT ); Fri, 16 Oct 2020 12:02:25 -0400 Received: from mail-wr1-x444.google.com (mail-wr1-x444.google.com [IPv6:2a00:1450:4864:20::444]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E299DC0613D4 for ; Fri, 16 Oct 2020 09:02:24 -0700 (PDT) Received: by mail-wr1-x444.google.com with SMTP id e18so3475524wrw.9 for ; Fri, 16 Oct 2020 09:02:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=idIwMLR1qbs0LEcD4O/aA7HLr22tz18ZNCJ0k8fk7cI=; b=bfcdoIjsQPz/8DQCpMyYBVd2UI3qSwKRY7v0yRNoQQEj+Rp6gz/TJ+c+2aWwlGHNVl tiWyM8kv8AOh7Ry003DOQGVEY/Yo37LIfjtqubjeH+3GIc7jpULAg9u9A04CLk6Gu0jw /yHdR+t2GMgvN4HgERBfhetl6TIGtenJyPCUVu9f0A5KjcDVAt1VGQuBWexBUxlScauj qXh81fyybu0RrScobfpBu4N+/1SeZ+vk0sL9lFOyJAAxEPH/RrUItlQpfY+BqoIuODn9 3iiy7tMPTXq85miUzLQmeHsOmh1kCps1DU5tNZfoEk77LDH1+enI9uxbUIpTWvRPCf5j qz4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=idIwMLR1qbs0LEcD4O/aA7HLr22tz18ZNCJ0k8fk7cI=; b=n/HvhoZg7iujtlvzlvoogTykVizlU2xgMdSPAGAZ04Gc1rlZUznqUN+fpKUvckQkOf hBKABLyE2QH/EPYwkgWk7WQRzewYFIUqB4vlHujCGDzl+jYVI1iVup+QDf5VQ62trArA gbKWozlO/NjFLsMPIc3A2BFHuZnpUzr/iBOr2ziv3J3Id8jwnSI2TMIGENmzf4E9FruD XiaFjU49HLkUwUzzSepdfzXps2dSUsXM6FCj+RhZvILXxjcJgP3aBL0tdeRoWeUBDoBF GxGiZITUc6WlYhKoHfxj48s9WKKiKMiAMYrQhJbHtQ64j5ZTDAjUF6QCKLRBZ6V/002s g02g== X-Gm-Message-State: AOAM533viPPhjwyAfMeENC7G6Xb5rXSCdRyk2gHNYcbmCBAslRcsv3CA O25lQ4kX9djbHPrUqn59gnbIOjn/u898iA== X-Received: by 2002:adf:f54c:: with SMTP id j12mr4751369wrp.413.1602864143339; Fri, 16 Oct 2020 09:02:23 -0700 (PDT) Received: from google.com ([2a00:79e0:d:110:f693:9fff:fef4:a7ef]) by smtp.gmail.com with ESMTPSA id p9sm3193871wmm.4.2020.10.16.09.02.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 16 Oct 2020 09:02:21 -0700 (PDT) Date: Fri, 16 Oct 2020 17:02:18 +0100 From: Quentin Perret To: Lukasz Luba Cc: Daniel Lezcano , "Rafael J. Wysocki" , "Rafael J. Wysocki" , Linux Kernel Mailing List , Linux PM , "open list:DOCUMENTATION" , "devicetree@vger.kernel.org" , Rob Herring , Amit Kucheria , Jonathan Corbet , Dietmar Eggemann , Doug Anderson , Matthias Kaehlcke , "Nayak, Rajendra" Subject: Re: [PATCH v2 0/3] Clarify abstract scale usage for power values in Energy Model, EAS and IPA Message-ID: <20201016160218.GC2426638@google.com> References: <3e3dd42c-48ac-7267-45c5-ca88205611bd@arm.com> <00ceec64-3273-bb4a-6f38-22de8d877ab5@linaro.org> <20201016121844.GA2420691@google.com> <20201016130905.GA2426638@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday 16 Oct 2020 at 15:42:57 (+0100), Lukasz Luba wrote: > Do you mean a new entry in DT which will be always below > 'dynamic-power-coefficient' and/or 'sustainable-power' saying the unit > of above value? Yes, something like that. > There was discussion with Rob (and Doug) about this. I got the > impression he was against any new DT stuff [1]. > We don't have to, I think we all agree that DT will only support mW. Right, I agree this is a 'nice-to-have'. > I have agreed to this idea having a 'flag' inside EM [2], which > indicates the mW or bogoWatts. It could be set via API: > em_dev_register_perf_domain() and this new last argument. > > I can write that patch. There is only two usage (3rd is on LKML) of > that function. The DT way, which is via: > dev_pm_opp_of_register_em() will always set 'true'; > Driver direct calls of em_dev_register_perf_domain(), will have to > set appropriate value ('true' or 'false'). The EM struct em_perf_domain > will have the new bool field set based on that. > Is it make sense? I had something more complicated in mind, where units are arbitrary ('milliwats', 'scmi-bogowatts', ...) as that would help if units can be specified in the DT too, but if we don't care about that then yes I suppose a boolean flag should do. Thanks! Quentin