When opening a DRM debugfs file, locate the right path based on the
given DRM device FD.
This is needed so, in setups with more than one DRM device, any
operations on debugfs files affect the expected DRM device.
v2: rebased and fixed new API additions
Signed-off-by: Tomeu Vizoso
Reviewed-by: R
I've only found a very minor nitpick in intel_watermark.c,
other than that this patch does not apply cleanly on upstream/master,
so I've run no compilation or runtime tests.
When it applies to trunk, feel free to add my r-b.
On 2017-03-08 08:29 AM, Tomeu Vizoso wrote:
> When opening a DRM debugf
On Wed, Mar 08, 2017 at 02:29:59PM +0100, Tomeu Vizoso wrote:
> When opening a DRM debugfs file, locate the right path based on the
> given DRM device FD.
>
> This is needed so, in setups with more than one DRM device, any
> operations on debugfs files affect the expected DRM device.
>
> Signed-o
When opening a DRM debugfs file, locate the right path based on the
given DRM device FD.
This is needed so, in setups with more than one DRM device, any
operations on debugfs files affect the expected DRM device.
Signed-off-by: Tomeu Vizoso
---
Guess we could be more conservative and just rena
