Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp4794382rwd; Tue, 23 May 2023 12:38:15 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7tJWfroBPHFpYBbsCoA25p0fnr8ZRmHFNchHFSu0Z4ZQHMu9L1unRTcxGlcDOXpDbb/mqJ X-Received: by 2002:a05:6a21:6d9b:b0:105:e434:670b with SMTP id wl27-20020a056a216d9b00b00105e434670bmr17749109pzb.4.1684870695305; Tue, 23 May 2023 12:38:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684870695; cv=none; d=google.com; s=arc-20160816; b=fX7Z3Es5f6q8f7sghwho7ewovgczRcikc44g+YwHIeUXLleMdoYWVpnZYQ2cC1dkR5 FYWda3GVNpdI05OrURJ2hfK8vKXRfLkm4AkUaGJpd5NTd6UcNIqzpmH3cVTvMUfr+Bzn 3hR7di8fGc9vD7t448QiDYuTHE/JrpxRp4oxP/skSpFNlBtN2+uQ0Xf6ivuR6xu2N8Zv JUiaGNtQpUz2cwwlQ9g9ZKgujS1hiCv4/cpUIQjEuUb3MDNWVTznRxfbBONVFurphNeF v+edDMZ9wNom0YDGvCuLlpJaxKJWb2SBLKbewdB4xxWIKIM5YkEWiX+jnMP1gbPZDG5T a4HQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=X4dOZT20dOqS0usZgo9QW+bAxHjpFuRs1ASLPZBhyvI=; b=gsmUCM83Te2ZGbaXFzPmoA5ETtYC9lKSH5PhIW+zzVIGRy1xiH8AfI5y3qi5oiWZg4 dsfLih59srL2UDj07e3edFaCnhV8yauMo1gwYl9Wb45pOJyLyMUJPc/v2keQf2FxtOCp xhFKd1ibk1QZI5bQB6YE7wvPuNvKUYBPV6PfFGuVzwDxufun3FF3/0ZYF3ekdPolVoj6 y3nVcjiLwQNi2eo+Ccyv/s/aW8u9ZWvTiRL4+74AExXtW5qscAMyxKUzSFuZgo2Ig0hX 22SPXHGgdu0WKJxedniXNgTExiyETjU0+mctdlRO3e1NoGmf3TLUGUEekIvn0WF7Zzay EtSA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b=MKCTUdSN; 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=quicinc.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z64-20020a633343000000b005347ab5e4e2si6951540pgz.125.2023.05.23.12.38.00; Tue, 23 May 2023 12:38:15 -0700 (PDT) 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=@quicinc.com header.s=qcppdkim1 header.b=MKCTUdSN; 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=quicinc.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237965AbjEWTXX (ORCPT + 99 others); Tue, 23 May 2023 15:23:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33536 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229473AbjEWTXW (ORCPT ); Tue, 23 May 2023 15:23:22 -0400 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C0BA4119; Tue, 23 May 2023 12:23:20 -0700 (PDT) Received: from pps.filterd (m0279864.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 34NDsmwA032276; Tue, 23 May 2023 19:23:08 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=X4dOZT20dOqS0usZgo9QW+bAxHjpFuRs1ASLPZBhyvI=; b=MKCTUdSNq6Ap04GWW+n0jYEdbortfYUbFIKWs+fftOD+Mb/770hh+fbukjizbk2eCO4Z sVQ1+ivq4jJV+Tn18z+A3guboeIDrlJgf5pxEMTWoW94y8GjRJWulMhxsMosp6GO7lGb u8lProlvhh+qNbaiTkKvEYZHaPnfp++4t+HUUOwHUUcsUAOt9wu6nUpGPJcidk8p0zRb hKbKOCel8mKurvdIWExSe0Vf8Hhv+Br1gTuKnWRL7IBZJpYEdP0UhrZgv+Ik+k9GrVqF lPesL5FVZYH7QAjQvAoEzZcJQNtYOgFynjG6vkhN0ixk1Bixuts1KPY7m1BoOENV1jFN zg== Received: from nalasppmta03.qualcomm.com (Global_NAT1.qualcomm.com [129.46.96.20]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3qr6h0v5sj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 23 May 2023 19:23:07 +0000 Received: from nalasex01a.na.qualcomm.com (nalasex01a.na.qualcomm.com [10.47.209.196]) by NALASPPMTA03.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTPS id 34NJN6Kc028839 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 23 May 2023 19:23:07 GMT Received: from [10.134.70.142] (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.42; Tue, 23 May 2023 12:23:05 -0700 Message-ID: Date: Tue, 23 May 2023 12:23:04 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [PATCH] drm/msm/dp: add module parameter for PSR Content-Language: en-US To: Johan Hovold , Dmitry Baryshkov CC: , Rob Clark , "Sean Paul" , David Airlie , Daniel Vetter , , , , , , References: <20230427232848.5200-1-quic_abhinavk@quicinc.com> <053819bd-b3c4-a72c-9316-85d974082ad6@linaro.org> From: Abhinav Kumar In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01a.na.qualcomm.com (10.52.223.231) 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: RLVmB3q_iuB8PXhW-xmEok0S0tp12gQd X-Proofpoint-ORIG-GUID: RLVmB3q_iuB8PXhW-xmEok0S0tp12gQd X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.957,Hydra:6.0.573,FMLib:17.11.176.26 definitions=2023-05-23_12,2023-05-23_02,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 impostorscore=0 bulkscore=0 spamscore=0 suspectscore=0 clxscore=1011 adultscore=0 phishscore=0 mlxscore=0 lowpriorityscore=0 mlxlogscore=999 malwarescore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2304280000 definitions=main-2305230157 X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham 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 5/23/2023 8:24 AM, Johan Hovold wrote: > On Fri, May 12, 2023 at 09:13:04PM +0300, Dmitry Baryshkov wrote: >> On 28/04/2023 02:28, Abhinav Kumar wrote: >>> On sc7280 where eDP is the primary display, PSR is causing >>> IGT breakage even for basic test cases like kms_atomic and >>> kms_atomic_transition. Most often the issue starts with below >>> stack so providing that as reference >>> >>> Call trace: >>> dpu_encoder_assign_crtc+0x64/0x6c >>> dpu_crtc_enable+0x188/0x204 >>> drm_atomic_helper_commit_modeset_enables+0xc0/0x274 >>> msm_atomic_commit_tail+0x1a8/0x68c >>> commit_tail+0xb0/0x160 >>> drm_atomic_helper_commit+0x11c/0x124 >>> drm_atomic_commit+0xb0/0xdc >>> drm_atomic_connector_commit_dpms+0xf4/0x110 >>> drm_mode_obj_set_property_ioctl+0x16c/0x3b0 >>> drm_connector_property_set_ioctl+0x4c/0x74 >>> drm_ioctl_kernel+0xec/0x15c >>> drm_ioctl+0x264/0x408 >>> __arm64_sys_ioctl+0x9c/0xd4 >>> invoke_syscall+0x4c/0x110 >>> el0_svc_common+0x94/0xfc >>> do_el0_svc+0x3c/0xb0 >>> el0_svc+0x2c/0x7c >>> el0t_64_sync_handler+0x48/0x114 >>> el0t_64_sync+0x190/0x194 >>> ---[ end trace 0000000000000000 ]--- >>> [drm-dp] dp_ctrl_push_idle: PUSH_IDLE pattern timedout >>> >>> Other basic use-cases still seem to work fine hence add a >>> a module parameter to allow toggling psr enable/disable till >>> PSR related issues are hashed out with IGT. >> >> For the reference: Bjorn reported that he has issues with VT on a >> PSR-enabled laptops. This patch fixes the issue for him > > Module parameters are almost never warranted, and it is definitely not > the right way to handle a broken implementation. > > I've just sent a revert that unconditionally disables PSR support until > the implementation has been fixed: > > https://lore.kernel.org/lkml/20230523151646.28366-1-johan+linaro@kernel.org/ > > Johan I dont completely agree with this. Even the virtual terminal case was reported to be fixed by one user but not the other. So it was probably something missed out either in validation or reproduction steps of the user who reported it to be fixed OR the user who reported it not fixed. That needs to be investigated now. We should have ideally gone with the modparam with the feature patches itself knowing that it gets enabled for all sinks if PSR is supported. I had discussed with Rob that till we have some more confidence with the reported issues we would go with the modparam so as to not do the full revert. In this particular case, the one line revert is not really a deal breaker. In some other implementations, it might not really be so trivial to revert the feature with a one line change. So I would like to understand what is the concern with the mod param if the maintainers are onboard with it.