Le 25/02/2025 à 12:41, Thomas Zimmermann a écrit :
Hi
Am 10.02.25 um 15:37 schrieb Louis Chauvet:
On 10/02/25 - 13:30, Greg Kroah-Hartman wrote:
The vkms driver does not need to create a platform device, as there is
no real platform resources associated it, it only did so because it was
simple to do that in order to get a device to use for resource
management of drm resources. Change the driver to use the faux device
instead as this is NOT a real platform device.
Cc: Louis Chauvet <[email protected]>
Cc: Haneen Mohammed <[email protected]>
Cc: Simona Vetter <[email protected]>
Cc: Melissa Wen <[email protected]>
Cc: Maarten Lankhorst <[email protected]>
Cc: Maxime Ripard <[email protected]>
Cc: Thomas Zimmermann <[email protected]>
Cc: David Airlie <[email protected]>
Cc: [email protected]
Reviewed-by: Lyude Paul <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Reviewed-by: Thomas Zimmermann <[email protected]>
Tested-by: Louis Chauvet <[email protected]>
Reviewed-by: Louis Chauvet <[email protected]>
Thanks for the modification, it seems to work.
Should this patch be merged through DRM trees? drm-misc-next is at
v6.14-rc4 and has struct faux_device.
Hi,
I was not aware the faux-device was merged, as it is a new feature, I
expected it to reach drm-misc-next on 6.15-rc1.
I plan to merge [1] today/tomorrow (well tested with platform_device),
and then I will submit an updated version of this patch (only trivial
conflicts, but never tested with multiple VKMS devices).
[1]:https://lore.kernel.org/all/[email protected]/
Thanks,
Louis Chauvet
Best regards
Thomas
Louis chauvet
--
Louis Chauvet, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
