From: Brian Norris <briannorris@chromium.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: dri-devel@lists.freedesktop.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>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Damon Ding <damon.ding@rock-chips.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Heiko Stuebner <heiko@sntech.de>,
Douglas Anderson <dianders@chromium.org>
Subject: Re: [PATCH] drm/bridge: analogix_dp: Power down synchronously on bridge disable
Date: Thu, 19 Nov 2026 15:23:07 -0800 [thread overview]
Message-ID: <av-E277eE3c6FxhR@google.com> (raw)
In-Reply-To: <7f73a078-1041-43b7-8e35-3a2d9c69240f@samsung.com>
On Thu, Nov 19, 2026 at 11:27:33PM +0100, Marek Szyprowski wrote:
> Sigh... Runtime PM API is highly confusing and imho a bit over-engineered.
Agreed. Or, over-implemented / under-engineered perhaps.
I'm working on trying to reduce some of the confusion (e.g., we're about
ready to eliminate all the differences between put*() and
put_*autosuspend()).
I'm nearly of a mind that put_sync() and friends serve more to confuse
than to help, because while they work like you expect much of the time,
they aren't really guaranteed to be all that synchronous. So in its
current state, it might be better to not pretend it's synchronous at
all.
Anyway, enough musing. Feel free to send me thoughts separately if you
have specific confusing things that you think could be improved.
Brian
prev parent reply other threads:[~2026-11-19 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20261119084929eucas1p26166723765c9707e2e2b81f8ded99da6@eucas1p2.samsung.com>
2026-11-19 8:49 ` [PATCH] drm/bridge: analogix_dp: Power down synchronously on bridge disable Marek Szyprowski
2026-11-19 8:59 ` sashiko-bot
2026-11-19 18:31 ` Brian Norris
2026-11-19 22:27 ` Marek Szyprowski
2026-11-19 22:40 ` Marek Szyprowski
2026-11-19 23:23 ` Brian Norris [this message]
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=av-E277eE3c6FxhR@google.com \
--to=briannorris@chromium.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=damon.ding@rock-chips.com \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=luca.ceresoli@bootlin.com \
--cc=m.szyprowski@samsung.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@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 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.