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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 41646FA3740 for ; Thu, 27 Oct 2022 13:07:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=UjmnFRN6nMFjYeZEdOrJLT+oSoInOXgcEqeMpiv0EAQ=; b=FQwBYO72+CKWnv IDa5FByKHnOLc55lIJoczGhfJSDWfLTI6kE/qVrsDEFJsi7b0HoZcNvMVJpUz258ZrKqmq5utF9ZJ pGPCrU/zGnL5QZoEbTtjqX0AyaRTpR7F1B5rVLytZPZI5CVwz5nNupckqnKkStT+0iSee8blKtGKb +jLNC5WmexQ/VAdqLOSUjGXnHWwcb7T97jDRc7T011EcnDG0fPPavNDiamdgE1EhtkgsCjVO0AWiQ tCgvdzFOvA/2sze8IUS/FG73JiNRYhbDSzsC4DZ+ivN6yQRLCXbJS0wGTlgY9w8rTqQ/Qz+3q0E6C Qq3sUNc5jd82Xkf0MaNw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oo2a8-00DKYo-HQ; Thu, 27 Oct 2022 13:06:01 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oo2ZV-00DKDC-5I for linux-arm-kernel@lists.infradead.org; Thu, 27 Oct 2022 13:05:22 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 0F0B423A; Thu, 27 Oct 2022 06:05:26 -0700 (PDT) Received: from bogus (e103737-lin.cambridge.arm.com [10.1.197.49]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 567363F7B4; Thu, 27 Oct 2022 06:05:18 -0700 (PDT) Date: Thu, 27 Oct 2022 14:05:15 +0100 From: Sudeep Holla To: Ulf Hansson Cc: Andy Gross , Bjorn Andersson , Konrad Dybcio , Dmitry Baryshkov , Maulik Shah , Rajendra Nayak , Amit Pundir , linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] arm64: dts: qcom: sm8250: Disable the not yet supported cluster idle state Message-ID: <20221027130515.uixhr4a7axmvtabe@bogus> References: <20221027115745.240516-1-ulf.hansson@linaro.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20221027115745.240516-1-ulf.hansson@linaro.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221027_060521_283329_BD002A69 X-CRM114-Status: GOOD ( 13.96 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Oct 27, 2022 at 01:57:45PM +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. > > vreg_l11c_3p3: failed to enable: -ETIMEDOUT > qcom-rpmh-regulator 18200000.rsc:pm8150l-rpmh-regulators: ldo11: devm_regulator_register() failed, ret=-110 > qcom-rpmh-regulator: probe of 18200000.rsc:pm8150l-rpmh-regulators failed with error -110 > > Reported-by: Amit Pundir > Fixes: 32bc936d7321 ("arm64: dts: qcom: sm8250: Add cpuidle states") Thanks for the patience and fixing it this way :). I take it is only the cluster states that has the issue because [1] only disables the CPU level states which was confusing and I had asked the same. Anyways for this, Reviewed-by: Sudeep Holla -- Regards, Sudeep _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel