[AMD Official Use Only - Internal Distribution Only]
That looks better to me :) As more things get added, I don't know how long you
will be able to hold sw/hw cleanup separate and the name could confuse
eventually.
Thanks,
Lijo
___
dri-devel mailing l
ucher, Alexander
*Subject:* [PATCH v5 03/27] drm/amdgpu: Split amdgpu_device_fini into
early and late
Some of the stuff in amdgpu_device_fini such as HW interrupts
disable and pending fences finilization must be done right away on
pci_remove while most of the stuff which relates to finilizing and
rele
...@gmail.com ; helg...@kernel.org
; Deucher, Alexander
Subject: [PATCH v5 03/27] drm/amdgpu: Split amdgpu_device_fini into early and
late
Some of the stuff in amdgpu_device_fini such as HW interrupts
disable and pending fences finilization must be done right away on
pci_remove while most of the
On Thu, Apr 29, 2021 at 3:04 AM Christian König
wrote:
>
>
>
> Am 28.04.21 um 17:11 schrieb Andrey Grodzovsky:
> > Some of the stuff in amdgpu_device_fini such as HW interrupts
> > disable and pending fences finilization must be done right away on
> > pci_remove while most of the stuff which relat
Am 28.04.21 um 17:11 schrieb Andrey Grodzovsky:
Some of the stuff in amdgpu_device_fini such as HW interrupts
disable and pending fences finilization must be done right away on
pci_remove while most of the stuff which relates to finilizing and
releasing driver data structures can be kept until
Some of the stuff in amdgpu_device_fini such as HW interrupts
disable and pending fences finilization must be done right away on
pci_remove while most of the stuff which relates to finilizing and
releasing driver data structures can be kept until
drm_driver.release hook is called, i.e. when the las
