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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id F356CC433FE for ; Mon, 21 Nov 2022 07:45:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229677AbiKUHpG (ORCPT ); Mon, 21 Nov 2022 02:45:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55908 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229610AbiKUHpC (ORCPT ); Mon, 21 Nov 2022 02:45:02 -0500 Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F038AEB0 for ; Sun, 20 Nov 2022 23:45:01 -0800 (PST) Received: by mail-pf1-x436.google.com with SMTP id k15so10619357pfg.2 for ; Sun, 20 Nov 2022 23:45:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=U4YrBZ+z5Rv0IVGY54zvMFMIIXczOnV6KezpP9Psod8=; b=d8JZSgvT5BA2o/z4WbLW3psSTivyO8g7XPXzffla04xDuMJhu8t4lVOKt8Vbe2Pop7 yTKPTlgh7whFG5+4J9zoqSqNK3JWDAQiwSJYw290shiuW1+HElSc6++iWGKLKT7pIlCg GVLSmOLBHJViK/P4R9c+NZy9F7BrmolbUwsKA4sExYcmRk6ydtfWwkfhK9N/8T7ARc+G UayKsstAExOiUvc2e1AtdHm+5N2sxj7qv4GLwG6mjxf0QlmLm8wSDgyuI9QbW2UlRdhA OJYl1+ZTB37mwUDlclsEmd8AkFm65UkVyV4P2XSFa7b3ptRGh29Xg3rjPkydhtR5iIeI 6Orw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-transfer-encoding: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=U4YrBZ+z5Rv0IVGY54zvMFMIIXczOnV6KezpP9Psod8=; b=K0PRx4oxjxhmLhZRTxVSB/J/pUJg58PdIlSAgUhk0ZW1gEhRVifFdZg0xzQ6oiP4Mi D773C7AuuCcdQTSoV8itOU89I+iprvVo2C5gt1P+Uc1DE9iibKuXPwe24z2Fqpw/26VR Dhepg9t961m0XZMS5ZT4up88srtKX/7VvAbXXDjkOs+YAAD0aOGyuL/+TefqxP2lM2Ql JjkJSFXszykB4ofg+XDvYfCNFnGl3lyazMVK69GSy3xSEeIRwFwtSxiAZ0W+xBQjGhjy 3f4grMiY2XjqlEk9eIq55Wo/MlqjqVN02ygMHzfbRx167Iinkye6wjJO/0c7ecq566fm kVzw== X-Gm-Message-State: ANoB5pnp84w5avwhGPnYadGAbVqloNQ3KGkDhvtPhNIObCibVB/eC8VN hMO5H2y6a781fql4iDxysBqo X-Google-Smtp-Source: AA0mqf4f7se5taUJcccRbDf6HECYnxDm8eEEqavRBFe/z+MIHaXDoJXozlpOjk3olLjSJ9faNG3Cbw== X-Received: by 2002:a63:d948:0:b0:46f:1081:f517 with SMTP id e8-20020a63d948000000b0046f1081f517mr16962151pgj.297.1669016701452; Sun, 20 Nov 2022 23:45:01 -0800 (PST) Received: from thinkpad ([59.92.99.222]) by smtp.gmail.com with ESMTPSA id m8-20020a170902db0800b001783f964fe3sm9085680plx.113.2022.11.20.23.44.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 20 Nov 2022 23:45:00 -0800 (PST) Date: Mon, 21 Nov 2022 13:14:53 +0530 From: Manivannan Sadhasivam To: Viresh Kumar Cc: Johan Hovold , 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: <20221121074453.GF11945@thinkpad> References: <20221121073817.7ollj7jeixrx5og5@vireshk-i7> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20221121073817.7ollj7jeixrx5og5@vireshk-i7> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 21, 2022 at 01:08:17PM +0530, Viresh Kumar wrote: > On 21-11-22, 08:22, Johan Hovold wrote: > > 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? > > I assumed Mani fixed all affected Qcom SoCs :( > > > 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. > > Sure. > > > (It looks like Mani's series only updated sm8450 and I guess Bjorn > > hasn't picked up that one up yet either.) > > I applied that series today to my cpufreq/arm/linux-next, since it had > cpufreq updates too and these patches are rebased on top of them. > Ah, I thought you applied only cpufreq patches. DTS and bindings patches are supposed to go through Bjorn's tree. Can you please drop them? Thanks, Mani > -- > viresh -- மணிவண்ணன் சதாசிவம்