From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794586105; b=m08yozvmFe/KWbHm5w+XnHpo9SrrxABwhWqJ0Vp3gmGjA4DLdqCkdGeab6or0ouNnYvn Z9y9gzKdvP1MsJRT7ZDW8Q2DTLBSfo3xhzAfQhl7ZakKvCIlYVjbesQzVYPe4vw86iyte KrMgPJSOb3ZpmcTKZFJe/Dn1v8/NCJeBLNAaUprdJXXcQyEE+TPw+BXw+fqsquN0+b6fU AWMC9InsHYZpzWKVtKuUtwOkVpi7RjruJLqo1866OK85k2Gdjq+2glwxTejEh18IyNEzt VYCva/PERoxadDVuPhvo9/AgX4E0/VFjGgdIGIKtg7ZFHUU4OC86WgnnLjifYubxg9w== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794586105; h=Received:DKIM-Signature:Message-ID:From:Subject:Reply-To:To:Cc: In-Reply-To:References:Content-Type:Content-Transfer-Encoding:Date; bh=6ryxFwwcER6FOSNecYjXVfS7v18vVPAs/JONPuhnvVk=; b=Qriryf14LXdGjCS1KqDJUNMQLL+T5VJyFaRvc6Bmd++08xB1Rl3UYShuV5XlDwWlFZXR fAak8kcqzOjhw0j66eMpQ4mKsnoR6UDJUPxwhlzQbKztriKMhAT1+v+04pghifD3wBX// Xjqve49Akl3RvTUbw6DqD9zQhD1fwZpXcN3sYMslgSoeM2xujo2LbDOQPzt3BP+B7iNAL 3C6qAmgYoqtkqzPGKCVkTe8WAJLJMVl0GdEXgRMackB+Comb0J7NKVSoBf5L5GJzBYGrL w5i7Z/Im+fn5m3UkTrClXUZ7q6091g12duJg9EhlSrHKJ9RDgO8aim8T67JXjrFNr6Q== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=cY3VOVAp; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 388BC606A884 for ; Fri, 13 Nov 2026 16:08:25 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=cY3VOVAp Received: by smtp.kernel.org (Postfix) with ESMTPSA id AACA41F000C4; Fri, 13 Nov 2026 16:08:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1794586105; bh=6ryxFwwcER6FOSNecYjXVfS7v18vVPAs/JONPuhnvVk=; h=From:Subject:Reply-To:To:Cc:In-Reply-To:References:Date; b=cY3VOVApbt5h+WMzqSbbXgiBmMKV3s6IB/7euA0QKP1t1Tkd+okMlurxoIgyCpY+9 0qvL3C4SiyrUxnMU9QDGu7kvdSVl/Hl9N6dsmJ2fRUuhQekdbXgGbymXrr08QdsCqH 8GsHADX8RWvGYBuKRDK0KAiSh/niGus+zdQMIKtrgCMFloQnhgDisYXr/Z1/PytHTP LrbnECVBzAJyeqpgMJJLo1kHqIDYa3lOp2di9/hF1Hc8+WQQBDNL0EeLBuxsVbvyD1 CHuVFPJbi33SjYdxV70Ng7il/y/iEqSKq0XtntT1gf4BuwCW+prw1aNLQjOxktMjYy 9OaWLq//tH55Q== Message-ID: From: sashiko-bot@kernel.org Subject: Re: [PATCH 2/3] drm/msm/mdss: reset all block resets described in DT Reply-To: sashiko-reviews@lists.linux.dev To: "Qianhui Xu" , dri-devel@lists.freedesktop.org Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org In-Reply-To: <20261113155606.1677313-3-xiaqinghuan@mail.ustc.edu.cn> References: <20261113155606.1677313-1-xiaqinghuan@mail.ustc.edu.cn> <20261113155606.1677313-3-xiaqinghuan@mail.ustc.edu.cn> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Fri, 13 Nov 2026 16:08:24 +0000 X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list Thank you for your contribution! Sashiko AI review found 1 potential issue to consider: - [Low] drm/msm/mdss: inaccurate INT2 reset description in msm_mdss_reset() commit -- commit 8dd3e2454eeeb0b73b84226f92cb892017ce9f66 Author: Qianhui Xu drm/msm/mdss: reset all block resets described in DT This commit switches msm_mdss_reset() to devm_reset_control_array_get() so that all resets listed in the MDSS device node are asserted and deasserted together. > msm_mdss_reset() acquires only the first reset listed in the MDSS > device node. Platforms can describe more than one MDSS block reset: the > SM8750 display clock controller also provides a reset for the MDSS core > INT2 interrupt controller, which is left out of reset when the > bootloader hands over with the display block still running. [ ... ] > diff --git a/drivers/gpu/drm/msm/msm_mdss.c b/drivers/gpu/drm/msm/msm_mds= s.c > index 259d362475c81..e10185ef21677 100644 > --- a/drivers/gpu/drm/msm/msm_mdss.c > +++ b/drivers/gpu/drm/msm/msm_mdss.c > @@ -325,7 +325,8 @@ static int msm_mdss_reset(struct device *dev) > { > struct reset_control *reset; > =20 > - reset =3D reset_control_get_optional_exclusive(dev, NULL); > + reset =3D devm_reset_control_array_get(dev, > + RESET_CONTROL_OPTIONAL_EXCLUSIVE); > if (!reset) { > /* Optional reset not specified */ > return 0; > @@ -342,8 +343,6 @@ static int msm_mdss_reset(struct device *dev) > msleep(20); > reset_control_deassert(reset); > =20 > - reset_control_put(reset); > - > return 0; > } [Severity: Low] As reported by Dmitry Baryshkov on v3 [1], is the commit message accurate in describing DISP_CC_MDSS_CORE_INT2_BCR on SM8750 as a reset for an INT2 interrupt controller? In drivers/clk/qcom/dispcc-sm8750.c, DISP_CC_MDSS_CORE_INT2_BCR (0xa000) is the block reset for the second internal MDSS core domain paired with mdss_int2_gdsc (0xb000) and the disp_cc_mdss_mdp1_clk, disp_cc_mdss_mdp_lut1_clk, disp_cc_mdss_vsync1_clk, and disp_cc_mdss_ahb1_clk branch clocks, as updated in commit "arm64: dts: qcom: sm8750: describe the second MDSS block reset". In addition, switching from reset_control_get_optional_exclusive() and reset_control_put() to devm_reset_control_array_get() keeps the exclusive reset controls acquired for the lifetime of the msm_mdss device rather than releasing them after the boot reset pulse. [1] https://lore.kernel.org/r/awb7bslhrhemsgvu7ubaejvurk6fecotgvqlwtvsoe2be= nqdgq@tvh2sfjbuzyu --=20 Sashiko AI review =C2=B7 https://sashiko.dev/#/patchset/20261113155606.1677= 313-1-xiaqinghuan@mail.ustc.edu.cn?part=3D2