Mathias, There seems to a bug in the poll with the replacement of readb with read_byte related to timeout. I will have to fix that and also received few comments as well. Let me fix those and will post a new version which you can use for testing.
Thanks and Regards, Arun R Murthy -------------------- > -----Original Message----- > From: Metrical revel <[email protected]> > Sent: Tuesday, September 8, 2026 2:23 AM > To: Murthy, Arun R <[email protected]> > Cc: [email protected] > Subject: Re: [PATCHv4] drm/i915/dp: On DPCD init wake the DPRx for eDP > > Hi Arun, > > (Replying by email since patchwork doesn't support direct comments — > apologies if this duplicates my GitLab note.) > > Noticed v5's i915.CI.BAT is passing now — good sign the build issue is > resolved. > > Before I compile and test v5 on my hardware for a Tested-by, I wanted to flag > something from i915.CI.Full that looks a bit more specific than the usual > noise > we saw on v1/v3: > > igt@kms_cursor_crc@cursor-rapid-movement-128x128@pipe-a-edp-1: > shard-mtlp: PASS -> ABORT +1 other test abort > > igt@kms_cursor_crc@cursor-rapid-movement-128x128@pipe-d-edp-1: > shard-mtlp: PASS -> DMESG-WARN > > Unlike the earlier CI flags (which were all in unrelated subsystems like > gem_ccs/kms_plane_lowres), these two are both on eDP-1 specifically, same > shard, same test family, both regressing from PASS. Is this known/expected > noise on shard-mtlp, or worth digging into given it touches the exact > connector > this patch modifies? > > Happy to go ahead and test v5 on my hardware for a Tested-by either way — > just didn't want to give a Tested-by without flagging this first. > > Thanks, > Mathias
