All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Cristian Ciocaltea" <cristian.ciocaltea@collabora.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v4 4/9] drm/vc4: hdmi: Propagate -EDEADLK to the top level
Date: Tue, 10 Nov 2026 00:33:05 +0000	[thread overview]
Message-ID: <sashiko-outbox-205865@kernel.org> (raw)
In-Reply-To: <20261110-vc4-common-scramb-v4-4-eaa141a0da0f@collabora.com>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] drm/vc4: hdmi: missing Fixes trailer for
  vc4_hdmi_handle_hotplug()
--

commit 6d4e22aadcba086750601443588ce618f73cc846
Author: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>

> drm/vc4: hdmi: Propagate -EDEADLK to the top level
>
> drm_connector_helper_funcs.detect_ctx() is expected to propagate
> -EDEADLK so that context owners, e.g. drm_helper_probe_detect_ctx(), can
> perform the required backoff and retry.
>
> vc4_hdmi_handle_hotplug() instead runs its own retry loop and calls
> drm_modeset_backoff() on an acquire context it does not own.  This drops
> all locks in the context, including connection_mutex held by the core.
>
> Drop the local retry logic and propagate -EDEADLK to the caller instead.
> This aligns VC4 with the expected detect_ctx() semantics.
>
> Acked-by: Maxime Ripard <mripard@kernel.org>
> Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>

[Severity: Low]
Since this fixes the local retry loop and drm_modeset_backoff() call in
vc4_hdmi_handle_hotplug(), should this include a Fixes tag?

  Fixes: 479d4f0be423 ("drm/vc4: drop all currently held locks if deadlock happens")

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261110-vc4-common-scramb-v4-0-eaa141a0da0f@collabora.com?part=4

  reply	other threads:[~2026-11-10  0:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10  0:13 [PATCH v4 0/9] drm/vc4: hdmi: Convert to common HDMI 2.0 scrambling infrastructure Cristian Ciocaltea
2026-11-10  0:13 ` [PATCH v4 1/9] drm/vc4: hdmi: Use common TMDS char rate constants Cristian Ciocaltea
2026-11-10  0:13 ` [PATCH v4 2/9] drm/vc4: hdmi: Switch to drm_hdmi_mode_needs_scrambling() Cristian Ciocaltea
2026-11-10 11:57   ` Maíra Canal
2026-11-10  0:13 ` [PATCH v4 3/9] drm/vc4: hdmi: Switch to .force_ctx() connector helper Cristian Ciocaltea
2026-11-10  0:13 ` [PATCH v4 4/9] drm/vc4: hdmi: Propagate -EDEADLK to the top level Cristian Ciocaltea
2026-11-10  0:33   ` sashiko-bot [this message]
2026-11-10 12:08   ` Maíra Canal
2026-11-10  0:13 ` [PATCH v4 5/9] drm/vc4: hdmi: Convert to drmm_connector_hdmi_init() Cristian Ciocaltea
2026-11-10  0:13 ` [PATCH v4 6/9] drm/vc4: hdmi: Convert to common HDMI 2.0 scrambling infrastructure Cristian Ciocaltea
2026-11-10  0:53   ` sashiko-bot
2026-11-10 12:11   ` Maíra Canal
2026-11-10 12:51     ` Cristian Ciocaltea
2026-11-10  0:13 ` [PATCH v4 7/9] drm/vc4: hdmi: Clamp CEC clock divider to its register field width Cristian Ciocaltea
2026-11-10  0:13 ` [PATCH v4 8/9] drm/vc4: hdmi: Bump BCM2835 max pixel clock to 165 MHz Cristian Ciocaltea
2026-11-10  0:13 ` [PATCH v4 9/9] drm/vc4: hdmi: Defer pixel clock validation to HDMI helpers Cristian Ciocaltea
2026-11-10 12:48 ` [PATCH v4 0/9] drm/vc4: hdmi: Convert to common HDMI 2.0 scrambling infrastructure Cristian Ciocaltea

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=sashiko-outbox-205865@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=cristian.ciocaltea@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.