On Fri, Oct 14, 2022 at 02:07:09AM +0200, Danilo Krummrich wrote:
> Hi Liviu,
>
> On 10/12/22 17:07, Liviu Dudau wrote:
> > Hi Danilo,
> >
> > Appologies again for the delay in reviewing this as I was at XDC last week.
>
> No worries, thanks for following up.
>
> > Looking at the documentation
Hi Liviu,
On 10/12/22 17:07, Liviu Dudau wrote:
Hi Danilo,
Appologies again for the delay in reviewing this as I was at XDC last week.
No worries, thanks for following up.
Looking at the documentation for drm_dev_unplug, you can get a hint about what
is going on:
/*
* [] There is
Hi Danilo,
Appologies again for the delay in reviewing this as I was at XDC last week.
This patch is causing a regression at 'rmmod' time as the drm_crtc_vblank_off()
does
not get called when we disable outputs and the HDLCD remains active as I keep
getting
unhandled context faults from the arm
When the driver is unbound, there might still be users in userspace
having an open fd and are calling into the driver.
While this is fine for drm managed resources, it is not for resources
bound to the device/driver lifecycle, e.g. clocks or MMIO mappings.
To prevent use-after-free issues we need
