From: Artur Rojek <contact@artur-rojek.eu>
To: Christophe Branchereau <cbranchereau@gmail.com>
Cc: Paul Cercueil <paul@crapouillou.net>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH v5 1/3] drm/ingenic : add ingenic_drm_bridge_atomic_enable and disable
Date: Tue, 05 Apr 2022 22:26:40 +0200 [thread overview]
Message-ID: <2d0ebd708f9c5a6f1ff1f3ba2e9c92c2@artur-rojek.eu> (raw)
In-Reply-To: <20220321133651.291592-2-cbranchereau@gmail.com>
On 2022-03-21 14:36, Christophe Branchereau wrote:
Hi Christophe,
looks good to me.
Cheers,
Artur
Acked-by: Artur Rojek <contact@artur-rojek.eu>
> ingenic_drm_bridge_atomic_enable allows the CRTC to be enabled after
> panels have slept out, and before their display is turned on, solving
> a graphical bug on the newvision nv3502c.
>
> Also add ingenic_drm_bridge_atomic_disable to balance it out.
>
> Signed-off-by: Christophe Branchereau <cbranchereau@gmail.com>
> ---
> drivers/gpu/drm/ingenic/ingenic-drm-drv.c | 34 +++++++++++++++--------
> 1 file changed, 23 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/gpu/drm/ingenic/ingenic-drm-drv.c
> b/drivers/gpu/drm/ingenic/ingenic-drm-drv.c
> index dcf44cb00821..2bbfd2e7fdab 100644
> --- a/drivers/gpu/drm/ingenic/ingenic-drm-drv.c
> +++ b/drivers/gpu/drm/ingenic/ingenic-drm-drv.c
> @@ -226,6 +226,18 @@ static int ingenic_drm_update_pixclk(struct
> notifier_block *nb,
> }
> }
>
> +static void ingenic_drm_bridge_atomic_enable(struct drm_bridge
> *bridge,
> + struct drm_bridge_state *old_bridge_state)
> +{
> + struct ingenic_drm *priv = drm_device_get_priv(bridge->dev);
> +
> + regmap_write(priv->map, JZ_REG_LCD_STATE, 0);
> +
> + regmap_update_bits(priv->map, JZ_REG_LCD_CTRL,
> + JZ_LCD_CTRL_ENABLE | JZ_LCD_CTRL_DISABLE,
> + JZ_LCD_CTRL_ENABLE);
> +}
> +
> static void ingenic_drm_crtc_atomic_enable(struct drm_crtc *crtc,
> struct drm_atomic_state *state)
> {
> @@ -237,28 +249,20 @@ static void
> ingenic_drm_crtc_atomic_enable(struct drm_crtc *crtc,
> if (WARN_ON(IS_ERR(priv_state)))
> return;
>
> - regmap_write(priv->map, JZ_REG_LCD_STATE, 0);
> -
> /* Set addresses of our DMA descriptor chains */
> next_id = priv_state->use_palette ? HWDESC_PALETTE : 0;
> regmap_write(priv->map, JZ_REG_LCD_DA0, dma_hwdesc_addr(priv,
> next_id));
> regmap_write(priv->map, JZ_REG_LCD_DA1, dma_hwdesc_addr(priv, 1));
>
> - regmap_update_bits(priv->map, JZ_REG_LCD_CTRL,
> - JZ_LCD_CTRL_ENABLE | JZ_LCD_CTRL_DISABLE,
> - JZ_LCD_CTRL_ENABLE);
> -
> drm_crtc_vblank_on(crtc);
> }
>
> -static void ingenic_drm_crtc_atomic_disable(struct drm_crtc *crtc,
> - struct drm_atomic_state *state)
> +static void ingenic_drm_bridge_atomic_disable(struct drm_bridge
> *bridge,
> + struct drm_bridge_state *old_bridge_state)
> {
> - struct ingenic_drm *priv = drm_crtc_get_priv(crtc);
> + struct ingenic_drm *priv = drm_device_get_priv(bridge->dev);
> unsigned int var;
>
> - drm_crtc_vblank_off(crtc);
> -
> regmap_update_bits(priv->map, JZ_REG_LCD_CTRL,
> JZ_LCD_CTRL_DISABLE, JZ_LCD_CTRL_DISABLE);
>
> @@ -267,6 +271,12 @@ static void
> ingenic_drm_crtc_atomic_disable(struct drm_crtc *crtc,
> 1000, 0);
> }
>
> +static void ingenic_drm_crtc_atomic_disable(struct drm_crtc *crtc,
> + struct drm_atomic_state *state)
> +{
> + drm_crtc_vblank_off(crtc);
> +}
> +
> static void ingenic_drm_crtc_update_timings(struct ingenic_drm *priv,
> struct drm_display_mode *mode)
> {
> @@ -968,6 +978,8 @@ static const struct drm_encoder_helper_funcs
> ingenic_drm_encoder_helper_funcs =
>
> static const struct drm_bridge_funcs ingenic_drm_bridge_funcs = {
> .attach = ingenic_drm_bridge_attach,
> + .atomic_enable = ingenic_drm_bridge_atomic_enable,
> + .atomic_disable = ingenic_drm_bridge_atomic_disable,
> .atomic_check = ingenic_drm_bridge_atomic_check,
> .atomic_reset = drm_atomic_helper_bridge_reset,
> .atomic_duplicate_state = drm_atomic_helper_bridge_duplicate_state,
next prev parent reply other threads:[~2022-04-05 22:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 13:36 [PATCH v5 0/3] Ingenic DRM bridge_atomic_enable proposal Christophe Branchereau
2022-03-21 13:36 ` [PATCH v5 1/3] drm/ingenic : add ingenic_drm_bridge_atomic_enable and disable Christophe Branchereau
2022-04-05 20:26 ` Artur Rojek [this message]
2022-03-21 13:36 ` [PATCH v5 2/3] drm/panel: Add panel driver for NewVision NV3052C based LCDs Christophe Branchereau
2022-03-27 19:38 ` Sam Ravnborg
2022-03-21 13:36 ` [PATCH v5 3/3] drm/panel : innolux-ej030na and abt-y030xx067a : add .enable and .disable Christophe Branchereau
2022-03-21 14:21 ` Paul Cercueil
2022-03-21 14:39 ` Christophe Branchereau
2022-03-21 14:42 ` Christophe Branchereau
2022-03-27 19:45 ` Sam Ravnborg
2022-04-05 21:03 ` [PATCH v5 0/3] Ingenic DRM bridge_atomic_enable proposal Paul Cercueil
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=2d0ebd708f9c5a6f1ff1f3ba2e9c92c2@artur-rojek.eu \
--to=contact@artur-rojek.eu \
--cc=airlied@linux.ie \
--cc=cbranchereau@gmail.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).