public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helen Koike <helen.koike@collabora.com>
To: Vignesh Raman <vignesh.raman@collabora.com>,
	dri-devel@lists.freedesktop.org
Cc: daniels@collabora.com, airlied@gmail.com, daniel@ffwll.ch,
	emma@anholt.net, robdclark@gmail.com,
	david.heidelberg@collabora.com, guilherme.gallo@collabora.com,
	sergi.blanch.torne@collabora.com, hamohammed.sa@gmail.com,
	rodrigosiqueiramelo@gmail.com, melissa.srw@gmail.com,
	mairacanal@riseup.net, mcanal@igalia.com,
	linux-mediatek@lists.infradead.org,
	linux-amlogic@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 09/11] drm/ci: rockchip: Refactor existing rockchip jobs
Date: Fri, 15 Mar 2024 09:02:02 -0300	[thread overview]
Message-ID: <aba60de7-63a2-4009-bdfd-4d86cec464be@collabora.com> (raw)
In-Reply-To: <f53c716d-6d11-13f6-0ecf-ec02f4debcfa@collabora.com>



On 15/03/2024 08:18, Vignesh Raman wrote:
> Hi Helen,
> 
> On 07/03/24 19:32, Helen Koike wrote:
>>
>>
>> On 06/03/2024 00:06, Vignesh Raman wrote:
>>> For rockchip rk3288 and rk3399, the display driver is rockchip.
>>> Currently, in drm-ci for rockchip, only the display driver is
>>> tested. Refactor the existing rockchip jobs so that gpu driver
>>> testing jobs can be added later and update xfails accordingly.
>>>
>>> Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>
>>> ---
>>>
>>> v2:
>>>    - Refactor the patch to rename job to indicate display driver 
>>> testing,
>>>      rename the existing xfail files.
>>>
>>> v3:
>>>    - Add the job name in GPU_VERSION and use it for xfail file names
>>>      instead of using DRIVER_NAME. Also update xfails.
>>>
>>> v4:
>>>    - Remove the display suffix in job and rename xfails accordingly.
>>>      Remove the change adding job name in GPU_VERSION.
>>>
>>> ---
>>>   drivers/gpu/drm/ci/test.yml                   | 36 ++++++++----
>>>   .../drm/ci/xfails/rockchip-rk3288-fails.txt   | 58 ++++++-------------
>>>   .../drm/ci/xfails/rockchip-rk3288-flakes.txt  | 20 +++++++
>>>   .../drm/ci/xfails/rockchip-rk3288-skips.txt   | 54 ++---------------
>>>   .../drm/ci/xfails/rockchip-rk3399-fails.txt   | 38 ++++++------
>>>   .../drm/ci/xfails/rockchip-rk3399-flakes.txt  | 28 +++++++--
>>>   .../drm/ci/xfails/rockchip-rk3399-skips.txt   |  5 +-
>>>   7 files changed, 110 insertions(+), 129 deletions(-)
>>>   create mode 100644 
>>> drivers/gpu/drm/ci/xfails/rockchip-rk3288-flakes.txt
>>>
>>> diff --git a/drivers/gpu/drm/ci/test.yml b/drivers/gpu/drm/ci/test.yml
>>> index 6ae6398b3d88..831e580e6dfd 100644
>>> --- a/drivers/gpu/drm/ci/test.yml
>>> +++ b/drivers/gpu/drm/ci/test.yml
>>> @@ -153,33 +153,45 @@ msm:sdm845:
>>>     script:
>>>       - ./install/bare-metal/cros-servo.sh
>>> -rockchip:rk3288:
>>> -  extends:
>>> -    - .lava-igt:arm32
>>> +.rockchip:
>>>     stage: rockchip
>>>     variables:
>>> -    DRIVER_NAME: rockchip
>>
>> Looks like it make sense to keep DRIVER_NAME here, no?
>>
>>> -    DEVICE_TYPE: rk3288-veyron-jaq
>>>       DTB: ${DEVICE_TYPE}
>>>       BOOT_METHOD: depthcharge
>>> +
>>> +.rk3288:
>>> +  extends:
>>> +    - .lava-igt:arm32
>>> +    - .rockchip
>>
>> Maybe, instead of extending .rockchip here, make .rockchip tied to the 
>> DRIVER_NAME and .rk3288 tied to the GPU_VERSION, and on 
>> rockchip:rk3288 you can extend both .rockchip and .rk3288, what do you 
>> think?
>> So rockchip:rk3399 you can extend .rockchip and .rk3399.
>>
>> and in the panfrost one you can have a .panfrost (that can extend 
>> .rockchip if they are the same definition).
>>
>> I feel it becomes less confusing, what do you think?
>>
>> I would even add some prefix or suffix to make it less confusing, like 
>> .driver-rockchip and .gpu-rk3288 for instance, making it a bit more 
>> intuitive and helping our future selves :)
> 
> Thanks for the suggestion. This can be done. Should we do it only
> for rockchip jobs or others also (meson, mediatek) ?

I guess we could keep the same patter for all the make sense.

Helen

> 
>>
>>> +  variables:
>>> +    DEVICE_TYPE: rk3288-veyron-jaq
>>>       KERNEL_IMAGE_TYPE: "zimage"
>>> -    GPU_VERSION: rk3288
>>
>> Looks like it make sense to keep GPU_VERSION here, no? Same comment 
>> for .rk3399.
> Yes, will fix this.
> 
> Regards,
> Vignesh

  reply	other threads:[~2024-03-15 12:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06  3:06 [PATCH v4 00/11] drm/ci: Add support for GPU and display testing Vignesh Raman
2024-03-06  3:06 ` [PATCH v4 01/11] drm/ci: arm64.config: Enable CONFIG_DRM_ANALOGIX_ANX7625 Vignesh Raman
2024-03-06  3:06 ` [PATCH v4 02/11] drm/ci: uprev mesa version Vignesh Raman
2024-03-07 13:35   ` Helen Koike
2024-03-06  3:06 ` [PATCH v4 03/11] drm/ci: uprev IGT and update testlist Vignesh Raman
2024-03-07 13:35   ` Helen Koike
2024-03-15 11:12     ` Vignesh Raman
2024-03-15 12:00       ` Helen Koike
2024-03-15 11:37   ` Dmitry Baryshkov
2024-03-18 14:48     ` Vignesh Raman
2024-03-06  3:06 ` [PATCH v4 04/11] drm/ci: amdgpu: update xfails Vignesh Raman
2024-03-06  3:06 ` [PATCH v4 05/11] drm/ci: mediatek: Refactor existing mediatek jobs Vignesh Raman
2024-03-07 14:02   ` Helen Koike
2024-03-15 11:15     ` Vignesh Raman
2024-03-06  3:06 ` [PATCH v4 06/11] drm/ci: mediatek: Add job to test panfrost and powervr GPU driver Vignesh Raman
2024-03-06  3:06 ` [PATCH v4 07/11] drm/ci: meson: Refactor existing meson jobs Vignesh Raman
2024-03-07 14:02   ` Helen Koike
2024-03-06  3:06 ` [PATCH v4 08/11] drm/ci: meson: Add job to test panfrost GPU driver Vignesh Raman
2024-03-06  3:06 ` [PATCH v4 09/11] drm/ci: rockchip: Refactor existing rockchip jobs Vignesh Raman
2024-03-07 14:02   ` Helen Koike
2024-03-15 11:18     ` Vignesh Raman
2024-03-15 12:02       ` Helen Koike [this message]
2024-03-06  3:06 ` [PATCH v4 10/11] drm/ci: rockchip: Add job to test panfrost GPU driver Vignesh Raman
2024-03-06  3:06 ` [PATCH v4 11/11] drm/ci: add tests on vkms Vignesh Raman
2024-03-07 14:02 ` [PATCH v4 00/11] drm/ci: Add support for GPU and display testing Helen Koike
2024-03-15 11:23   ` Vignesh Raman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aba60de7-63a2-4009-bdfd-4d86cec464be@collabora.com \
    --to=helen.koike@collabora.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=daniels@collabora.com \
    --cc=david.heidelberg@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emma@anholt.net \
    --cc=guilherme.gallo@collabora.com \
    --cc=hamohammed.sa@gmail.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mairacanal@riseup.net \
    --cc=mcanal@igalia.com \
    --cc=melissa.srw@gmail.com \
    --cc=robdclark@gmail.com \
    --cc=rodrigosiqueiramelo@gmail.com \
    --cc=sergi.blanch.torne@collabora.com \
    --cc=vignesh.raman@collabora.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox