Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp1267036rwb; Sun, 6 Nov 2022 22:38:55 -0800 (PST) X-Google-Smtp-Source: AMsMyM45mRXYlIKv/sBJYTHWXUkZzYnU9yDKL+mRfHI2HfIENnLFN+ExOLQT2QzUmQwmZYProscv X-Received: by 2002:a17:907:3e11:b0:78d:9918:217f with SMTP id hp17-20020a1709073e1100b0078d9918217fmr45502204ejc.742.1667803135572; Sun, 06 Nov 2022 22:38:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1667803135; cv=none; d=google.com; s=arc-20160816; b=KUjcoR2zHB6A7+4u3DJJHcZTRjqikMSS+7wsBx4iJFSk7up/ONvjWd9wITfa2/VnLZ pvV3N9JKeFbHu09M4q8agOV8EsM5zr8aCkFa0sT8tPy4YTC9gI0/HD9ZQDq00YFUE8Og x0gJDOrRdZZE5bN5w7gb7S1Wj4EEfRMLK0IEWNI1XjtebkQfCCdZdom8Tcalq2iCobKX xhGpGu1dGth12HFjBYKiNOGtsKRLxtDC4BVsWXbZFEP0U9X6qxuVwtZml5r0LzR2uzNk lIYuHpz66GtUpEmfm+TS/esm2tyj3jjZW5QpJAHTWmqw0ffgFfEw5x6p6+YZdXbmDW5z 39Fg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=hHO9LGTR6tWq8NtHbmt7CuQkGK66YEpPE/913FcVM5M=; b=Gk/PuawlHqLAyXMnJnLIZi4d6MqdMD3P+wJVnR5bGaTEU2C3eDrz+XzrCzZ/8ApqmY nEhYV58OlA0yMb1YuIQJRB+2SvDQevSr9gZeUsNx46qe1tiHn006Lpi2NrkRpAzxgqlo C9+QMsoB9oi7hrmxavNF17dAR/3ymjf8JJ08NAor7EobDP8q0EM0twE2V9Z/d+vDIXch MtJikcoJmz1+KQr2InN4W38gS7mYI9kcG0MLZT+2XWct5V85zpzvhWzstRa2TZ5dSTEa i44vPAXhc2cp0jCKzwi9ZqCyNhu+KtJX/DVVJxiIn0MV8vG2nuO4r2N4xEr7s60xrqTB uHcA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Hofmv0zD; 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=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id eb6-20020a0564020d0600b0046462065e1dsi10014957edb.291.2022.11.06.22.38.30; Sun, 06 Nov 2022 22:38:55 -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=@linaro.org header.s=google header.b=Hofmv0zD; 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=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231149AbiKGFzn (ORCPT + 96 others); Mon, 7 Nov 2022 00:55:43 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60864 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230332AbiKGFzm (ORCPT ); Mon, 7 Nov 2022 00:55:42 -0500 Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ADC01BCB3 for ; Sun, 6 Nov 2022 21:55:40 -0800 (PST) Received: by mail-wr1-x433.google.com with SMTP id v1so14545138wrt.11 for ; Sun, 06 Nov 2022 21:55:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=hHO9LGTR6tWq8NtHbmt7CuQkGK66YEpPE/913FcVM5M=; b=Hofmv0zDOLo0a4Zw0r6u3YN8H2rV16cZKG+zGX3Epy8VMHUxnW43c6iXukitDgwjE4 lbqN6wnC2FO/kZ4KUpUxrBqB7y1sSiBkT3sQlGej8fimI5HEnv/qYWSRVVDe9qs5Sn0C N2P6tNLDPP55kDBtNVbZUBBBRIXGJOBySi6uffBk0McMq7qu3/qNHAVmLu7b5NiN8SWk rm1kxSQNRpvoQTph7oc0gA04eTQ22zFHZcEayVbosR2JkdgCKUKp/YKORiChAW9Ka3Ml fKeK4zTG1uIzUpgDKKUBFnK+RBcivc9eKTF9Mw6SUe3nw/pt1sx/N51ydd+WUxPptxR8 52lw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=hHO9LGTR6tWq8NtHbmt7CuQkGK66YEpPE/913FcVM5M=; b=5fYbsgej8CNmVqu9+6eMdQRv7/jtlVnYN0faPw6g+po0ybCBIlfcJHkT+OZHD88mIU TYLxyPvyU6rbveX3VpZatdwo7+e7BHBkzPgNgqGwp48BBfjAjhu4TP8iVgKPwPQIFGHh pOW8KMa9141zdqXOZuZ5UvSbIeN1Y5CwAOTNbmGBcSOZtR5ouFD036bVs8deZkRs+SSx Xosd6SBT2Gvhq842zCRKrQK5jarm/Tqec5mMtNojnkNr9ChFg7NLQnCeNN2AoTEzdJSg Pk7uUetuEgTN82rVz3sVcsJkwJCZaT15RYuOEMRoAABezp+3jXv5x5tUv/aM4yQekFIx jV6g== X-Gm-Message-State: ACrzQf3cxmx4Gqk3FOukPdGxomo6peFu0+4xm8E27SwTubWH4KTdCaNe JqzXppk8EQm5osQqVME7TGLX4MViz6WBMkcv11YHQw== X-Received: by 2002:adf:fa83:0:b0:236:a97d:693c with SMTP id h3-20020adffa83000000b00236a97d693cmr29467043wrr.108.1667800539251; Sun, 06 Nov 2022 21:55:39 -0800 (PST) MIME-Version: 1.0 References: <20221027115745.240516-1-ulf.hansson@linaro.org> <166779074268.500303.10369639779721394913.b4-ty@kernel.org> In-Reply-To: <166779074268.500303.10369639779721394913.b4-ty@kernel.org> From: Amit Pundir Date: Mon, 7 Nov 2022 11:25:02 +0530 Message-ID: Subject: Re: [PATCH] arm64: dts: qcom: sm8250: Disable the not yet supported cluster idle state To: Bjorn Andersson Cc: Andy Gross , ulf.hansson@linaro.org, konrad.dybcio@somainline.org, dmitry.baryshkov@linaro.org, sudeep.holla@arm.com, quic_mkshah@quicinc.com, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, quic_rjendra@quicinc.com Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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, 7 Nov 2022 at 08:43, Bjorn Andersson wrote: > > On Thu, 27 Oct 2022 13:57:45 +0200, Ulf Hansson wrote: > > To support the deeper cluster idle state for sm8250 platforms, some > > additional synchronization is needed between the rpmh-rsc device and the > > CPU cluster PM domain. Until that is supported, let's disable the cluster > > idle state. > > > > This fixes a problem that has been reported for the Qcom RB5 platform (see > > below), but most likely other sm8250 platforms suffers from similar issues, > > so let's make the fix generic for sm8250. > > > > [...] > > Applied, thanks! > > [1/1] arm64: dts: qcom: sm8250: Disable the not yet supported cluster idle state > commit: 5c7fa5de12a31c1425cc87ba2ef27e6ae0a1788c Hi Bjorn, There seem to be some error while applying the patch "arm64: dts: qcom: sm8250: Disable the not yet supported cluster idle state". This patch is already applied in your arm64-fixes-for-6.1 tree (commit: cadaa773bcf161184fa428180516bae33a7bc667) The new commit: 5c7fa5de12a31c1425cc87ba2ef27e6ae0a1788c, however, disables the Big cpu idle state instead. I'm not sure if that is intentional though. Regards, Amit Pundir > > Best regards, > -- > Bjorn Andersson