RE: [PATCH] drm/amdgpu: add the accelerator pcie class

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



[Public]

> -----Original Message-----
> From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
> Sent: Friday, May 26, 2023 2:55 AM
> To: Deucher, Alexander <Alexander.Deucher@xxxxxxx>
> Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Alex Deucher
> <alexdeucher@xxxxxxxxx>; bhelgaas@xxxxxxxxxx; amd-
> gfx@xxxxxxxxxxxxxxxxxxxxx; Zhang, Morris <Shiwu.Zhang@xxxxxxx>; linux-
> pci@xxxxxxxxxxxxxxx
> Subject: Re: [PATCH] drm/amdgpu: add the accelerator pcie class
>
> On Thu, May 25, 2023 at 08:52:06PM +0000, Deucher, Alexander wrote:
> > We already handle this today for CLASS_DISPLAY via a data table provided on
> our hardware that details the components on the board.  The driver can then
> determine whether or not that combination of components is supported.  If
> the data table doesn't exist or isn’t parse-able, or the components
> enumerated are not supported, the driver doesn't load.
>
> But things like module loading and initramfs generation still work off the ID
> table and not your internal tables.

Sure, and everything still works fine.  If the device is too new and the driver doesn't have support for it, it doesn't bind and returns -ENODEV when it probes the device.

Alex





[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux