public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vignesh Raman <vignesh.raman@collabora.com>
To: Helen Koike <helen.koike@collabora.com>, dri-devel@lists.freedesktop.org
Cc: daniel@fooishbar.org, airlied@gmail.com, daniel@ffwll.ch,
	david.heidelberg@collabora.com, guilherme.gallo@collabora.com,
	sergi.blanch.torne@collabora.com, robdclark@gmail.com,
	linux-mediatek@lists.infradead.org,
	linux-rockchip@lists.infradead.org,
	linux-amlogic@lists.infradead.org, amd-gfx@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/9] drm/ci: mediatek: Add job to test panfrost and powervr GPU driver
Date: Mon, 19 Feb 2024 15:09:30 +0530	[thread overview]
Message-ID: <2083520a-13f3-0ecd-45ce-ee4ba34d5bca@collabora.com> (raw)
In-Reply-To: <61575073-ce37-4027-8f95-f05290cc10c4@collabora.com>

Hi Helen,

On 09/02/24 23:51, Helen Koike wrote:
> 
> 
> On 30/01/2024 12:03, Vignesh Raman wrote:
>> For mediatek mt8173, the GPU driver is powervr and for mediatek
>> mt8183, the GPU driver is panfrost. So add support in drm-ci to
>> test panfrost and powervr GPU driver for mediatek SOCs and update
>> xfails. Powervr driver was merged in linux kernel, but there's no
>> mediatek support yet. So disable the mt8173-gpu job which uses
>> powervr driver.
>>
>> Add panfrost specific tests to testlist and skip KMS tests for
>> panfrost driver since it is not a not a KMS driver. Also update
>> the MAINTAINERS file to include xfails for panfrost driver.
>>
>> Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>
> 
> Hi Vignesh, thanks for your work.
> 
> I'm still wondering about a few things, please check below.
> 
>> ---
>>
>> v2:
>>    - Add panfrost and PVR GPU jobs for mediatek SOC with new xfails, 
>> add xfail
>>      entry to MAINTAINERS.
> 
> Maybe we should review how the xfails failes are named. I think they 
> should start with the DRIVER_NAME instead of GPU_VERSION.
> 
> For instance, consider the following job:
> 
> mediatek:mt8183-gpu:
>    extends:
>      - .mt8183
>    variables:
>      GPU_VERSION: mediatek-mt8183-gpu
>      DRIVER_NAME: panfrost
> 
> And we have mediatek-mt8183-gpu-skips.txt
> 
> If there is an error, we want to notify the panfrost driver maintainers 
> (and maybe not the mediatek driver maintainers), so MAINTAINERS file 
> doesn't correspond to this.

Agree.

> 
> How about a naming <driver name>_<hardware/gpu>_<type: gpu/display> ?
> 
> powervr_mediatek-mt8173_gpu-skipts.txt
> mediatek_mediatek-mt8173_display-skipts.txt
> panfrost_mediatek-mt8183_gpu-skips.txt
> mediatek_mediatek-mt8183_display-skips.txt
> ...
> 
> What do you think?

Yes we can keep this naming. In this case do we still need gpu/display 
in the xfails file name?

Regards,
Vignesh

  reply	other threads:[~2024-02-19  9:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 15:03 [PATCH v3 0/9] drm/ci: Add support for GPU and display testing Vignesh Raman
2024-01-30 15:03 ` [PATCH v3 1/9] drm/ci: arm64.config: Enable CONFIG_DRM_ANALOGIX_ANX7625 Vignesh Raman
2024-02-09 18:21   ` Helen Koike
2024-01-30 15:03 ` [PATCH v3 2/9] drm/ci: mediatek: Rename exisitng job Vignesh Raman
2024-01-30 15:03 ` [PATCH v3 3/9] drm/ci: mediatek: Add job to test panfrost and powervr GPU driver Vignesh Raman
2024-02-09 18:21   ` Helen Koike
2024-02-19  9:39     ` Vignesh Raman [this message]
2024-02-19 12:52       ` Helen Koike
2024-01-30 15:03 ` [PATCH v3 4/9] drm/ci: meson: Rename exisitng job Vignesh Raman
2024-01-30 15:03 ` [PATCH v3 5/9] drm/ci: meson: Add job to test panfrost GPU driver Vignesh Raman
2024-01-30 15:03 ` [PATCH v3 6/9] drm/ci: rockchip: Rename existing job Vignesh Raman
2024-01-30 15:03 ` [PATCH v3 7/9] drm/ci: rockchip: Add job to test panfrost GPU driver Vignesh Raman
2024-01-30 15:03 ` [PATCH v3 8/9] drm/ci: uprev mesa version Vignesh Raman
2024-01-30 15:03 ` [PATCH v3 9/9] drm/ci: uprev IGT and update testlist Vignesh Raman
2024-02-10 18:17   ` Maíra Canal
2024-02-10 18:20     ` Maíra Canal
2024-02-14 14:10       ` Helen Koike
2024-02-19  8:52       ` Vignesh Raman
2024-03-06  2:40         ` 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=2083520a-13f3-0ecd-45ce-ee4ba34d5bca@collabora.com \
    --to=vignesh.raman@collabora.com \
    --cc=airlied@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel@ffwll.ch \
    --cc=daniel@fooishbar.org \
    --cc=david.heidelberg@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=guilherme.gallo@collabora.com \
    --cc=helen.koike@collabora.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=robdclark@gmail.com \
    --cc=sergi.blanch.torne@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