Hi Helen,
On 07/03/24 19:32, Helen Koike wrote:
On 06/03/2024 00:06, Vignesh Raman wrote:
Some ARM SOCs have a separate display controller and GPU, each with
different drivers. For mediatek mt8173, the GPU driver is powervr,
and the display driver is mediatek. In the case of mediatek mt8183,
the GPU driver is panfrost, and the display driver is mediatek.
With rockchip rk3288/rk3399, the GPU driver is panfrost, while the
display driver is rockchip. For amlogic meson, the GPU driver is
panfrost, and the display driver is meson.
IGT tests run various tests with different xfails and can test both
GPU devices and KMS/display devices. Currently, in drm-ci for MediaTek,
Rockchip, and Amlogic Meson platforms, only the GPU driver is tested.
This leads to incomplete coverage since the display is never tested on
these platforms. This commit series adds support in drm-ci to run tests
for both GPU and display drivers for MediaTek, Rockchip, and Amlogic
Meson platforms.
Uprev mesa and IGT in drm-ci and add amd, v3d, vc4 and vgem specific
tests to testlist. Have testlist.txt per driver and include a base
testlist so that the driver specific tests will run only on those
hardware
and add testlists to the MAINTAINERS file.
This series also includes patch to add vkms testing to drm-ci.
Working pipeline link,
https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1119859
Hi Vignesh, thanks for this patchset.
Just to confirm, the new convention is:
stages are named per DRIVER_NAME
Yes correct.
jobs are named DRIVER_NAME:GPU_VERSION
Yes
xfails files and testlist files are named DRIVER_NAME-<xfails-suffix>.txt
Base testlist is named as testlist.txt
driver specific testlist is named as testlist-$DRIVER_NAME.txt
xfails files are named as $DRIVER_NAME-$GPU_VERSION-<xfails-suffix>.txt
(mediatek-mt8183-fails.txt)
Looks good.
I just have some minor comments/questions in the series, please check.
Will address those and send v5.
Regards,
Vignesh
