From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 511C3C47096 for ; Wed, 2 Jun 2021 12:51:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3B8856121D for ; Wed, 2 Jun 2021 12:51:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229822AbhFBMw7 (ORCPT ); Wed, 2 Jun 2021 08:52:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45192 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229751AbhFBMw6 (ORCPT ); Wed, 2 Jun 2021 08:52:58 -0400 Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DFFBAC06174A for ; Wed, 2 Jun 2021 05:51:15 -0700 (PDT) Received: by mail-vs1-xe35.google.com with SMTP id e2so1004400vsr.7 for ; Wed, 02 Jun 2021 05:51:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zDam4v5Fg9p7lK+CPPtdMq2wb+GIbZcnsBCVIiUd08s=; b=pPx7UQ5vCXmUVaWp/RGRW8H3dUeJPovQZDDbaJVgs5/Wp6iRe5oN3pKw2b4JwQXMiT lMEGL2nBG0T/ztRgyHjWu/z0HHHB/0H9SIzc/4mfpBERd9AKFFV+SGY2FnjATr39V+yy IrZXEkbTq2//k3FAo/Un/eAHd4UMhDZaZV4PZHC22BXOslQbAj3t8okWLVTmr+45tT7d iAtxORC4HMNJcqe5TQ/uvvMb1EwqvfBjkK3SvbefiKKbpFWUFZls3ukK/eVJH1iPFRfQ U2htTY/gOql+jetOZw7vHEGRgW94m+6W3URlxLlhXxyYPcnVDuC4cDiE8PuFj60d5b8v fAzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zDam4v5Fg9p7lK+CPPtdMq2wb+GIbZcnsBCVIiUd08s=; b=SIcj1iba2g16NxM/r9e1yxS0czi/0zkjhbwikZlqNFCgkJkr7SWxXZXk3Lmp6NHXWA WStVAO/j7w2+zSrEXWspT1wDEJ7P/3ZWgUgd/0fiNfoNEuUwr1FSeaPVp0RHZAl0HYNm MIjnFS/BeHMEatbJe/L3tzDXpgp7+khsYW+g5KxkAx86vYC6hHQEQVEmEpM/a5Ua41lO FCcwJxxDCviJYSMIli+FbDE20YCcrMs+hjIcwAZJdEcpzWCPVgbQuIuVC7GrrXxAjkQ6 xhL3dlitJeRbZ5hp8gSWRTIXUiPjND3YuSe5jkOGj0SDM8pyvPX39sam0+XlaVPtfiyd sYWg== X-Gm-Message-State: AOAM533bb85qf0S7QeuMXDKyVci8Ujkf9y/0+CWnYwu+GkHNMFInGTF7 Bl5e5D4Wy0kTwEkpt/T515WaMUlU8TtZXjYdYLbq9g== X-Google-Smtp-Source: ABdhPJzUginGmlokX+ysh4R5RQMBlTK4PfZt1V/KV/Te6Zr4zZ5crlWHz5ddYGKBWzw8HczkDLY1ZEHZw3YTwIkaRuw= X-Received: by 2002:a05:6102:5da:: with SMTP id v26mr2293516vsf.19.1622638274853; Wed, 02 Jun 2021 05:51:14 -0700 (PDT) MIME-Version: 1.0 References: <1622095949-2014-1-git-send-email-rnayak@codeaurora.org> <1622095949-2014-2-git-send-email-rnayak@codeaurora.org> <20210601114426.3vhh2twocqx254b6@vireshk-i7> <20210602105459.t3ptci42lgvrzqlx@vireshk-i7> In-Reply-To: <20210602105459.t3ptci42lgvrzqlx@vireshk-i7> From: Ulf Hansson Date: Wed, 2 Jun 2021 14:50:38 +0200 Message-ID: Subject: Re: [PATCH v2 1/3] dt-bindings: power: Introduce 'assigned-performance-states' property To: Viresh Kumar Cc: Rajendra Nayak , Stephan Gerhold , Rob Herring , Bjorn Andersson , Linux PM , DTML , Linux Kernel Mailing List , linux-arm-msm , Stephen Boyd , Roja Rani Yarubandi Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On Wed, 2 Jun 2021 at 12:55, Viresh Kumar wrote: > > On 02-06-21, 12:45, Ulf Hansson wrote: > > Alright, so it looks like we already have the DT binding that we need for this. > > > > That leaves us with the question, at what place should we parse it > > (call of_get_required_opp_performance_state()) and set the performance > > state for the device? > > > > Does it still make sense to do it while attaching the device to the > > genpd, you think? > > For parsing, yes this is the right place. For getting that into > effect, whenever the device is supposed to work, i.e. with runtime PM > somehow. Okay, thanks for confirming. That would be along the lines of what Rajendra did in patch2. Kind regards Uffe