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 8B71E7AE47; Fri, 23 Feb 2024 12:10:14 +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=1708690214; cv=none; b=nejg8Wu+I7iF0rE5oNDVzfzxG7qxI8+dWY+XkZ7mTdAgQr/tpQZUw3SO7kvfObyfVxzL7nUeA7OHEQe9/kZIRT+QV90WBmfgNAJfgh8tUXaTHm3kC2Ou7cWHxyJdJmHl6/0OPTh1MyvMD+wXtwUlL18LkWxAzqLWAzh7NmDOChs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708690214; c=relaxed/simple; bh=4mfjeqsrT5LLWTfnZOi1uQqHARRbPNHPlL7bWNXA1qs=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=P8+9BcaAI2kfdSOZukm1FIdbK8xvtQnlJXuIr0cYDxIxqBY/r1xja3Qj2DBoUklnLWb28tFRzdE91AZ2Wgoxu2cFUVzTF9GQk5S1p71Db87J2z1Oa28wFBK/qSAto8SX1kB1UK5zsDZdVqG7ZuDZgh08H+BiBhj+AMdETaVVpwE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=h72n9H/E; 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="h72n9H/E" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4B80DC433C7; Fri, 23 Feb 2024 12:10:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1708690214; bh=4mfjeqsrT5LLWTfnZOi1uQqHARRbPNHPlL7bWNXA1qs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=h72n9H/Ey6btg2YG3+/Lndvz6UL99KJBWHTd2DmoRO2yWH1/pu+jFKJsTzELXXwr9 vIacBhyEGk57aSoaG5rkePrkzJ8HlT6EbaoKn6IKXgGhBTEgUAgBUGhr9loLlZHJEp ZxTqExOuYNu/bJOFEen2Or5AE7hQ+yCu4H+zmNUAz3uefWv18K3hrjLl1ZuN00s8p5 K19x+3oTMDVW0ePSzIr3+a0r8iefy3Qh+FtcnlzmVqSWWznSrVA1Rw9nTICEOD/aBV JUuZlze6Xt3nUJzJdpMhuuzG1116zfi+uW9Z1vpbBqUi83BdreXLKp7K//DhXTLL1e UnGBCgRv5PJDQ== Date: Fri, 23 Feb 2024 17:40:10 +0530 From: Vinod Koul To: Johan Hovold Cc: Bjorn Andersson , Andrzej Hajda , Neil Armstrong , Robert Foss , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Daniel Vetter , Jonas Karlman , Laurent Pinchart , Jernej Skrabec , Konrad Dybcio , Kishon Vijay Abraham I , Dmitry Baryshkov , Rob Clark , Abhinav Kumar , Kuogee Hsieh , freedreno@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org, stable@vger.kernel.org, Bjorn Andersson Subject: Re: [PATCH 6/6] phy: qcom-qmp-combo: fix type-c switch registration Message-ID: References: <20240217150228.5788-1-johan+linaro@kernel.org> <20240217150228.5788-7-johan+linaro@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@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: <20240217150228.5788-7-johan+linaro@kernel.org> On 17-02-24, 16:02, Johan Hovold wrote: > Due to a long-standing issue in driver core, drivers may not probe defer > after having registered child devices to avoid triggering a probe > deferral loop (see fbc35b45f9f6 ("Add documentation on meaning of > -EPROBE_DEFER")). > > Move registration of the typec switch to after looking up clocks and > other resources. > > Note that PHY creation can in theory also trigger a probe deferral when > a 'phy' supply is used. This does not seem to affect the QMP PHY driver > but the PHY subsystem should be reworked to address this (i.e. by > separating initialisation and registration of the PHY). Acked-by: Vinod Koul -- ~Vinod