On Wed, 2021-05-19 at 13:51 +1000, Sam McNally wrote:
> On Wed, 19 May 2021 at 08:01, Lyude Paul wrote:
> >
> > Looks like these tests might still need to be fixed up a bit:
> >
> > [ 34.785042] (null): [drm:drm_dp_sideband_parse_req [drm_kms_helper]]
> > connection status reply parse length
On Wed, 19 May 2021 at 08:01, Lyude Paul wrote:
>
> Looks like these tests might still need to be fixed up a bit:
>
> [ 34.785042] (null): [drm:drm_dp_sideband_parse_req [drm_kms_helper]]
> connection status reply parse length fail 2 1
> [ 34.785082] (null): [drm:drm_dp_sideband_parse_req [
Looks like these tests might still need to be fixed up a bit:
[ 34.785042] (null): [drm:drm_dp_sideband_parse_req [drm_kms_helper]]
connection status reply parse length fail 2 1
[ 34.785082] (null): [drm:drm_dp_sideband_parse_req [drm_kms_helper]]
resource status reply parse length fail 2
Up requests are decoded by drm_dp_sideband_parse_req(), which operates
on a drm_dp_sideband_msg_rx, unlike down requests. Expand the existing
self-test helper sideband_msg_req_encode_decode() to copy the message
contents and length from a drm_dp_sideband_msg_tx to
drm_dp_sideband_msg_rx and use the
