Hi All, On 09/12/25 17:33, Harikrishna Shenoy wrote: > With the DRM_BRIDGE_ATTACH_NO_CONNECTOR framework, the connector is > no longer initialized in bridge_attach() when the display controller > sets the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag. > This causes a null pointer dereference in cdns_mhdp_modeset_retry_fn() > when trying to access &conn->dev->mode_config.mutex. > Observed on a board where EDID read failed. > (log: https://gist.github.com/Jayesh2000/233f87f9becdf1e66f1da6fd53f77429) > > Patch 1 adds a connector_ptr which takes care of both > DRM_BRIDGE_ATTACH_NO_CONNECTOR and !DRM_BRIDGE_ATTACH_NO_CONNECTOR > case by setting the pointer in appropriate hooks and checking for pointer > validity before accessing the connector. > Patch 2 adds mode validation hook to bridge fucntions. > Patch 3 fixes HDCP to work with both DRM_BRIDGE_ATTACH_NO_CONNECTOR > and !DRM_BRIDGE_ATTACH_NO_CONNECTOR case by moving HDCP state handling > into the bridge atomic check inline with the > DRM_BRIDGE_ATTACH_NO_CONNECTOR model. > Patches 4,5 do necessary cleanup and alignment for using > connector pointer. > > The rationale behind the sequence of commits is we can cleanly > switch to drm_connector pointer after removal of connector helper > code blocks, which are anyways not touch after > DRM_BRIDGE_ATTACH_NO_CONNECTOR has been enabled in driver. > > The last patch make smaller adjustment: lowering the log level for > noisy DPCD transfer errors.
A gentle ping for this series. This has received multiple R/Bs. Please help with a review/merge of this series. Thanks, Beleswar [...]
