Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D1715C64ED8 for ; Mon, 27 Feb 2023 09:22:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230084AbjB0JWh (ORCPT ); Mon, 27 Feb 2023 04:22:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56016 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229969AbjB0JWQ (ORCPT ); Mon, 27 Feb 2023 04:22:16 -0500 Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 836551FCE for ; Mon, 27 Feb 2023 01:21:27 -0800 (PST) Received: by mail-lf1-x130.google.com with SMTP id i9so7611129lfc.6 for ; Mon, 27 Feb 2023 01:21:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1677489686; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=K4vKb9mEq8TjcumxIlTnCGVRdXGwvc52NzKU43XYqaQ=; b=LsuSnJZ1AgMn0+FwWdXrwe6b5ZDdHxdwLSLl3CwD910O0wBuUcrfKJoR7k+uvMvrVM ixA6DTs1/DSoacWt4jn3CX9AGnOZDoWURey/HHhSaDHzjC9OVxPLyC5hZJFuXSX1EUPd JHOmkShINZ24+kIIhp6flTOpPOR95PIQmXKqnJ12obbHjx0I/oMY+HgO8ax1eNylLjee WwP8Lz7aBnmU/NKW+hiCXQ9gLGUn3mxk/9caLhyiSjTlCz37VVS3Tuc9ND7rJhUErACj m3/OXHgfzXcYmovi78hidHAqRmKmCGRSkEnWCeH0psQcDyCJ58mlys1SlAa7qbfGXsMs 8SHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677489686; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=K4vKb9mEq8TjcumxIlTnCGVRdXGwvc52NzKU43XYqaQ=; b=iRkb19PTRrVgDmxc+i9y0bSV1lzMA3jPPmkuQCHuKXp5q43/9EEb+qbRCU0vC2fxaB qtex7CZRM1P6Z8vz/py1DhH0gAB0GFj+Usy6JebgJGFCsQz9MruEF2oQKXv4V6MZ7QJm vOXREvotvEFxK1GcB8/o66YhkKaCcadb/OHNKR7/+HZ9s2opgWuSRLQgzouhi1hTY52u fofkmbenEo/nbQTz/IeiB/UBMk1Le406xWv+zN+3DD3g2uNSxLCMaJ+c7rDku7ygiuJ5 O1nl4XpnJk8XyO/6WAi9LH40qNdPQ4wniqgqX9s3dAKTHFid4LiHtrD5J1VYfgZPQ69F C43w== X-Gm-Message-State: AO0yUKVwE/SFcZNc754s+lBp6TvWMPekZNd85Qunyamr9/axIRx0PkPp ecL29z1pF94FhtnEk+zVc8RuGMU/ZQJHU5Z+d76roA== X-Google-Smtp-Source: AK7set+LBfQK7pU11FnKg1wid2t8Zu/K6bDjzW7zfw+pgjz4Dx1NNfjKLH47iTIIWlShb2/cKW7LsKpwUgTfHCqovYg= X-Received: by 2002:a05:6512:15c:b0:4d5:ca42:aee7 with SMTP id m28-20020a056512015c00b004d5ca42aee7mr7294032lfo.7.1677489685796; Mon, 27 Feb 2023 01:21:25 -0800 (PST) MIME-Version: 1.0 References: <20230224021713.stpcykx2tjkjwyti@vireshk-i7> <20230227042349.3p2ijo6s6yyqc267@vireshk-i7> In-Reply-To: <20230227042349.3p2ijo6s6yyqc267@vireshk-i7> From: Jun Nie Date: Mon, 27 Feb 2023 17:21:56 +0800 Message-ID: Subject: Re: [PATCH 0/3] OPP: Simplify set_required_opp handling To: Viresh Kumar Cc: cw00.choi@samsung.com, Nishanth Menon , "Rafael J. Wysocki" , Stephen Boyd , Viresh Kumar , linux-pm@vger.kernel.org, Vincent Guittot , Manivannan Sadhasivam , linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Viresh Kumar =E4=BA=8E2023=E5=B9=B42=E6=9C=8827= =E6=97=A5=E5=91=A8=E4=B8=80 12:23=E5=86=99=E9=81=93=EF=BC=9A > > On 24-02-23, 16:17, Jun Nie wrote: > > For the opp lib, this is right direction. We still need to find a metho= d to > > pass devfreq device node to opp lib, just genpd_virt_devs for power dom= ain. > > I am not really sure I understood it all. What is "device node" ? DT node= or > struct device ? What exactly do you need ? Sorry for not expressing it accurately. I should say devfreq devices pointers, just devfreq_virt_devs vs genpd_virt_devs. Then you know why I add devfreq-devs dts nodes below. > > > But I am not clear below is the right way yet and this also involves wi= der > > changes. Or the opp's owner, devfreq device can be referred via opp lib= ? > > If so, we do not need to add devfreq-devs to cpu node at all. > > > > cpu1: cpu@101 { > > compatible =3D "arm,cortex-a53"; > > device_type =3D "cpu"; > > power-domains =3D <&cpr>; > > power-domain-names =3D "cpr"; > > devfreq-devs =3D <&cci>; > > devfreq-names =3D "cci"; > > Why do you need these ? > > > operating-points-v2 =3D <&cluster1_opp_table>; > > }; > > > > opp-200000000 { > > opp-hz =3D /bits/ 64 <200000000>; > > required-opps =3D <&cpr_opp3>, <&cci_opp1>; > > This looks fine though. > > > }; > > -- > viresh