From: Janne Grunau <j@jannau.net>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: dri-devel@lists.freedesktop.org,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
intel-gfx@lists.freedesktop.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-msm@vger.kernel.org,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
linux-usb@vger.kernel.org, Maxime Ripard <mripard@kernel.org>,
Daniel Vetter <daniel@ffwll.ch>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
freedreno@lists.freedesktop.org, David Airlie <airlied@gmail.com>,
Bjorn Andersson <andersson@kernel.org>
Subject: Re: [Intel-gfx] [PATCH v6 2/3] drm/bridge_connector: stop filtering events in drm_bridge_connector_hpd_cb()
Date: Fri, 28 Jul 2023 20:31:35 +0200 [thread overview]
Message-ID: <ZMQJh6BIM2mQ9fCo@jannau.net> (raw)
In-Reply-To: <20230709202511.287794-3-dmitry.baryshkov@linaro.org>
On 2023-07-09 23:25:10 +0300, Dmitry Baryshkov wrote:
> In some cases the bridge drivers would like to receive hotplug events
> even in the case new status is equal to the old status. In the DP case
> this is used to deliver "attention" messages to the DP host. Stop
> filtering the events in the drm_bridge_connector_hpd_cb() and let
> drivers decide whether they would like to receive the event or not.
Worth mentioning in the commit message that all current bridges which
set .hpd_notify appear to be safe w.r.t multiple calls with the same
status. meson_encoder_hdmi.c will do unnecessary work when called
repeatedly with status connected. Not sure if it is worth adressing
since I don't expect multiple calls with connector_status_connected to
occur for this particular bridge.
Reviewed-By: Janne Grunau <j@jannau.net>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> drivers/gpu/drm/drm_bridge_connector.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_bridge_connector.c b/drivers/gpu/drm/drm_bridge_connector.c
> index 19ae4a177ac3..84d8d310ef04 100644
> --- a/drivers/gpu/drm/drm_bridge_connector.c
> +++ b/drivers/gpu/drm/drm_bridge_connector.c
> @@ -113,16 +113,11 @@ static void drm_bridge_connector_hpd_cb(void *cb_data,
> struct drm_bridge_connector *drm_bridge_connector = cb_data;
> struct drm_connector *connector = &drm_bridge_connector->base;
> struct drm_device *dev = connector->dev;
> - enum drm_connector_status old_status;
>
> mutex_lock(&dev->mode_config.mutex);
> - old_status = connector->status;
> connector->status = status;
> mutex_unlock(&dev->mode_config.mutex);
>
> - if (old_status == status)
> - return;
> -
> drm_bridge_connector_hpd_notify(connector, status);
>
> drm_kms_helper_hotplug_event(dev);
> --
> 2.39.2
>
next prev parent reply other threads:[~2023-07-31 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 20:25 [Intel-gfx] [PATCH v6 0/3] drm/bridge_connector: implement OOB HPD handling Dmitry Baryshkov
2023-07-09 20:25 ` [Intel-gfx] [PATCH v6 1/3] drm: Add HPD state to drm_connector_oob_hotplug_event() Dmitry Baryshkov
2023-07-09 20:25 ` [Intel-gfx] [PATCH v6 2/3] drm/bridge_connector: stop filtering events in drm_bridge_connector_hpd_cb() Dmitry Baryshkov
2023-07-28 18:31 ` Janne Grunau [this message]
2023-07-09 20:25 ` [Intel-gfx] [PATCH v6 3/3] drm/bridge_connector: implement oob_hotplug_event Dmitry Baryshkov
2023-07-28 19:44 ` Janne Grunau
2023-07-09 21:06 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/bridge_connector: implement OOB HPD handling (rev2) Patchwork
2023-07-09 21:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-07-09 22:28 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=ZMQJh6BIM2mQ9fCo@jannau.net \
--to=j@jannau.net \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=rodrigo.vivi@intel.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