Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp1378301pxm; Thu, 24 Feb 2022 01:48:03 -0800 (PST) X-Google-Smtp-Source: ABdhPJwpgW5tc8aHGVaR5vkzSzALRfVn8ZhdiL4QH1jizjDveesr9U+NQNGp6+SXvmNNYo1QepCo X-Received: by 2002:a63:a50d:0:b0:373:4c33:1292 with SMTP id n13-20020a63a50d000000b003734c331292mr1664817pgf.286.1645696082980; Thu, 24 Feb 2022 01:48:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645696082; cv=none; d=google.com; s=arc-20160816; b=dkGtGC9kYcZe6yBj8z2JmosdJEvFvcdKPh1YUtznXRmsff3IplYy0w9FpzsfZYCl17 rNuy+FbIAwsq0P5fi9mSBJplBHu/cLsiYDhMxDnGCgzo9i7i+dMlIO5JXCR4U7NzjSCF 6WyepV/vwfBVjK+Mfefoxuc9v1nCXG5NaIGAYCfcxocyErIZbms7G57YtA1TSn2c9Xfi lv7ZMA6lnCrfgD8LvxvvVUNQcXHS3DZuFrVhY0LZNLyTKTYNjhAO00XD4tMAMlNDJ1hv ksCnJXpalRTg98UaPGIfvhetibGq7k0mOstKpaHt16FrIcI1WNDTVa0psrYVVnFK0yvU XLqw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=kpeZOLAjOWDOxOLAZwon9tgkbygh+pggRkOmi8tbYh0=; b=AkJWlfbmTpq1cg+X9KIuH1ZR63VWw0d0So5kN18Q1Gcj1ctvX7eYFX19wkppJOm2zr +sTePSDj8310C4riDk1xi5lYid1P8AWFspKsDagS1+LDLGV81HBxOXi8xceoRNsLZIP/ c2x0dSUTX29TZMsNfIMXC9Dy5OugrNfa3Jkn6XOK3ab1fF6uQlSMGXfbQKgXKjwi1ZXE nwKJpkX9S1F0EEdH72WmkI91/ZrvdrSRbFcM9NQW/fVTA69Dv5SE2SewchPqNkPjiqp4 vdL2KAJRRrQHQZ2wUaZZrp/62nh7A/rARzCzN0ugo9p0yxnOJ8vQwJCJPkknRkJbKZFm slQQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=FaH9oQe2; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id n1si1903694pgj.247.2022.02.24.01.47.48; Thu, 24 Feb 2022 01:48:02 -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; dkim=pass header.i=@linaro.org header.s=google header.b=FaH9oQe2; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232582AbiBXJhw (ORCPT + 99 others); Thu, 24 Feb 2022 04:37:52 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56672 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230353AbiBXJhu (ORCPT ); Thu, 24 Feb 2022 04:37:50 -0500 Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BCD8626A393 for ; Thu, 24 Feb 2022 01:37:20 -0800 (PST) Received: by mail-pl1-x62d.google.com with SMTP id p17so1180171plo.9 for ; Thu, 24 Feb 2022 01:37:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=kpeZOLAjOWDOxOLAZwon9tgkbygh+pggRkOmi8tbYh0=; b=FaH9oQe2rreTUm+yh+gI6rkYx41p6V2vC0iPwLCgRW0y/ZsVOh4eYNXoZS1rDNTdLH AR0jjoIIwOARJDAftFsI9hYdyuP5zBqED/jw2Enbpo6YOYkWeDWH56pq1dQVbUWvyBoq rBXmMoYnC/nk53wQGU4FPq+jkB5HBsIRucV58qecRaBggrfrQg5bWUeQc+qwdghAGI0r XASWvcfosoFnIhFa3wqGmL6G6+QgpAZYAZXxL1+RPHi92JnqhbW4CvXNs/trHLbTSdaN lvsnij7+ibJFnKLbHhxGsgwtc37YB+R98f7q2p9lS6afgtW05veB+TNjltQLmuNNUmHD RBew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=kpeZOLAjOWDOxOLAZwon9tgkbygh+pggRkOmi8tbYh0=; b=7NTNmTMEMHDUF1p82f6lx+I3Aa1mKLQ3X7rmhNY6I28L3uQNP837WADWR/LJfFF3gv aoYfg6XowivpXTYxt77ObsN9BSeSHuoK5V2XNyj0i5EgYzYUUifyIHSRHIly/pEZRplT Syxc0FF+TGXf58OdjECKR1I7J4BS3+L/kuTQbOdios+BTBoQXKggtxiE8a1zxzWTiFTH EEiMV2cBqnIOGPD01dbFC6Tj7M//cRIGs1h/tZd4FORNbriy4c1vy/Hns1+IhusglaD8 8l3NPEkGCCyQKx0zdJYqVlu6/zLyQBVCL6YR/zBb9c+MT4x9ijVMrKtIin7yGiAWqwtr nF+Q== X-Gm-Message-State: AOAM530JcIO2flNBW79eC0zUFM/yw7xoAN7w4RJ9dnOpaCV+Rl3aA5Vq AD2aQ9G3bnaYVxtYWmJ5ezrfHg== X-Received: by 2002:a17:90b:1193:b0:1bc:1b5a:84e4 with SMTP id gk19-20020a17090b119300b001bc1b5a84e4mr13794880pjb.113.1645695440264; Thu, 24 Feb 2022 01:37:20 -0800 (PST) Received: from localhost ([223.184.83.228]) by smtp.gmail.com with ESMTPSA id b1-20020a17090aa58100b001bcb7bad374sm2233192pjq.17.2022.02.24.01.37.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 24 Feb 2022 01:37:19 -0800 (PST) Date: Thu, 24 Feb 2022 15:07:17 +0530 From: Viresh Kumar To: Lukasz Luba Cc: linux-kernel@vger.kernel.org, dietmar.eggemann@arm.com, rafael@kernel.org, daniel.lezcano@linaro.org, nm@ti.com, sboyd@kernel.org, mka@chromium.org, dianders@chromium.org, robh+dt@kernel.org, devicetree@vger.kernel.org, linux-pm@vger.kernel.org Subject: Re: [PATCH v3 4/4] Documentation: EM: Describe new registration method using DT Message-ID: <20220224093717.3vsi4t26zcmoh2ra@vireshk-i7> References: <20220224081131.27282-1-lukasz.luba@arm.com> <20220224081131.27282-5-lukasz.luba@arm.com> <20220224091508.fp7emu2zyhavkfkt@vireshk-i7> <02d16fbe-d4d6-a7f1-d81f-39f05dff76fc@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <02d16fbe-d4d6-a7f1-d81f-39f05dff76fc@arm.com> User-Agent: NeoMutt/20180716-391-311a52 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable 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 24-02-22, 09:25, Lukasz Luba wrote: > Our partners had a lot of issues with EM+EAS, because they were not > aware of the internals of EM and limitations. > > We've started to name two types of EM: 'advanced' and 'simple'. > The 'simple' is the one which causes issues. Now when we contact with > partners we ask if they use 'simple' EM and see some issues in EAS. > This is a needed clarification and naming convention that we use. > > Here the paragraph name is stressing the fact explicitly that > from today we have the option to provide real power measurements using > DT and it will be the 'advanced' EM. I understand the background now, and since I am part of the same community I can appreciate that. But being a maintainer, I have to say that when we look at something from Upstream's point of view, we may have to neglect/ignore the terminology used in downstream. From what I can see, there is no advancement here, as of now. This is a very small change where we are getting pre-evaluated power values from DT, instead of calculating them at runtime. The data may be more correct, but the EM doesn't get advanced because of that. And so using such terminology is only going to harm further. If EM gets a "advanced" algorithm later on, which can improve things, then yes we can call it advanced, but for now there is nothing. -- viresh