[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250528070452.901183-1-tommaso.merciai.xr@bp.renesas.com>
Date: Wed, 28 May 2025 09:04:36 +0200
From: Tommaso Merciai <tommaso.merciai.xr@...renesas.com>
To: tomm.merciai@...il.com
Cc: linux-renesas-soc@...r.kernel.org,
biju.das.jz@...renesas.com,
Tommaso Merciai <tommaso.merciai.xr@...renesas.com>,
Andrzej Hajda <andrzej.hajda@...el.com>,
Neil Armstrong <neil.armstrong@...aro.org>,
Robert Foss <rfoss@...nel.org>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
Jonas Karlman <jonas@...boo.se>,
Jernej Skrabec <jernej.skrabec@...il.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>,
Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
Adam Ford <aford173@...il.com>,
Douglas Anderson <dianders@...omium.org>,
Jesse Van Gavere <jesseevg@...il.com>,
dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/2] Improve adv7511_mode_set()
Dear All,
Currently adv7511_bridge_atomic_enable() call adv7511_power_on(), then
adv7511_dsi_config_timing_gen() that is responsible to update h/v porch
params.
But during the adv7511_mode_set() adv7511->curr_mode change and this is
not reflected into the h/v ADV porch regs, then h/w porch regs are keeping
the old values.
This series fix this issue moving adv711_dsi_config_timing_gen() into
the adv7511_mode_set().
Thanks & Regards,
Tommaso
v1->v2:
- Added cover letter
Tommaso Merciai (2):
drm/bridge: adv7511: Move adv711_dsi_config_timing_gen() into
adv7511_mode_set()
drm/bridge: adv7511: Rename adv7511_dsi_config_timing_gen() into
adv7533_dsi_config_timing_gen()
drivers/gpu/drm/bridge/adv7511/adv7511.h | 1 +
drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 4 ++++
drivers/gpu/drm/bridge/adv7511/adv7533.c | 5 +----
3 files changed, 6 insertions(+), 4 deletions(-)
--
2.43.0
Powered by blists - more mailing lists