Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp3859661rwb; Sun, 20 Nov 2022 23:53:41 -0800 (PST) X-Google-Smtp-Source: AA0mqf5K/s0kHFE6QMfi2HjGXZloMEUzc+nD5vZX7ur0CfkIuFR778iIyrMpVrqfaD3oPad/iz6V X-Received: by 2002:a05:6402:2065:b0:469:82d0:ca4b with SMTP id bd5-20020a056402206500b0046982d0ca4bmr2966003edb.242.1669017221532; Sun, 20 Nov 2022 23:53:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669017221; cv=none; d=google.com; s=arc-20160816; b=zC1JUBO2J4fufveZ7uupIO9VaJURZwAEXXTkoyvU9eYRHKc5niTTi3YvxCOXvIC8lo bD/AbhEM6xueiR/gUDNwPQ+ao1OSwYUrRtn5WWvQxB+mj4cqES1MWtjkdxudD3RNuAxk USeVTdzJHxZIES9OlGeM/TeS1DS8UR+wYbDUXJO5QVqWkq5ns8L3x3Fx09ey3C+Dbcg6 cCS8x3iBIzRE1iaoCNAfw7Uy6521EjSnzWTN2xfKZRXFVNeD+FKZnJvwR7i2iZSXbWeW l7k+DZaJwPPE+IGp8WcyiRhMl+nwZgdpIpEvdgfkb9BgTzk729gf6I+2OgtkT6H12oQF vZAw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=3MJ80aCyXCs9Nzj9jPczkgDl29H4O+ZaqjkF6IM7lKs=; b=o3hIbWLOaijri7VzsfhuSPyFKej7W2NabRriKWndP7InThKafBM+6JoXxz0G8vSX4S cwOdRK0qGsIhQdTFmIFUBJ0ZL17odNCvBHFf8+m7xFHXWILyJ6igWhnrMhLVDoCuvAXv AsQlaqwNpKbLoYHSstqG5HYYm+1sBFQjxfzkVMq7kiiy/cf6neL5ucFOKUCAE1Ee8Bzu cBuv1ZppQ1MkEKbtcGvYwkf4LgounR0YAFbdbEvsnx6RGdc6E9i2ATRRWnJC3QkTQf52 iqwFTrkn/FTKswUSlTw6HVa+O2hO/cBjjfOWtgNVhQ9GUd9DwwPTGdYgH9v0/XlA4p5d AIzg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=HqeoS5rb; 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=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s5-20020a056402520500b00468f6919522si9720029edd.564.2022.11.20.23.53.16; Sun, 20 Nov 2022 23:53:41 -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=@kernel.org header.s=k20201202 header.b=HqeoS5rb; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229676AbiKUHWh (ORCPT + 91 others); Mon, 21 Nov 2022 02:22:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42908 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229627AbiKUHWf (ORCPT ); Mon, 21 Nov 2022 02:22:35 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0729B634D; Sun, 20 Nov 2022 23:22:33 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id B358260E65; Mon, 21 Nov 2022 07:22:32 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0F5EAC433C1; Mon, 21 Nov 2022 07:22:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1669015352; bh=WJG5+ANBw3FNv8nSoyzix1RmK2851uIlja2ML+dxAGg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=HqeoS5rbkczlGuKqlnIHgiRck4mOCvfARtsq3dZXoxw6tSmt9h/OKmgdVhke86be1 jXMR+pSaqlbUkRAIJGLySlqQRlqU9R+osgivlYdqM/G+Awz6v6Uo9uUndBJ1a77BzC Qp8NzTeq5zNV/Co5EOUa3r0iKhf0fRNZ+FktRCFeu+dBZjhC6xgn9Jmrl/6x9zTtXW ZHzZOeI4Lv3HerisUjz4P/8scjLMLP9jLXGNlPFbiecf+Lw6DDpUKaKDX5tQnBA07G oQs+2HasKXtlDgaA8QiDRVWoNl/vV5k+fDhGwpvlMCyz38T9mqC/9RkRCmk0ixYcB6 TJ+2kosPeV4Wg== Received: from johan by xi.lan with local (Exim 4.94.2) (envelope-from ) id 1ox17x-0002R1-V9; Mon, 21 Nov 2022 08:22:02 +0100 Date: Mon, 21 Nov 2022 08:22:01 +0100 From: Johan Hovold To: Viresh Kumar Cc: Manivannan Sadhasivam , Viresh Kumar , Nishanth Menon , Stephen Boyd , linux-pm@vger.kernel.org, Vincent Guittot , "Rafael J. Wysocki" , andersson@kernel.org, krzysztof.kozlowski+dt@linaro.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] OPP: Disallow "opp-hz" property without a corresponding clk Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS 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 Mon, Nov 21, 2022 at 12:27:48PM +0530, Viresh Kumar wrote: > This removes the special code added by the commit 2083da24eb56 ("OPP: > Allow multiple clocks for a device"), to make it work for Qcom SoC. > > In qcom-cpufreq-hw driver, we want to skip clk configuration that > happens via dev_pm_opp_set_opp(), but still want the OPP core to parse > the "opp-hz" property so we can use the freq based OPP helpers. > > The DT for Qcom SoCs is fixed now and contain a valid clk entry, and we > no longer need the special handling of the same in the OPP core. Didn't this affect also sc8280xp? Perhaps you can hold off with applying this one for a bit until the needed devicetree changes are in linux-next for all the affected platforms. (It looks like Mani's series only updated sm8450 and I guess Bjorn hasn't picked up that one up yet either.) Johan