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 41040C64ED6 for ; Fri, 24 Feb 2023 02:17:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229741AbjBXCRU (ORCPT ); Thu, 23 Feb 2023 21:17:20 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41094 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229446AbjBXCRS (ORCPT ); Thu, 23 Feb 2023 21:17:18 -0500 Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 66EF55E874 for ; Thu, 23 Feb 2023 18:17:17 -0800 (PST) Received: by mail-pl1-x632.google.com with SMTP id e9so10216838plh.2 for ; Thu, 23 Feb 2023 18:17:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=XwQM5jDCnisoGK+9lg+DN9mXAFVodSsNBaIsTAFZ/HA=; b=U+6xJp4C4jhOSJawd+VDYS75rVNz161MGfLLnJrgNjnKmt8cBQdIR26gxPBeNPJ6qP m9AHc5m4KsZqNcMuZHDfheCR9byDTZvYiRj2fid6Io03+1lVcPVJfAT5x23GwMKbFBY5 pCm+SzTK21aJFfV9MmyCrEU1cauAGOffKM7iN1UW08fUNsf/JRrDNHyedKZpq5scl9lS D61eeBFRipb4kA4c1lYrvE0M+dpq5mCIQQd2pndWwvF+bco0GDqcaPj8wic2IYeRlCgT Rp113bTu8exyqlSchWz4PZ17yx5XbqKGSJeg3WxjPNTq+TMbhfBFR8HpWsOcFO5fYC0K XKvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=XwQM5jDCnisoGK+9lg+DN9mXAFVodSsNBaIsTAFZ/HA=; b=zu8Zy9vmHav68700MHRNIEWnM+Q5k8gSKmcYgcpZuX4QfaDCEvkU1qnCTdYryZSSRY wdPXBKsRNi+NGU3uRMIGA1jXGhQpgCIv92ywave7zyKEJgfgT6A5WxsmabrEG0Pfb12J DycHPQs0+eNtT69/ztz625uYda2uEo8P+UmhFpOeYxmvjXHEJqG7WJUdsyRgMNSpdA/C Titjhups9mQ8U0/WNxrESrxKz2RJLpkBc3mZSqmPJtI4dW8uTJAVHkpujG9rAraGP6/V ROr5mWUnBtPoyru7ajXKDhOy1N7KbHJfw/Dl6S0ghuZIzFpLXh9wl0086rI9Owh+Z+u6 fzjg== X-Gm-Message-State: AO0yUKXQ2d7SMLpKYosg/j50p7Q/MrxVlBPyYhxOS6zhOQB0T7MhugCl 5v1s0CdroXQloF1Z24CPRbhVXQ== X-Google-Smtp-Source: AK7set/CzIDjqcs+ex1tt/uuL6og7+c8sKGOmyeRSPakEVadCRP1/lhjq2n1ROS6VFu3TO3FZkeR9g== X-Received: by 2002:a17:903:5c4:b0:19a:b9a8:3fbe with SMTP id kf4-20020a17090305c400b0019ab9a83fbemr10522949plb.48.1677205036904; Thu, 23 Feb 2023 18:17:16 -0800 (PST) Received: from localhost ([122.172.83.155]) by smtp.gmail.com with ESMTPSA id k17-20020a170902761100b0019a8468cbedsm4440202pll.226.2023.02.23.18.17.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 23 Feb 2023 18:17:16 -0800 (PST) Date: Fri, 24 Feb 2023 07:47:13 +0530 From: Viresh Kumar To: Jun Nie 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 Subject: Re: [PATCH 0/3] OPP: Simplify set_required_opp handling Message-ID: <20230224021713.stpcykx2tjkjwyti@vireshk-i7> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 23-02-23, 17:56, Jun Nie wrote: > It looks promising. The function get_target_freq_with_cpufreq() can be wrapped > to act as set_required_opps() callback. > But my case is a bit complicated. CPU opp depends on both genpd opp and > devfreq opp. I was wondering if we will have such a case soon enough or not :) > So the genpd_virt_devs array need > to be modified or add another array for devfreq case. While genpd_virt_devs is > bounded with genpd directly and coupled with "power-domains" list in > device tree. > Current required-opp nodes are designed to be aligned with the list. I > am considering > what's the best way for back compatibility. Please look at the top commit here: git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git opp/propagate Will this be enough for your use case ? I will post everything again once we are settled on a solution. -- viresh