From: Louis Chauvet <louis.chauvet@bootlin.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.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>,
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>
Cc: Hui Pu <Hui.Pu@gehealthcare.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Ian Ray <ian.ray@gehealthcare.com>
Subject: Re: [PATCH v5 5/7] drm/bridge: prevent encoder chain changes while iterating with list_for_each_entry_from()
Date: Thu, 9 Apr 2026 11:56:57 +0200 [thread overview]
Message-ID: <3ea41a49-5ec1-42f2-859d-0293c4b444aa@bootlin.com> (raw)
In-Reply-To: <20260324-drm-bridge-alloc-encoder-chain-mutex-v5-5-8bf786c5c7e6@bootlin.com>
On 3/24/26 9:58 AM, Luca Ceresoli wrote:
> These loops in drm_bridge.c iterate over the encoder chain using
> list_for_each_entry_from(), which does not prevent changes to the bridge
> chain while iterating over it.
>
> Convert most of those loops to instead use
> drm_for_each_bridge_in_chain_from(), which locks the chain.
>
> This also simplifies code.
>
> All the "simple" loops are converted here. The only ones not touched are
> those in drm_atomic_bridge_chain_pre_enable() and
> drm_atomic_bridge_chain_post_disable(), because they have nested loops
> which are not well handled by drm_for_each_bridge_in_chain_from(). Those
> two functions are handled by a separate commit.
>
> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Reviewed-by: Louis Chauvet <louis.chauvet@bootlin.com>
> ---
> drivers/gpu/drm/drm_bridge.c | 35 ++++++++++++-----------------------
> 1 file changed, 12 insertions(+), 23 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_bridge.c b/drivers/gpu/drm/drm_bridge.c
> index 42ca4b243579..37feb8143de4 100644
> --- a/drivers/gpu/drm/drm_bridge.c
> +++ b/drivers/gpu/drm/drm_bridge.c
> @@ -725,7 +725,7 @@ void drm_bridge_detach(struct drm_bridge *bridge)
> /**
> * drm_bridge_chain_mode_valid - validate the mode against all bridges in the
> * encoder chain.
> - * @bridge: bridge control structure
> + * @first_bridge: bridge control structure
> * @info: display info against which the mode shall be validated
> * @mode: desired mode to be validated
> *
> @@ -739,17 +739,14 @@ void drm_bridge_detach(struct drm_bridge *bridge)
> * MODE_OK on success, drm_mode_status Enum error code on failure
> */
> enum drm_mode_status
> -drm_bridge_chain_mode_valid(struct drm_bridge *bridge,
> +drm_bridge_chain_mode_valid(struct drm_bridge *first_bridge,
> const struct drm_display_info *info,
> const struct drm_display_mode *mode)
> {
> - struct drm_encoder *encoder;
> -
> - if (!bridge)
> + if (!first_bridge)
> return MODE_OK;
>
> - encoder = bridge->encoder;
> - list_for_each_entry_from(bridge, &encoder->bridge_chain, chain_node) {
> + drm_for_each_bridge_in_chain_from(first_bridge, bridge) {
> enum drm_mode_status ret;
>
> if (!bridge->funcs->mode_valid)
> @@ -767,7 +764,7 @@ EXPORT_SYMBOL(drm_bridge_chain_mode_valid);
> /**
> * drm_bridge_chain_mode_set - set proposed mode for all bridges in the
> * encoder chain
> - * @bridge: bridge control structure
> + * @first_bridge: bridge control structure
> * @mode: desired mode to be set for the encoder chain
> * @adjusted_mode: updated mode that works for this encoder chain
> *
> @@ -776,20 +773,16 @@ EXPORT_SYMBOL(drm_bridge_chain_mode_valid);
> *
> * Note: the bridge passed should be the one closest to the encoder
> */
> -void drm_bridge_chain_mode_set(struct drm_bridge *bridge,
> +void drm_bridge_chain_mode_set(struct drm_bridge *first_bridge,
> const struct drm_display_mode *mode,
> const struct drm_display_mode *adjusted_mode)
> {
> - struct drm_encoder *encoder;
> -
> - if (!bridge)
> + if (!first_bridge)
> return;
>
> - encoder = bridge->encoder;
> - list_for_each_entry_from(bridge, &encoder->bridge_chain, chain_node) {
> + drm_for_each_bridge_in_chain_from(first_bridge, bridge)
> if (bridge->funcs->mode_set)
> bridge->funcs->mode_set(bridge, mode, adjusted_mode);
> - }
> }
> EXPORT_SYMBOL(drm_bridge_chain_mode_set);
>
> @@ -1013,7 +1006,7 @@ EXPORT_SYMBOL(drm_atomic_bridge_chain_pre_enable);
>
> /**
> * drm_atomic_bridge_chain_enable - enables all bridges in the encoder chain
> - * @bridge: bridge control structure
> + * @first_bridge: bridge control structure
> * @state: atomic state being committed
> *
> * Calls &drm_bridge_funcs.atomic_enable (falls back on
> @@ -1023,22 +1016,18 @@ EXPORT_SYMBOL(drm_atomic_bridge_chain_pre_enable);
> *
> * Note: the bridge passed should be the one closest to the encoder
> */
> -void drm_atomic_bridge_chain_enable(struct drm_bridge *bridge,
> +void drm_atomic_bridge_chain_enable(struct drm_bridge *first_bridge,
> struct drm_atomic_state *state)
> {
> - struct drm_encoder *encoder;
> -
> - if (!bridge)
> + if (!first_bridge)
> return;
>
> - encoder = bridge->encoder;
> - list_for_each_entry_from(bridge, &encoder->bridge_chain, chain_node) {
> + drm_for_each_bridge_in_chain_from(first_bridge, bridge)
> if (bridge->funcs->atomic_enable) {
> bridge->funcs->atomic_enable(bridge, state);
> } else if (bridge->funcs->enable) {
> bridge->funcs->enable(bridge);
> }
> - }
> }
> EXPORT_SYMBOL(drm_atomic_bridge_chain_enable);
>
>
next prev parent reply other threads:[~2026-04-09 9:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 8:58 [PATCH v5 0/7] drm/bridge: protect encoder bridge chain with a mutex Luca Ceresoli
2026-03-24 8:58 ` [PATCH v5 1/7] drm/encoder: add mutex to protect the bridge chain Luca Ceresoli
2026-04-09 9:56 ` Louis Chauvet
2026-03-24 8:58 ` [PATCH v5 2/7] drm/encoder: drm_encoder_cleanup: lock the encoder chain mutex during removal Luca Ceresoli
2026-04-09 9:55 ` Louis Chauvet
2026-03-24 8:58 ` [PATCH v5 3/7] drm/bridge: drm_bridge_attach: lock the encoder chain mutex during insertion Luca Ceresoli
2026-04-09 9:56 ` Louis Chauvet
2026-03-24 8:58 ` [PATCH v5 4/7] drm/bridge: lock the encoder chain in scoped for_each loops Luca Ceresoli
2026-04-09 9:56 ` Louis Chauvet
2026-03-24 8:58 ` [PATCH v5 5/7] drm/bridge: prevent encoder chain changes while iterating with list_for_each_entry_from() Luca Ceresoli
2026-04-09 9:56 ` Louis Chauvet [this message]
2026-03-24 8:58 ` [PATCH v5 6/7] drm/bridge: prevent encoder chain changes while iterating with list_for_each_entry_reverse() Luca Ceresoli
2026-04-09 9:57 ` Louis Chauvet
2026-03-24 8:58 ` [PATCH v5 7/7] drm/bridge: prevent encoder chain changes in pre_enable/post_disable Luca Ceresoli
2026-04-09 9:57 ` Louis Chauvet
2026-04-16 7:42 ` [PATCH v5 0/7] drm/bridge: protect encoder bridge chain with a mutex Luca Ceresoli
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=3ea41a49-5ec1-42f2-859d-0293c4b444aa@bootlin.com \
--to=louis.chauvet@bootlin.com \
--cc=Hui.Pu@gehealthcare.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.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=luca.ceresoli@bootlin.com \
--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
all inboxes | Powered by JetHome®