From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Rob Clark <robdclark@gmail.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
Simona Vetter <simona@ffwll.ch>,
Simona Vetter <simona.vetter@ffwll.ch>
Cc: <dri-devel@lists.freedesktop.org>,
<linux-arm-msm@vger.kernel.org>,
<freedreno@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7 2/7] drm/msm/hdmi: program HDMI timings during atomic_pre_enable
Date: Fri, 7 Feb 2025 16:42:46 -0800 [thread overview]
Message-ID: <cdfa5cfd-6cdf-45cf-ac18-c2c217d4211a@quicinc.com> (raw)
In-Reply-To: <20250208-bridge-hdmi-connector-v7-2-0c3837f00258@linaro.org>
On 2/7/2025 4:27 PM, Dmitry Baryshkov wrote:
> The mode_set callback is deprecated, it doesn't get the
> drm_bridge_state, just mode-related argumetns. Also Abhinav pointed out
> that HDMI timings should be programmed after setting up HDMI PHY and
> PLL. Rework the code to program HDMI timings at the end of
> atomic_pre_enable().
>
I think now this needs to be changed that, program the HDMI timings at
the beginning of atomic_pre_enable() to match the location of mode_set()
With that fixed,
Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
> Reviewed-by: Maxime Ripard <mripard@kernel.org>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> drivers/gpu/drm/msm/hdmi/hdmi_bridge.c | 24 ++++++++++++++++--------
> 1 file changed, 16 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/msm/hdmi/hdmi_bridge.c b/drivers/gpu/drm/msm/hdmi/hdmi_bridge.c
> index d839c71091dcdc3b020fcbba8d698d58ee7fc749..bd94b3a70f0e5e457a88f089b491103a8c09567b 100644
> --- a/drivers/gpu/drm/msm/hdmi/hdmi_bridge.c
> +++ b/drivers/gpu/drm/msm/hdmi/hdmi_bridge.c
> @@ -126,15 +126,29 @@ static void msm_hdmi_config_avi_infoframe(struct hdmi *hdmi)
> hdmi_write(hdmi, REG_HDMI_INFOFRAME_CTRL1, val);
> }
>
> +static void msm_hdmi_set_timings(struct hdmi *hdmi,
> + const struct drm_display_mode *mode);
> +
> static void msm_hdmi_bridge_atomic_pre_enable(struct drm_bridge *bridge,
> struct drm_bridge_state *old_bridge_state)
> {
> + struct drm_atomic_state *state = old_bridge_state->base.state;
> struct hdmi_bridge *hdmi_bridge = to_hdmi_bridge(bridge);
> struct hdmi *hdmi = hdmi_bridge->hdmi;
> struct hdmi_phy *phy = hdmi->phy;
> + struct drm_encoder *encoder = bridge->encoder;
> + struct drm_connector *connector;
> + struct drm_connector_state *conn_state;
> + struct drm_crtc_state *crtc_state;
>
> DBG("power up");
>
> + connector = drm_atomic_get_new_connector_for_encoder(state, encoder);
> + conn_state = drm_atomic_get_new_connector_state(state, connector);
> + crtc_state = drm_atomic_get_new_crtc_state(state, conn_state->crtc);
> +
> + msm_hdmi_set_timings(hdmi, &crtc_state->adjusted_mode);
> +
> if (!hdmi->power_on) {
> msm_hdmi_phy_resource_enable(phy);
> msm_hdmi_power_on(bridge);
> @@ -177,17 +191,12 @@ static void msm_hdmi_bridge_atomic_post_disable(struct drm_bridge *bridge,
> }
> }
>
> -static void msm_hdmi_bridge_mode_set(struct drm_bridge *bridge,
> - const struct drm_display_mode *mode,
> - const struct drm_display_mode *adjusted_mode)
> +static void msm_hdmi_set_timings(struct hdmi *hdmi,
> + const struct drm_display_mode *mode)
> {
> - struct hdmi_bridge *hdmi_bridge = to_hdmi_bridge(bridge);
> - struct hdmi *hdmi = hdmi_bridge->hdmi;
> int hstart, hend, vstart, vend;
> uint32_t frame_ctrl;
>
> - mode = adjusted_mode;
> -
> hdmi->pixclock = mode->clock * 1000;
>
> hstart = mode->htotal - mode->hsync_start;
> @@ -306,7 +315,6 @@ static const struct drm_bridge_funcs msm_hdmi_bridge_funcs = {
> .atomic_reset = drm_atomic_helper_bridge_reset,
> .atomic_pre_enable = msm_hdmi_bridge_atomic_pre_enable,
> .atomic_post_disable = msm_hdmi_bridge_atomic_post_disable,
> - .mode_set = msm_hdmi_bridge_mode_set,
> .mode_valid = msm_hdmi_bridge_mode_valid,
> .edid_read = msm_hdmi_bridge_edid_read,
> .detect = msm_hdmi_bridge_detect,
>
next prev parent reply other threads:[~2025-02-08 0:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 0:26 [PATCH v7 0/7] drm/msm: make use of the HDMI connector infrastructure Dmitry Baryshkov
2025-02-08 0:27 ` [PATCH v7 1/7] drm/msm/hdmi: switch to atomic bridge callbacks Dmitry Baryshkov
2025-02-08 0:27 ` [PATCH v7 2/7] drm/msm/hdmi: program HDMI timings during atomic_pre_enable Dmitry Baryshkov
2025-02-08 0:42 ` Abhinav Kumar [this message]
2025-02-08 3:49 ` Dmitry Baryshkov
2025-02-08 0:27 ` [PATCH v7 3/7] drm/msm/hdmi: make use of the drm_connector_hdmi framework Dmitry Baryshkov
2025-02-08 4:14 ` Abhinav Kumar
2025-02-08 0:27 ` [PATCH v7 4/7] drm/msm/hdmi: get rid of hdmi_mode Dmitry Baryshkov
2025-02-08 0:27 ` [PATCH v7 5/7] drm/msm/hdmi: update HDMI_GEN_PKT_CTRL_GENERIC0_UPDATE definition Dmitry Baryshkov
2025-02-08 0:27 ` [PATCH v7 6/7] drm/msm/hdmi: also send the SPD and HDMI Vendor Specific InfoFrames Dmitry Baryshkov
2025-02-08 1:31 ` Abhinav Kumar
2025-02-08 2:04 ` Dmitry Baryshkov
2025-02-08 3:05 ` Abhinav Kumar
2025-02-08 3:24 ` Dmitry Baryshkov
2025-02-08 0:27 ` [PATCH v7 7/7] drm/msm/hdmi: use DRM HDMI Audio framework Dmitry Baryshkov
2025-02-10 22:26 ` Abhinav Kumar
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=cdfa5cfd-6cdf-45cf-ac18-c2c217d4211a@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=simona.vetter@ffwll.ch \
--cc=simona@ffwll.ch \
--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
all inboxes | Powered by JetHome®