On Mon, Jun 29, 2026 at 10:48:03PM +0800, Yongxing Mou wrote: > The bridge connector framework currently invokes all bridge > hpd_notify() callbacks and unconditionally emits a connector hotplug > event afterwards. > > However, not every HPD notification requires a userspace hotplug event. > > In particular, DP MST bridges may use hpd_notify() to propagate HPD and > IRQ notifications through the bridge chain while the actual hotplug > handling is performed by the DRM DP MST core. Connector creation, > removal and userspace hotplug events are already managed by the MST > topology framework. > > Allow hpd_notify() implementations to suppress the bridge connector > hotplug event by introducing a bool *send_hotplug parameter. Drivers > can clear this flag when HPD processing should not result in a > connector hotplug notification.
Why? Worst case the kernel receives another hotplug notification which gets ignored by the driver. > > A NULL pointer indicates that hotplug suppression is not supported by > the caller, such as the connector detect polling path. And nothing in this patch makes any use of it. I'd say, it's questionable addition. Let me check other patches... > > Signed-off-by: Yongxing Mou <[email protected]> > --- > drivers/gpu/drm/bridge/lontium-lt9611uxc.c | 3 ++- > drivers/gpu/drm/display/drm_bridge_connector.c | 15 +++++++++------ > drivers/gpu/drm/meson/meson_encoder_hdmi.c | 3 ++- > drivers/gpu/drm/msm/dp/dp_display.c | 3 ++- > drivers/gpu/drm/msm/dp/dp_drm.h | 3 ++- > drivers/gpu/drm/omapdrm/dss/hdmi4.c | 3 ++- > include/drm/drm_bridge.h | 3 ++- > 7 files changed, 21 insertions(+), 12 deletions(-) -- With best wishes Dmitry
