Re: [PATCH v2 04/10] drm/aperture: Add infrastructure for aperture ownership

On Thu, Apr 15, 2021 at 09:12:14PM +0200, Thomas Zimmermann wrote: > Hi > > Am 15.04.21 um 14:57 schrieb Daniel Vetter: > > On Thu, Apr 15, 2021 at 08:56:20AM +0200, Thomas Zimmermann wrote: > > > Hi > > > > > > Am 09.04.21 um 11:22 schrieb Daniel Vetter: > > > > > Is it that easy? simepldrm's de

Re: [PATCH v2 04/10] drm/aperture: Add infrastructure for aperture ownership

Hi Am 15.04.21 um 14:57 schrieb Daniel Vetter: On Thu, Apr 15, 2021 at 08:56:20AM +0200, Thomas Zimmermann wrote: Hi Am 09.04.21 um 11:22 schrieb Daniel Vetter: Is it that easy? simepldrm's detach function has code to synchronize with concurrent hotplug removals. If we can use drm_dev_unplu

Re: [PATCH v2 04/10] drm/aperture: Add infrastructure for aperture ownership

On Thu, Apr 15, 2021 at 08:56:20AM +0200, Thomas Zimmermann wrote: > Hi > > Am 09.04.21 um 11:22 schrieb Daniel Vetter: > > > Is it that easy? simepldrm's detach function has code to synchronize with > > > concurrent hotplug removals. If we can use drm_dev_unplug() for > > > everything, > > > I'm

Re: [PATCH v2 04/10] drm/aperture: Add infrastructure for aperture ownership

Hi Am 09.04.21 um 11:22 schrieb Daniel Vetter: Is it that easy? simepldrm's detach function has code to synchronize with concurrent hotplug removals. If we can use drm_dev_unplug() for everything, I'm all for it. Uh, I should have looked at the code instead of just asking silly questions :-)

Re: [PATCH v2 04/10] drm/aperture: Add infrastructure for aperture ownership

On Fri, Apr 09, 2021 at 09:54:03AM +0200, Thomas Zimmermann wrote: > Hi > > Am 08.04.21 um 11:48 schrieb Daniel Vetter: > > On Thu, Mar 18, 2021 at 11:29:15AM +0100, Thomas Zimmermann wrote: > > > Platform devices might operate on firmware framebuffers, such as VESA or > > > EFI. Before a native d

Re: [PATCH v2 04/10] drm/aperture: Add infrastructure for aperture ownership

On Fri, Apr 09, 2021 at 09:06:56AM +0200, Thomas Zimmermann wrote: > Hi > > Am 08.04.21 um 11:48 schrieb Daniel Vetter: > > > > Maybe just me, but to avoid overstretching the attention spawn of doc > > readers I'd avoid this example here. And maybe make the recommendation > > stronger, e.g. "PCI

Re: [PATCH v2 04/10] drm/aperture: Add infrastructure for aperture ownership

Hi Am 08.04.21 um 11:48 schrieb Daniel Vetter: On Thu, Mar 18, 2021 at 11:29:15AM +0100, Thomas Zimmermann wrote: Platform devices might operate on firmware framebuffers, such as VESA or EFI. Before a native driver for the graphics hardware can take over the device, it has to remove any platfor

Re: [PATCH v2 04/10] drm/aperture: Add infrastructure for aperture ownership

Hi Am 08.04.21 um 11:48 schrieb Daniel Vetter: Maybe just me, but to avoid overstretching the attention spawn of doc readers I'd avoid this example here. And maybe make the recommendation stronger, e.g. "PCI device drivers can avoid open-coding remove_conflicting_framebuffers() by calling drm_f

Re: [PATCH v2 04/10] drm/aperture: Add infrastructure for aperture ownership

On Thu, Mar 18, 2021 at 11:29:15AM +0100, Thomas Zimmermann wrote: > Platform devices might operate on firmware framebuffers, such as VESA or > EFI. Before a native driver for the graphics hardware can take over the > device, it has to remove any platform driver that operates on the firmware > fram

[PATCH v2 04/10] drm/aperture: Add infrastructure for aperture ownership

Platform devices might operate on firmware framebuffers, such as VESA or EFI. Before a native driver for the graphics hardware can take over the device, it has to remove any platform driver that operates on the firmware framebuffer. Aperture helpers provide the infrastructure for platform drivers t