The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.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>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Hui Pu" <Hui.Pu@gehealthcare.com>,
	"Ian Ray" <ian.ray@gehealthcare.com>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 01/41] drm/display: bridge-connector: attach the encoder to the created connector
Date: Tue, 21 Apr 2026 13:08:20 +0200	[thread overview]
Message-ID: <DHYSAK9P2RFA.WL1BXACGKTU0@bootlin.com> (raw)
In-Reply-To: <aaxyye3vsef56qxqmblv25mlwpjz5dqovblrgwaclq77tqjvps@kr3aec254a5y>

Hi Dmitry,

On Sat Apr 18, 2026 at 1:18 AM CEST, Dmitry Baryshkov wrote:
> On Fri, Apr 17, 2026 at 11:57:49AM +0200, Luca Ceresoli wrote:
>> Currently all users of the bridge-connector must call
>> drm_connector_attach_encoder() immediately after a successful
>> drm_bridge_connector_init().
>>
>> This is an unnecessary burden for users. Move the call to the end of
>> drm_bridge_connector_init() so all callers can be simplified.
>>
>> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
>> ---
>>  drivers/gpu/drm/display/drm_bridge_connector.c | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/display/drm_bridge_connector.c b/drivers/gpu/drm/display/drm_bridge_connector.c
>> index 39cc18f78eda..bba8327fe3f7 100644
>> --- a/drivers/gpu/drm/display/drm_bridge_connector.c
>> +++ b/drivers/gpu/drm/display/drm_bridge_connector.c
>> @@ -1055,6 +1055,10 @@ struct drm_connector *drm_bridge_connector_init(struct drm_device *drm,
>>  	    IS_ENABLED(CONFIG_DRM_DISPLAY_HDCP_HELPER))
>>  		drm_connector_attach_content_protection_property(connector, true);
>>
>> +	ret = drm_connector_attach_encoder(connector, encoder);
>
> I'd explicitly document that the connector is created and attached.

Sure!

I'd reword a bit the description, as I can't find a way to append the new
info without making it all become awkward:

 /**
  * drm_bridge_connector_init - Initialise a connector for a chain of bridges
  * @drm: the DRM device
  * @encoder: the encoder where the bridge chain starts
  *
- * Allocate, initialise and register a &drm_bridge_connector with the @drm
- * device. The connector is associated with a chain of bridges that starts at
+ * Create a new &drm_bridge_connector for the @drm device. The connector is
+ * allocated, initialised, registered with the @drm device and and attached
+ * to @encoder.
+ *
+ * The connector is associated with a chain of bridges that starts at
  * the @encoder. All bridges in the chain shall report bridge operation flags
  * (&drm_bridge->ops) and bridge output type (&drm_bridge->type), and none of
  * them may create a DRM connector directly.
  *
  * Returns a pointer to the new connector on success, or a negative error
  * pointer otherwise.
  */

Does it look fine?

> With that in place:
>
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>

Thanks!

Luca

--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2026-04-21 11:08 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17  9:57 [PATCH 00/41] drm/display: bridge-connector: attach encoder to the connector Luca Ceresoli
2026-04-17  9:57 ` [PATCH 01/41] drm/display: bridge-connector: attach the encoder to the created connector Luca Ceresoli
2026-04-17 23:18   ` Dmitry Baryshkov
2026-04-21 11:08     ` Luca Ceresoli [this message]
2026-04-21 11:18       ` Dmitry Baryshkov
2026-04-17  9:57 ` [PATCH 02/41] drm: adp: remove now-redundant call to drm_connector_attach_encoder() Luca Ceresoli
2026-04-17  9:57 ` [PATCH 03/41] drm/bridge: adv7511: " Luca Ceresoli
2026-04-17 23:18   ` Dmitry Baryshkov
2026-04-17  9:57 ` [PATCH 04/41] drm/bridge: ite-it6263: " Luca Ceresoli
2026-04-17  9:57 ` [PATCH 05/41] drm/bridge: ti-sn65dsi86: " Luca Ceresoli
2026-04-17  9:57 ` [PATCH 06/41] drm/imx/dcss: " Luca Ceresoli
2026-04-17  9:57 ` [PATCH 07/41] drm/imx: ldb: " Luca Ceresoli
2026-04-17  9:57 ` [PATCH 08/41] drm/imx: parallel-display: " Luca Ceresoli
2026-04-17  9:57 ` [PATCH 09/41] drm/imx/lcdc: " Luca Ceresoli
2026-04-17  9:57 ` [PATCH 10/41] drm/ingenic: " Luca Ceresoli
2026-04-17  9:57 ` [PATCH 11/41] drm/kmb/dsi: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 12/41] drm/mediatek: mtk_dpi: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 13/41] drm/mediatek: mtk_dsi: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 14/41] drm/meson: encoder_cvbs: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 15/41] drm/meson: encoder_hdmi: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 16/41] drm/msm/dp: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 17/41] drm/msm/hdmi: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 18/41] drm/omapdrm: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 19/41] rm/rockchip: cdn-dp: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 20/41] drm/rockchip: rk3066_hdmi: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 21/41] drm/tegra: hdmi: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 22/41] drm/tegra: rgb: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 23/41] drm/tests: bridge: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 24/41] drm: verisilicon: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 25/41] drm/exynos: exynos_dp: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 26/41] drm: rcar-du: encoder: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 27/41] drm: renesas: rz-du: rzg2l_du_encoder: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 28/41] drm/rockchip: analogix_dp: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 29/41] drm/rockchip: dw_dp: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 30/41] drm/rockchip: dw_hdmi_qp: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 31/41] drm/rockchip: inno-hdmi: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 32/41] drm/msm/mdp4: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 33/41] drm/msm/dsi: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 34/41] drm/mxsfb/lcdif: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 35/41] drm/rockchip: lvds: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 36/41] drm/tidss: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 37/41] drm/tilcdc: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 38/41] drm: zynqmp_kms: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 39/41] drm/imx: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 40/41] drm/rockchip: rgb: " Luca Ceresoli
2026-04-17  9:58 ` [PATCH 41/41] drm: renesas: shmobile: " Luca Ceresoli
2026-04-17 23:20   ` Dmitry Baryshkov

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=DHYSAK9P2RFA.WL1BXACGKTU0@bootlin.com \
    --to=luca.ceresoli@bootlin.com \
    --cc=Hui.Pu@gehealthcare.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ian.ray@gehealthcare.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=thomas.petazzoni@bootlin.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