Re: [RFC PATCH RESEND v4 0/6] drm/display: dp: add new DPCD access functions

2025-04-05 Thread Lyude Paul
This looks all good to me, do you need someone to push this to drm-misc? On Mon, 2025-03-24 at 13:51 +0200, Dmitry Baryshkov wrote: > Existing DPCD access functions return an error code or the number of > bytes being read / write in case of partial access. However a lot of > drivers either (incorr

Re: [RFC PATCH RESEND v4 0/6] drm/display: dp: add new DPCD access functions

2025-03-25 Thread Dmitry Baryshkov
On Mon, 24 Mar 2025 13:51:18 +0200, Dmitry Baryshkov wrote: > Existing DPCD access functions return an error code or the number of > bytes being read / write in case of partial access. However a lot of > drivers either (incorrectly) ignore partial access or mishandle error > codes. In other cases t

Re: [RFC PATCH RESEND v4 0/6] drm/display: dp: add new DPCD access functions

2025-03-25 Thread Dmitry Baryshkov
On Mon, Mar 24, 2025 at 03:34:02PM -0400, Lyude Paul wrote: > This looks all good to me, do you need someone to push this to drm-misc? No, I can do that. I have resent it in order to retrigger Intel and Xe CI builds. It seems that Xe built was successful and i915 shows unrelated issues. I think it

[RFC PATCH RESEND v4 0/6] drm/display: dp: add new DPCD access functions

2025-03-24 Thread Dmitry Baryshkov
Existing DPCD access functions return an error code or the number of bytes being read / write in case of partial access. However a lot of drivers either (incorrectly) ignore partial access or mishandle error codes. In other cases this results in a boilerplate code which compares returned value with