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 D8CC1C636D4 for ; Tue, 31 Jan 2023 23:32:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230502AbjAaXcj (ORCPT ); Tue, 31 Jan 2023 18:32:39 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34904 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230013AbjAaXcg (ORCPT ); Tue, 31 Jan 2023 18:32:36 -0500 Received: from mx0b-0031df01.pphosted.com (mx0b-0031df01.pphosted.com [205.220.180.131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1A4F74A22E; Tue, 31 Jan 2023 15:32:33 -0800 (PST) Received: from pps.filterd (m0279871.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 30VNTgJA028435; Tue, 31 Jan 2023 23:32:16 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h=message-id : date : mime-version : subject : to : cc : references : from : in-reply-to : content-type : content-transfer-encoding; s=qcppdkim1; bh=ELZAQk6O3jQa16QepC2O+iGAaFK4ij19+eVMDpim58A=; b=WAmpGXRcAFDS5IF1ZhYU7SwuwpoeJEahhsZBKc4jnYU6gONNFutYoB/LXvk/SKI2EZrx HqvUo44euGaByXoXSL6bQJZtrKaB+NP0xmvg1NfWmhkkuuNbHfWp5jTbisgDT2a6mdaM MIMP45FYS1+8OaCOWFECgd7+RMrcbNJwwytcTIwVTEAaADoqJbt1wfcMlCI6FseFLJJi vfT9MDtJb7N5p0HpC/CFkFkrdhz9+HhQ37qUJCntGmc99X89vKkAJjq5Zx7WZ5EGIq3u ddDzIeJ6ANkaHvz0/2Q50KJ6pN3HnQTyNb3uD5QDZqCNm4ZbDnQfXFKiHcyZLTVxveVt BA== Received: from nalasppmta01.qualcomm.com (Global_NAT1.qualcomm.com [129.46.96.20]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3new3uac8w-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 31 Jan 2023 23:32:15 +0000 Received: from nalasex01a.na.qualcomm.com (nalasex01a.na.qualcomm.com [10.47.209.196]) by NALASPPMTA01.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTPS id 30VNWEAV007765 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 31 Jan 2023 23:32:14 GMT Received: from [10.110.114.165] (10.80.80.8) by nalasex01a.na.qualcomm.com (10.47.209.196) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.36; Tue, 31 Jan 2023 15:32:13 -0800 Message-ID: <43095d93-29c8-b30a-08c0-0a452770c1ce@quicinc.com> Date: Tue, 31 Jan 2023 15:32:12 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.2 Subject: Re: [RFT PATCH v2 2/3] drm/msm/dsi: Stop unconditionally powering up DSI hosts at modeset Content-Language: en-US To: Douglas Anderson , , Rob Clark , Dmitry Baryshkov CC: Andrzej Hajda , Laurent Pinchart , Sean Paul , Jonas Karlman , Vinod Koul , Robert Foss , , Daniel Vetter , David Airlie , , Stephen Boyd , Neil Armstrong , Jernej Skrabec , Dave Stevenson , References: <20230131141756.RFT.v2.1.I723a3761d57ea60c5dd754c144aed6c3b2ea6f5a@changeid> <20230131141756.RFT.v2.2.I4cfeab9d0e07e98ead23dd0736ab4461e6c69002@changeid> From: Abhinav Kumar In-Reply-To: <20230131141756.RFT.v2.2.I4cfeab9d0e07e98ead23dd0736ab4461e6c69002@changeid> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) To nalasex01a.na.qualcomm.com (10.47.209.196) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-GUID: uCvkqKdiMDR6zUORD7MGoz0XKomFveNA X-Proofpoint-ORIG-GUID: uCvkqKdiMDR6zUORD7MGoz0XKomFveNA X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.219,Aquarius:18.0.930,Hydra:6.0.562,FMLib:17.11.122.1 definitions=2023-01-31_08,2023-01-31_01,2022-06-22_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 lowpriorityscore=0 phishscore=0 clxscore=1015 suspectscore=0 mlxscore=0 mlxlogscore=999 impostorscore=0 adultscore=0 bulkscore=0 malwarescore=0 priorityscore=1501 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2301310202 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/31/2023 2:18 PM, Douglas Anderson wrote: > In commit 7d8e9a90509f ("drm/msm/dsi: move DSI host powerup to modeset > time"), we moved powering up DSI hosts to modeset time. This wasn't > because it was an elegant design, but there were no better options. > > That commit actually ended up breaking ps8640, and thus was born > commit ec7981e6c614 ("drm/msm/dsi: don't powerup at modeset time for > parade-ps8640") as a temporary hack to un-break ps8640 by moving it to > the old way of doing things. It turns out that ps8640 _really_ doesn't > like its pre_enable() function to be called after > dsi_mgr_bridge_power_on(). Specifically (from experimentation, not > because I have any inside knowledge), it looks like the assertion of > "RST#" in the ps8640 runtime resume handler seems like it's not > allowed to happen after dsi_mgr_bridge_power_on() > > Recently, Dave Stevenson's series landed allowing bridges some control > over pre_enable ordering. The meaty commit for our purposes is commit > 4fb912e5e190 ("drm/bridge: Introduce pre_enable_prev_first to alter > bridge init order"). As documented by that series, if a bridge doesn't > set "pre_enable_prev_first" then we should use the old ordering. > > Now that we have the commit ("drm/bridge: tc358762: Set > pre_enable_prev_first") we can go back to the old ordering, which also > allows us to remove the ps8640 special case. > > One last note is that even without reverting commit 7d8e9a90509f > ("drm/msm/dsi: move DSI host powerup to modeset time"), if you _just_ > revert the ps8640 special case and try it out then it doesn't seem to > fail anymore. I spent time bisecting / debugging this and it turns out > to be mostly luck, so we still want this patch to make sure it's > solid. Specifically the reason it sorta works these days is because > we implemented wait_hpd_asserted() in ps8640 now, plus the magic of > "pm_runtime" autosuspend. The fact that we have wait_hpd_asserted() > implemented means that we actually power the bridge chip up just a wee > bit earlier and then the bridge happens to stay on because of > autosuspend and thus ends up powered before dsi_mgr_bridge_power_on(). > > Cc: Dave Stevenson > Cc: Dmitry Baryshkov > Cc: Abhinav Kumar > Signed-off-by: Douglas Anderson > --- > > Changes in v2: > - Don't fold dsi_mgr_bridge_power_on() back into dsi_mgr_bridge_pre_enable() > > drivers/gpu/drm/msm/dsi/dsi_manager.c | 38 +-------------------------- > 1 file changed, 1 insertion(+), 37 deletions(-) > > diff --git a/drivers/gpu/drm/msm/dsi/dsi_manager.c b/drivers/gpu/drm/msm/dsi/dsi_manager.c > index 1bbac72dad35..2197a54b9b96 100644 > --- a/drivers/gpu/drm/msm/dsi/dsi_manager.c > +++ b/drivers/gpu/drm/msm/dsi/dsi_manager.c > @@ -34,32 +34,6 @@ static struct msm_dsi_manager msm_dsim_glb; > #define IS_SYNC_NEEDED() (msm_dsim_glb.is_sync_needed) > #define IS_MASTER_DSI_LINK(id) (msm_dsim_glb.master_dsi_link_id == id) > > -#ifdef CONFIG_OF > -static bool dsi_mgr_power_on_early(struct drm_bridge *bridge) > -{ > - struct drm_bridge *next_bridge = drm_bridge_get_next_bridge(bridge); > - > - /* > - * If the next bridge in the chain is the Parade ps8640 bridge chip > - * then don't power on early since it seems to violate the expectations > - * of the firmware that the bridge chip is running. > - * > - * NOTE: this is expected to be a temporary special case. It's expected > - * that we'll eventually have a framework that allows the next level > - * bridge to indicate whether it needs us to power on before it or > - * after it. When that framework is in place then we'll use it and > - * remove this special case. > - */ > - return !(next_bridge && next_bridge->of_node && > - of_device_is_compatible(next_bridge->of_node, "parade,ps8640")); > -} > -#else > -static inline bool dsi_mgr_power_on_early(struct drm_bridge *bridge) > -{ > - return true; > -} > -#endif > - > static inline struct msm_dsi *dsi_mgr_get_dsi(int id) > { > return msm_dsim_glb.dsi[id]; > @@ -265,12 +239,6 @@ static void dsi_mgr_bridge_power_on(struct drm_bridge *bridge) > int ret; > > DBG("id=%d", id); > - if (!msm_dsi_device_connected(msm_dsi)) > - return; > - > - /* Do nothing with the host if it is slave-DSI in case of bonded DSI */ > - if (is_bonded_dsi && !IS_MASTER_DSI_LINK(id)) > - return; > Why are these two checks removed? > ret = dsi_mgr_phy_enable(id, phy_shared_timings); > if (ret) > @@ -327,8 +295,7 @@ static void dsi_mgr_bridge_pre_enable(struct drm_bridge *bridge) > if (is_bonded_dsi && !IS_MASTER_DSI_LINK(id)) > return; > > - if (!dsi_mgr_power_on_early(bridge)) > - dsi_mgr_bridge_power_on(bridge); > + dsi_mgr_bridge_power_on(bridge); > > ret = msm_dsi_host_enable(host); > if (ret) { > @@ -438,9 +405,6 @@ static void dsi_mgr_bridge_mode_set(struct drm_bridge *bridge, > msm_dsi_host_set_display_mode(host, adjusted_mode); > if (is_bonded_dsi && other_dsi) > msm_dsi_host_set_display_mode(other_dsi->host, adjusted_mode); > - > - if (dsi_mgr_power_on_early(bridge)) > - dsi_mgr_bridge_power_on(bridge); > } > > static enum drm_mode_status dsi_mgr_bridge_mode_valid(struct drm_bridge *bridge,