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

2025-02-08 Thread Dmitry Baryshkov
On Thu, Jan 23, 2025 at 12:12:43PM +0200, Jani Nikula wrote: > On Thu, 23 Jan 2025, Dmitry Baryshkov wrote: > > On Fri, Jan 17, 2025 at 10:56:35AM +0200, Dmitry Baryshkov wrote: > >> Existing DPCD access functions return an error code or the number of > >> bytes being read / write in case of parti

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

2025-01-23 Thread Jani Nikula
On Thu, 23 Jan 2025, Dmitry Baryshkov wrote: > On Fri, Jan 17, 2025 at 10:56:35AM +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 pa

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

2025-01-22 Thread Dmitry Baryshkov
On Fri, Jan 17, 2025 at 10:56:35AM +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 c

[PATCH RFC 0/7] drm/display: dp: add new DPCD access functions

2025-01-17 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