From: Sam Ravnborg <sam@ravnborg.org>
To: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
Cc: "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>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Sandy Huang" <hjc@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>,
"Andy Yan" <andy.yan@rock-chips.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Mark Yao" <markyao0591@gmail.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
kernel@collabora.com, "Alexandre ARNOUD" <aarnoud@me.com>,
"Luis de Arquer" <ldearquer@gmail.com>,
"Algea Cao" <algea.cao@rock-chips.com>
Subject: Re: [PATCH 13/14] drm/bridge: synopsys: Add DW HDMI QP TX controller driver
Date: Sat, 1 Jun 2024 16:32:26 +0200 [thread overview]
Message-ID: <20240601143226.GA2003970@ravnborg.org> (raw)
In-Reply-To: <20240601-b4-rk3588-bridge-upstream-v1-13-f6203753232b@collabora.com>
Hi Cristian,
a few drive-by comments below.
Sam
> +
> +static const struct drm_connector_funcs dw_hdmi_qp_connector_funcs = {
> + .fill_modes = drm_helper_probe_single_connector_modes,
> + .detect = dw_hdmi_connector_detect,
> + .destroy = drm_connector_cleanup,
> + .force = dw_hdmi_qp_connector_force,
> + .reset = drm_atomic_helper_connector_reset,
> + .atomic_duplicate_state = drm_atomic_helper_connector_duplicate_state,
> + .atomic_destroy_state = drm_atomic_helper_connector_destroy_state,
> +};
> +
> +static int dw_hdmi_qp_bridge_attach(struct drm_bridge *bridge,
> + enum drm_bridge_attach_flags flags)
> +{
> + struct dw_hdmi *hdmi = bridge->driver_private;
> +
> + if (flags & DRM_BRIDGE_ATTACH_NO_CONNECTOR)
> + return drm_bridge_attach(bridge->encoder, hdmi->next_bridge,
> + bridge, flags);
> +
> + return dw_hdmi_connector_create(hdmi, &dw_hdmi_qp_connector_funcs);
> +}
Are there any users left that requires the display driver to create the
connector?
In other words - could this driver fail if DRM_BRIDGE_ATTACH_NO_CONNECTOR
is not passed and drop dw_hdmi_connector_create()?
I did not try to verify this - just a naive question.
> +
> +static enum drm_mode_status
> +dw_hdmi_qp_bridge_mode_valid(struct drm_bridge *bridge,
> + const struct drm_display_info *info,
> + const struct drm_display_mode *mode)
> +{
> + struct dw_hdmi *hdmi = bridge->driver_private;
> + const struct dw_hdmi_plat_data *pdata = hdmi->plat_data;
> + enum drm_mode_status mode_status = MODE_OK;
> +
> + if (pdata->mode_valid)
> + mode_status = pdata->mode_valid(hdmi, pdata->priv_data, info,
> + mode);
> +
> + return mode_status;
> +}
> +
> +static void dw_hdmi_qp_bridge_atomic_disable(struct drm_bridge *bridge,
> + struct drm_bridge_state *old_state)
> +{
> + struct dw_hdmi *hdmi = bridge->driver_private;
> +
> + mutex_lock(&hdmi->mutex);
> + hdmi->disabled = true;
> + hdmi->curr_conn = NULL;
> + dw_hdmi_qp_update_power(hdmi);
> + dw_handle_plugged_change(hdmi, false);
> + mutex_unlock(&hdmi->mutex);
> +}
> +
> +static void dw_hdmi_qp_bridge_atomic_enable(struct drm_bridge *bridge,
> + struct drm_bridge_state *old_state)
> +{
> + struct dw_hdmi *hdmi = bridge->driver_private;
> + struct drm_atomic_state *state = old_state->base.state;
> + struct drm_connector *connector;
> +
> + connector = drm_atomic_get_new_connector_for_encoder(state,
> + bridge->encoder);
> +
> + mutex_lock(&hdmi->mutex);
> + hdmi->disabled = false;
> + hdmi->curr_conn = connector;
> + dw_hdmi_qp_update_power(hdmi);
> + dw_handle_plugged_change(hdmi, true);
> + mutex_unlock(&hdmi->mutex);
> +}
> +
> +static const struct drm_bridge_funcs dw_hdmi_qp_bridge_funcs = {
> + .atomic_duplicate_state = drm_atomic_helper_bridge_duplicate_state,
> + .atomic_destroy_state = drm_atomic_helper_bridge_destroy_state,
> + .atomic_reset = drm_atomic_helper_bridge_reset,
> + .attach = dw_hdmi_qp_bridge_attach,
> + .detach = dw_hdmi_bridge_detach,
> + .atomic_check = dw_hdmi_bridge_atomic_check,
> + .atomic_enable = dw_hdmi_qp_bridge_atomic_enable,
> + .atomic_disable = dw_hdmi_qp_bridge_atomic_disable,
> + .mode_set = dw_hdmi_bridge_mode_set,
The use of mode_set is deprecated - see drm_bridge.h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-06-01 14:33 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 13:12 [PATCH 00/14] Add initial support for the Rockchip RK3588 HDMI TX Controller Cristian Ciocaltea
2024-06-01 13:12 ` [PATCH 01/14] drm/bridge: dw-hdmi: Simplify clock handling Cristian Ciocaltea
2024-06-01 13:12 ` [PATCH 02/14] drm/bridge: dw-hdmi: Add dw-hdmi-common.h header Cristian Ciocaltea
2024-06-01 13:12 ` [PATCH 03/14] drm/bridge: dw-hdmi: Commonize dw_hdmi_i2c_adapter() Cristian Ciocaltea
2024-06-01 13:12 ` [PATCH 04/14] drm/bridge: dw-hdmi: Factor out AVI infoframe setup Cristian Ciocaltea
2024-06-01 13:12 ` [PATCH 05/14] drm/bridge: dw-hdmi: Factor out vmode setup Cristian Ciocaltea
2024-06-01 13:12 ` [PATCH 06/14] drm/bridge: dw-hdmi: Factor out hdmi_data_info setup Cristian Ciocaltea
2024-06-01 13:12 ` [PATCH 07/14] drm/bridge: dw-hdmi: Commonize dw_hdmi_connector_create() Cristian Ciocaltea
2024-06-01 13:12 ` [PATCH 08/14] drm/rockchip: dw_hdmi: Use modern drm_device based logging Cristian Ciocaltea
2024-06-01 13:12 ` [PATCH 09/14] drm/rockchip: dw_hdmi: Simplify clock handling Cristian Ciocaltea
2024-06-01 13:12 ` [PATCH 10/14] drm/rockchip: dw_hdmi: Use devm_regulator_get_enable() Cristian Ciocaltea
2024-06-01 13:12 ` [PATCH 11/14] drm/rockchip: dw_hdmi: Drop superfluous assignments of mpll_cfg, cur_ctr and phy_config Cristian Ciocaltea
2024-06-01 13:12 ` [PATCH 12/14] dt-bindings: display: rockchip,dw-hdmi: Add compatible for RK3588 Cristian Ciocaltea
2024-06-05 23:22 ` Rob Herring
2024-06-06 11:51 ` Cristian Ciocaltea
2024-06-06 14:58 ` Rob Herring
2024-06-06 19:28 ` Cristian Ciocaltea
2024-07-29 2:04 ` Andy Yan
2024-06-01 13:12 ` [PATCH 13/14] drm/bridge: synopsys: Add DW HDMI QP TX controller driver Cristian Ciocaltea
2024-06-01 14:32 ` Sam Ravnborg [this message]
2024-06-04 19:32 ` Cristian Ciocaltea
2024-06-04 20:41 ` Sam Ravnborg
2024-06-04 21:34 ` Cristian Ciocaltea
2024-06-05 10:11 ` Cristian Ciocaltea
2024-06-05 11:48 ` Neil Armstrong
2024-06-05 13:57 ` Cristian Ciocaltea
2024-06-14 6:56 ` Andy Yan
2024-06-14 8:34 ` Maxime Ripard
2024-06-14 8:39 ` neil.armstrong
2024-06-05 14:48 ` Heiko Stübner
2024-06-05 19:58 ` Luis de Arquer
2024-06-05 22:16 ` Heiko Stübner
2024-06-06 9:53 ` Cristian Ciocaltea
2024-06-06 10:16 ` Heiko Stübner
2024-06-06 11:32 ` Cristian Ciocaltea
2024-06-01 13:12 ` [PATCH 14/14] drm/rockchip: dw_hdmi: Add basic RK3588 support Cristian Ciocaltea
2024-06-01 14:50 ` kernel test robot
2024-06-01 17:15 ` kernel test robot
2024-06-01 16:32 ` [PATCH 00/14] Add initial support for the Rockchip RK3588 HDMI TX Controller Dmitry Baryshkov
2024-06-04 19:44 ` Cristian Ciocaltea
2024-06-04 23:49 ` Dmitry Baryshkov
2024-06-02 7:59 ` Piotr Oniszczuk
2024-06-04 19:59 ` Cristian Ciocaltea
2024-06-03 8:55 ` Neil Armstrong
2024-06-03 12:14 ` Andy Yan
2024-06-03 13:03 ` Heiko Stuebner
2024-06-03 13:08 ` neil.armstrong
2024-06-04 20:33 ` Cristian Ciocaltea
2024-06-05 9:25 ` Andy Yan
2024-06-05 9:28 ` neil.armstrong
2024-06-05 9:39 ` Maxime Ripard
2024-06-05 9:49 ` Andy Yan
2024-06-05 11:20 ` Cristian Ciocaltea
2024-06-03 16:22 ` Maxime Ripard
2024-07-14 19:03 ` Piotr Oniszczuk
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=20240601143226.GA2003970@ravnborg.org \
--to=sam@ravnborg.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=aarnoud@me.com \
--cc=airlied@gmail.com \
--cc=algea.cao@rock-chips.com \
--cc=andrzej.hajda@intel.com \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=ldearquer@gmail.com \
--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=markyao0591@gmail.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).