Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp4612247pxb; Tue, 22 Feb 2022 02:33:52 -0800 (PST) X-Google-Smtp-Source: ABdhPJwW/PoWNFfX5RRGCDLZynUXGt0UgO1F3A5TyPKEZMYlAVE1S6AM9BUTpnntACFNhR8S39zU X-Received: by 2002:a17:902:d507:b0:14d:76aa:fd38 with SMTP id b7-20020a170902d50700b0014d76aafd38mr22764425plg.107.1645526032310; Tue, 22 Feb 2022 02:33:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645526032; cv=none; d=google.com; s=arc-20160816; b=I5Z0Jd8UlG+nmtFhpgnsrvg0TUWoJs2BBtmWKEf5h0H9Lif8PIocf6iCyPDDsIxIZG g8xrE23xAo81qnnmeQQ1/JKJn7VsB8yBX9jefK0IQjAkx9Z664UtXDXqE+jq6l9kOZLm GTqQstdi0qlw1Ub77vahb+ntNI4Yj1Yl+0oLTmXuBO8YKBQ0tuekpTrL4b4WeA4Co479 vXLRvcN8ftnsINw3uNQm5L2QpBIpmvKDinZun5KC86jWHrLliMsWjA7tm0jMW9n8PTZW lkthOJqJq3b3cxoxJyl0rFCdZTiSCDc8z1Ba7URRawnyyZghPtGxZnn3GOVlqC+90qq0 V/cw== 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=RTtvSnkjQQcUgF7xBZFt7yyfK1O4T1NC4KLnKMVu9MI=; b=TNV5+WQ6QTfGPdasavohpLsssEFvy7jHFt5WGAC3gEs1kMekvBh1OzlewHYPaNOe0O pREnX1cHurrQTCfRRPWm/cfq1cpEpMAHQkat5P1Zke3mY7I9LiRg9SBoxjSnnzb4ZJmk TSV1GhfKivPs5+jQMgNOd4QfAs3hE1i0gmuZxeqa3J7BTdpAxrveTChEleW8nlyW6J6T Du7ZFSClnIP1LDrg5Ku/Uz6tY0eDzepHkTUk8CqJErBQQzlwPa93UvBYhzs5XHoonkAt mq2H47C+4FmkAvikdkhYyjsOHL6B39U9a1K5Y3RmBH4k6u7jykVHre3BxLr6Y3uq991M yASg== 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 w10si12765399pgs.822.2022.02.22.02.33.38; Tue, 22 Feb 2022 02:33:52 -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 S230346AbiBVKEK (ORCPT + 99 others); Tue, 22 Feb 2022 05:04:10 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33392 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229735AbiBVKEJ (ORCPT ); Tue, 22 Feb 2022 05:04:09 -0500 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 0F6EF5D1AE; Tue, 22 Feb 2022 02:03:44 -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 B0A95106F; Tue, 22 Feb 2022 02:03:43 -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 C61B83F5A1; Tue, 22 Feb 2022 02:03:40 -0800 (PST) Message-ID: Date: Tue, 22 Feb 2022 10:03:38 +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: [RFC][PATCH 1/2] dt-bindings: power: add Energy Model bindings Content-Language: en-US To: Viresh Kumar 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 References: <20220221225131.15836-1-lukasz.luba@arm.com> <20220221225131.15836-2-lukasz.luba@arm.com> <20220222030337.ijnfrh367illmidr@vireshk-i7> <147e48e5-e310-cd8f-ba8c-ff32e3094be3@arm.com> <20220222094547.tgj4bciq6rez62nk@vireshk-i7> From: Lukasz Luba In-Reply-To: <20220222094547.tgj4bciq6rez62nk@vireshk-i7> 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 09:45, Viresh Kumar wrote: > On 22-02-22, 08:06, Lukasz Luba wrote: >> I'm not sure if that would be flexible enough to meet the requirement: >> power for each OPP might be different in one board vs. other board. > > Don't DT files overload values from board files all the time ? Why wouldn't the > same apply for OPP table as well ? In that SoC and family of the boards, there are no such examples. It used to be popular in arm32 boards, but I'm not sure nowadays. > >> AFAIK the OPP definition is more SoC specific. > > This isn't about OPP definition as well, but just that if DT allows you to > override or not. I think it will. > Redefining the whole OPP table, when the freq, voltage, interconnect, and other old entries don't change isn't too messy? As I said, I would prefer something lightweight, not redefining all stuff from OPP in every board file.