Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp4617069pxb; Tue, 22 Feb 2022 02:41:40 -0800 (PST) X-Google-Smtp-Source: ABdhPJwxQNfFTrQ1AiXY9QbmHU/i9n+wMZhxuC1sH9QWhzLqRNyqOpHZoymSJnNP0TKcoW7Frrz1 X-Received: by 2002:a65:6a13:0:b0:373:14f6:5d33 with SMTP id m19-20020a656a13000000b0037314f65d33mr19332789pgu.62.1645526500401; Tue, 22 Feb 2022 02:41:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645526500; cv=none; d=google.com; s=arc-20160816; b=lT6CIb8UXQaqKVDFdNr+Wp8AHSRfSbR/HP0rurz4MlrkaQ6sOVqzuNVBr5yNoKu/XB lIqS+sUyGdS8P7FYgQG6PBXKXI0/cNzxJaGp07+DY4LFVEV2lVaNvVFF9JfYm/bhAGRU /RhLQvTVqOYfgwEJVqCBrBCxJ7Dhhj5pSwGxoI6ZEsE9IjdZZPa/8at/gWLeQvKNswYF WLxKt91wd4dsuxrU71CfhPJSkNegwdqpzRxTf+boieetUxrCmNKBQ9o2zbK4OYc0Bzgu InUYkqvufiIWGSe3TI1yMRqL0fWTcOFqec7NJogXGBsEVB1NjZVz5OvHU5xJn3dcphdp lVCA== 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=XJOc4s/JmrXgMJQfNvQ3zYpIHSf0zbHb+cTgCBKjP8I=; b=VzAaxwbFNv7WYAZJDrmIwQ44DWETg/cke8ctzKV0toaWsKqHf9XqhhHROCwVeetHdR Q72/vnPsWVFlViHe3OtzV52XQoSGVBDsWXEFj7nT8b00fi/V1R8pBZEfGAy+4i35N74Z ud8FlLfTWIHu/kzIsnK9dlPk+HeeRkh/BWUhKGFtaT8UNDQN9S1W62x7p8BrkANYcCN2 SKV/dUeT/WXaY1zHIQWVnv0hDMzfrQX/ABNiJNm2T2EvQTm5ZWvShhdkB8+nJF1P7qwF PUX3g7AxI/sBjQTcaJOw8G94Ybw2KTpmASGF1A4Cp/K/geqxQbA7xBU6fYe9oagBhnBx ba4A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=YtKoFtPD; 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 d8si19835885pgj.298.2022.02.22.02.41.25; Tue, 22 Feb 2022 02:41:40 -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=YtKoFtPD; 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 S230207AbiBVKNO (ORCPT + 99 others); Tue, 22 Feb 2022 05:13:14 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42226 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229526AbiBVKNM (ORCPT ); Tue, 22 Feb 2022 05:13:12 -0500 Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A75A613AA39 for ; Tue, 22 Feb 2022 02:12:44 -0800 (PST) Received: by mail-pl1-x62c.google.com with SMTP id u5so15195950ple.3 for ; Tue, 22 Feb 2022 02:12:44 -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=XJOc4s/JmrXgMJQfNvQ3zYpIHSf0zbHb+cTgCBKjP8I=; b=YtKoFtPDq9w4pOD4tUF/xaR3cgs6ntps/TGd9w4bavkd2Z9rgvvmXJiLHFCSXE7SQr 57+itX+45l3RNsA6+gOR56Km9guMlYU+mF2/L1gANc3sb1nqwU4uw+KqcCebql1xZqna jJ3XQtWc6gfqiKKZ1GwYWFEq25BAY7Zsp6tQZBycsv1doi/G0HmvnXu+lhJ7LS0uN+WQ quZenR9rc5X8GHcdcUUFo0SBqyEV0ipED5XTc+2DXVbmfQ1XNDBIuGdLph4xU4VGNuYw kp4J14p9at86TscDjxH4a6W+tVwY6WTE7HuNBgocof1NTwm8WuLsWLQrwGD5tqpv5PQE NeEQ== 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=XJOc4s/JmrXgMJQfNvQ3zYpIHSf0zbHb+cTgCBKjP8I=; b=v9YSg4uguj7/dmXIEcD5xnt14Wt0KutUNi/+NIVUuERGp6SiYxdfsZ/d2EML5h/pj9 NuvIpb3nXy5YYBi1ST97rdeha/sQdTREA0ID5NcY0kc4jnTOJD/p6G5hIbmEkTKVcPEJ +p2NMsKj6BBbRG4luffQ+C4LpRTXMmanw00E382uy85bJkdcjNWwVWDwYnFk71JY3Dvi HGTSidaO5GkE+I9jjMWhEImHHchrZo0PU1PRgVxMk8ts6S/30TsxzO5zIUMhieT0Xqv8 2/uOANvPV+CwHT/+KYrghkKrVMW7Pi+PaYSE7bYRGF/Z6yBDdD10ZOhpBlr7zmdGdk/0 b8WA== X-Gm-Message-State: AOAM533b6lflaTfoDac5G5bVQ8+Rn/lgvjwxKZmAvWE/vSEAMJi/00ZJ f+ZrHbuuWn8+Y+qknpLfml4ECQ== X-Received: by 2002:a17:902:7407:b0:14f:b5f4:6537 with SMTP id g7-20020a170902740700b0014fb5f46537mr8873407pll.32.1645524764110; Tue, 22 Feb 2022 02:12:44 -0800 (PST) Received: from localhost ([223.184.83.228]) by smtp.gmail.com with ESMTPSA id h26sm20821773pgm.72.2022.02.22.02.12.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Feb 2022 02:12:43 -0800 (PST) Date: Tue, 22 Feb 2022 15:42:42 +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: [RFC][PATCH 1/2] dt-bindings: power: add Energy Model bindings Message-ID: <20220222101242.chwcxan2nyhczqth@vireshk-i7> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 22-02-22, 10:03, Lukasz Luba wrote: > > > 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. Here is one I think. arch/arm64/boot/dts/freescale/imx8mq-librem5-r3.dts > It used to be popular in arm32 boards, but I'm not sure nowadays. I think it is still common, not with OPPs though. > > > 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? I think you misunderstood what I said. The common part of the OPP table should stay in the central .dtsi file. The dts files though, should just add the power specific values to the existing OPP table. > As I said, I would prefer something lightweight, not redefining all > stuff from OPP in every board file. -- viresh