From: Detlev Casanova <detlev.casanova@collabora.com>
To: Andy Yan <andyshrk@163.com>
Cc: linux-kernel@vger.kernel.org, "Sandy Huang" <hjc@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>,
"Andy Yan" <andy.yan@rock-chips.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiko Stuebner" <heiko.stuebner@cherry.de>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Dragan Simic" <dsimic@manjaro.org>,
"Chris Morgan" <macromorgan@hotmail.com>,
"Diederik de Haas" <didi.debian@cknow.org>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH v2 1/3] vop2: Add clock resets support
Date: Fri, 08 Nov 2024 11:53:47 -0500 [thread overview]
Message-ID: <1901885.tdWV9SEqCh@trenzalore> (raw)
In-Reply-To: <4605629.LvFx2qVVIh@trenzalore>
On Friday, 8 November 2024 11:39:57 EST Detlev Casanova wrote:
> On Thursday, 23 May 2024 23:09:26 EST Andy Yan wrote:
> > Hi Detlev,
> >
> > At 2024-05-23 02:57:48, "Detlev Casanova" <detlev.casanova@collabora.com>
>
> wrote:
> > >At the end of initialization, each VP clock needs to be reset before
> > >they can be used.
> > >
> > >Failing to do so can put the VOP in an undefined state where the
> > >generated HDMI signal is either lost or not matching the selected mode.
> >
> > Would you please provide a detailed description of your test case?
>
> The test case was to switch modes (using modetest) until the HDMI signal was
> lost on the TV side. It was also possible to detect the issue by tracking
> the HDMI TX Controller_VIDEO_MONITOR_STATUS[1-6] registers, especially at
> address 0x890, where the register would take the value `0x0000018c`.
>
> After adding these resets, the issue cannot be reproduced. I can share a
> script that reproduced this in the past (but this is an old patchset now, so
> things could have changed)
>
> > >Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>
> > >---
> > >
> > > drivers/gpu/drm/rockchip/rockchip_drm_vop2.c | 30 ++++++++++++++++++++
> > > 1 file changed, 30 insertions(+)
> > >
> > >diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
> > >b/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c index
> > >fdd768bbd487c..e81a67161d29a 100644
> > >--- a/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
> > >+++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
> > >@@ -17,6 +17,7 @@
> > >
> > > #include <linux/platform_device.h>
> > > #include <linux/pm_runtime.h>
> > > #include <linux/regmap.h>
> > >
> > >+#include <linux/reset.h>
> > >
> > > #include <linux/swab.h>
> > >
> > > #include <drm/drm.h>
> > >
> > >@@ -157,6 +158,7 @@ struct vop2_win {
> > >
> > > struct vop2_video_port {
> > >
> > > struct drm_crtc crtc;
> > > struct vop2 *vop2;
> > >
> > >+ struct reset_control *dclk_rst;
> > >
> > > struct clk *dclk;
> > > unsigned int id;
> > > const struct vop2_video_port_data *data;
> > >
> > >@@ -1915,6 +1917,26 @@ static int us_to_vertical_line(struct
> > >drm_display_mode *mode, int us)>
> > >
> > > return us * mode->clock / mode->htotal / 1000;
> > >
> > > }
> > >
> > >+static int vop2_clk_reset(struct vop2_video_port *vp)
> > >+{
> > >+ struct reset_control *rstc = vp->dclk_rst;
> > >+ struct vop2 *vop2 = vp->vop2;
> > >+ int ret;
> > >+
> > >+ if (!rstc)
> > >+ return 0;
> >
> > In fact, this check is not necessary here. The following reset control
> > api
> > will check for NULL pointer
>
> Agreed, I'll do a rebased v3 and remove the check.
Actually, re-thinking about it, the check is done to avoid the udelay(10); if
there is no resets configured, so I'd rather keep it that way.
> > >+
> > >+ ret = reset_control_assert(rstc);
> > >+ if (ret < 0)
> > >+ drm_warn(vop2->drm, "failed to assert reset\n");
> > >+ udelay(10);
> > >+ ret = reset_control_deassert(rstc);
> > >+ if (ret < 0)
> > >+ drm_warn(vop2->drm, "failed to deassert reset\n");
> > >+
> > >+ return ret;
> > >+}
> > >+
> > >
> > > static void vop2_crtc_atomic_enable(struct drm_crtc *crtc,
> > >
> > > struct drm_atomic_state
>
> *state)
>
> > > {
> > >
> > >@@ -2055,6 +2077,8 @@ static void vop2_crtc_atomic_enable(struct drm_crtc
> > >*crtc,>
> > >
> > > vop2_vp_write(vp, RK3568_VP_DSP_CTRL, dsp_ctrl);
> > >
> > >+ vop2_clk_reset(vp);
> > >+
> > >
> > > drm_crtc_vblank_on(crtc);
> > >
> > > vop2_unlock(vop2);
> > >
> > >@@ -2706,6 +2730,12 @@ static int vop2_create_crtcs(struct vop2 *vop2)
> > >
> > > vp->data = vp_data;
> > >
> > > snprintf(dclk_name, sizeof(dclk_name), "dclk_vp%d", vp-
> >
> >id);
> >
> > >+ vp->dclk_rst = devm_reset_control_get_optional(vop2-
> >
> >dev, dclk_name);
> >
> > >+ if (IS_ERR(vp->dclk_rst)) {
> > >+ drm_err(vop2->drm, "failed to get %s reset\n",
>
> dclk_name);
>
> > >+ return PTR_ERR(vp->dclk_rst);
> > >+ }
> > >+
> > >
> > > vp->dclk = devm_clk_get(vop2->dev, dclk_name);
> > > if (IS_ERR(vp->dclk)) {
> > >
> > > drm_err(vop2->drm, "failed to get %s\n",
>
> dclk_name);
next prev parent reply other threads:[~2024-11-08 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 18:57 [PATCH v2 0/3] drm: rockchip: vop2: Add VP clock resets support Detlev Casanova
2024-05-22 18:57 ` [PATCH v2 1/3] vop2: Add " Detlev Casanova
2024-05-24 3:09 ` Andy Yan
2024-11-08 16:39 ` [PATCH " Detlev Casanova
2024-11-08 16:53 ` Detlev Casanova [this message]
2024-05-22 18:57 ` [PATCH v2 2/3] arm64: dts: rockchip: Add VOP clock resets for rk3588s Detlev Casanova
2024-05-22 18:57 ` [PATCH v2 3/3] dt-bindings: display: vop2: Add VP clock resets Detlev Casanova
2024-05-23 14:51 ` Conor Dooley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1901885.tdWV9SEqCh@trenzalore \
--to=detlev.casanova@collabora.com \
--cc=airlied@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=boris.brezillon@collabora.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=dsimic@manjaro.org \
--cc=heiko.stuebner@cherry.de \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=macromorgan@hotmail.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox