Re: [PATCH v9 2/4] drm: Add API for capturing frame CRCs

2016-10-06 Thread Emil Velikov
On 6 October 2016 at 12:33, Tomeu Vizoso wrote: > On 10/06/2016 01:13 PM, Emil Velikov wrote: >> On 6 October 2016 at 09:56, Tomeu Vizoso wrote: >>> Adds files and directories to debugfs for controlling and reading frame >>> CRCs, per CRTC: >>> >>> dri/0/crtc-0/crc >>> dri/0/crtc-0/crc/control >>

Re: [PATCH v9 2/4] drm: Add API for capturing frame CRCs

2016-10-06 Thread Tomeu Vizoso
On 10/06/2016 01:13 PM, Emil Velikov wrote: > On 6 October 2016 at 09:56, Tomeu Vizoso wrote: >> Adds files and directories to debugfs for controlling and reading frame >> CRCs, per CRTC: >> >> dri/0/crtc-0/crc >> dri/0/crtc-0/crc/control >> dri/0/crtc-0/crc/data >> >> Drivers can implement the se

Re: [PATCH v9 2/4] drm: Add API for capturing frame CRCs

2016-10-06 Thread Emil Velikov
On 6 October 2016 at 09:56, Tomeu Vizoso wrote: > Adds files and directories to debugfs for controlling and reading frame > CRCs, per CRTC: > > dri/0/crtc-0/crc > dri/0/crtc-0/crc/control > dri/0/crtc-0/crc/data > > Drivers can implement the set_crc_source callback() in drm_crtc_funcs to > start a

[PATCH v9 2/4] drm: Add API for capturing frame CRCs

2016-10-06 Thread Tomeu Vizoso
Adds files and directories to debugfs for controlling and reading frame CRCs, per CRTC: dri/0/crtc-0/crc dri/0/crtc-0/crc/control dri/0/crtc-0/crc/data Drivers can implement the set_crc_source callback() in drm_crtc_funcs to start and stop generating frame CRCs and can add entries to the output b