From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8C69134888F for ; Fri, 13 Feb 2026 08:48:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770972483; cv=none; b=RPAtXvVopWilKKvnrSoj6n68MQ3VOPo4LUeR47XNK7pTbi8klEat0yRu7ol/LHmUm5a9cqstL916S4zyy1GrJfSGBf2g6tAFPI8GjGepFPKgXLxvB+Zz3sfEYC4Yk8s5uHU24JUe2Yvhr6jvikFH06lwQcmVDRlwkwe7QCUctf0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770972483; c=relaxed/simple; bh=sYVPcY0W5aokmXXau1LiI58XbehQLsCoQ855DU9hmIE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=OtKP48zqWpVyMLVaDS8Vgs92dbxjH8wXQfj0RoGsfeg3i1XRIJVDkLOXdy4FSpxNbkfftNbiSUuCtm26vg2hGknjClFtbehiHRKgY++mpPB9+odGxNdYM1zFAAT4HvIx/YfbPdRMCbV7J1y5QrkkN/rwrYcHwqCXtwBM9DWd05A= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=FIEKyZ5r; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="FIEKyZ5r" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 26643C16AAE; Fri, 13 Feb 2026 08:48:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1770972483; bh=sYVPcY0W5aokmXXau1LiI58XbehQLsCoQ855DU9hmIE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=FIEKyZ5r/uNPJ9Vd0kESgfL8eu0ddYOGmMO9eBDw4pvtJ4iRAOHK1QHbZ56ADdNlp U0sl+rrUJeSOpm2efDE0bxRpLvIsUNg5R3Ba4dAZsj9EsHUzBcJRiyW1nU9UsMpi3w rQ9cIsbs6FZfPAuFgtM7eQihknk/A/50dRHDTXc0Yv7xNi3Uc/KJsk2VZmMKNpAYFJ Okow9mMImpT0kujkfr6NR4AOuuAw/zZpnhV8Yz6gin8Q1YfdfuB9lRaoaEc9A67kuZ FrRPuHnwgwtS8DUF/SVOxFCuDHgmbhjAMxTBhn7BXch8wS8Bxj2T8HKGXoXsZnu/ul C1wnMmWbmjW+Q== Received: from johan by rho.lan with local (Exim 4.98.2) (envelope-from ) id 1vqoqA-000000000YZ-175U; Fri, 13 Feb 2026 09:47:55 +0100 Date: Fri, 13 Feb 2026 09:47:54 +0100 From: Johan Hovold To: Loic Poulain Cc: vkoul@kernel.org, kishon@kernel.org, linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org, dmitry.baryshkov@oss.qualcomm.com, neil.armstrong@linaro.org, konrad.dybcio@oss.qualcomm.com, Abel Vesa Subject: Re: [PATCH v3 1/5] phy: qcom: qmp-combo: Prevent unnecessary PM runtime suspend at boot Message-ID: References: <20260205160240.748371-1-loic.poulain@oss.qualcomm.com> <20260205160240.748371-2-loic.poulain@oss.qualcomm.com> Precedence: bulk X-Mailing-List: linux-arm-msm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260205160240.748371-2-loic.poulain@oss.qualcomm.com> On Thu, Feb 05, 2026 at 05:02:36PM +0100, Loic Poulain wrote: > There is a small window where the device can suspend after > pm_runtime_enable() and before pm_runtime_forbid(), causing an > unnecessary suspend/resume cycle while the PHY is not yet registered. What do you think can trigger a suspend in that window? (A racing user space request to both disable and re-enable runtime PM could theoretically do so but not in practice.). > Move pm_runtime_forbid() before pm_runtime_enable() to eliminate > this race. I think the commit message should reflect that this isn't really an issue. Johan