On 07.08.2025 13:18, Christian König wrote:
> IIRC we settled on printing everything DRM related (e.g. display, device 
> lifetime, clients etc...) with the DRM macros.
> 
> But everything related to general HW information like PCI slot configuration, 
> BARs, speed etc... is printed with the general kernel functions, e.g. 
> dev_err() dev_warn()....
> 
> Background is that a lot of messages are printed by the PCI subsystem while 
> resizing BARs for example and it just doesn't make sense to enable/disable 
> the amdgpu prints based on DRM log level around that.
> 
> So as far as I can see there isn't much left TODO on that side.
> 
> Regards,
> Christian.
> 
> On 07.08.25 12:20, Brahmajit Das wrote:
> > Hello Alex, Christian,
> > 
> > I'm a mentee at Linux kernel Bug Fixing Summer 2025. I came across the
> > TODO list on the kernel doc, and specifically this section[0]. Would
> > amdgpu be open to this conversion. I saw that before starting it is
> > recommended to talk with Sean and the relevant maintainer. Hence I'm
> > emailing you folks.
> > 
> > I guess you can also refer to this,
> > https://patchwork.freedesktop.org/patch/msgid/[email protected]
> > 
> > [0]:
> > https://docs.kernel.org/gpu/todo.html#convert-logging-to-drm-functions-with-drm-device-parameter
> > 
> 

Understood, thanks.

-- 
Regards,
listout

Reply via email to