From: Petri Latvala <petri.latvala@intel.com>
To: Liviu Dudau <liviu.dudau@arm.com>
Cc: IGT GPU Tool <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t v3] Add Arm drivers as supported drivers by igt.
Date: Thu, 20 Jun 2019 15:51:38 +0300 [thread overview]
Message-ID: <20190620125138.GJ22949@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20190620124254.6736-1-liviu.dudau@arm.com>
On Thu, Jun 20, 2019 at 01:42:54PM +0100, Liviu Dudau wrote:
> Add the drivers maintained by Arm developers to the igt.
>
> v3: Update the mali-dp driver's name to match kernel driver code.
> v2: Order the modules array entries alphabetically, as per
> Petri Latvala's suggestion.
>
> Signed-off-by: Liviu Dudau <liviu.dudau@arm.com>
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
> ---
> lib/drmtest.c | 3 +++
> lib/drmtest.h | 4 ++++
> 2 files changed, 7 insertions(+)
>
> diff --git a/lib/drmtest.c b/lib/drmtest.c
> index 25f203530..8243247a3 100644
> --- a/lib/drmtest.c
> +++ b/lib/drmtest.c
> @@ -205,7 +205,10 @@ static const struct module {
> void (*modprobe)(const char *name);
> } modules[] = {
> { DRIVER_AMDGPU, "amdgpu" },
> + { DRIVER_HDLCD, "hdlcd" },
> { DRIVER_INTEL, "i915", modprobe_i915 },
> + { DRIVER_KOMEDA, "komeda" },
> + { DRIVER_MALIDP, "mali-dp" },
> { DRIVER_PANFROST, "panfrost" },
> { DRIVER_V3D, "v3d" },
> { DRIVER_VC4, "vc4" },
> diff --git a/lib/drmtest.h b/lib/drmtest.h
> index 6c4c3899c..952f0c4b6 100644
> --- a/lib/drmtest.h
> +++ b/lib/drmtest.h
> @@ -45,6 +45,10 @@
> #define DRIVER_AMDGPU (1 << 4)
> #define DRIVER_V3D (1 << 5)
> #define DRIVER_PANFROST (1 << 6)
> +#define DRIVER_HDLCD (1 << 7)
> +#define DRIVER_MALIDP (1 << 8)
> +#define DRIVER_KOMEDA (1 << 9)
> +
> /*
> * Exclude DRVER_VGEM from DRIVER_ANY since if you run on a system
> * with vgem as well as a supported driver, you can end up with a
> --
> 2.22.0
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-06-20 12:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 15:18 [igt-dev] [PATCH i-g-t] Add Arm drivers as supported drivers by igt Liviu Dudau
2019-06-17 16:20 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2019-06-18 8:15 ` [igt-dev] [PATCH i-g-t] " Petri Latvala
2019-06-19 15:13 ` [igt-dev] [PATCH i-g-t v2] " Liviu Dudau
2019-06-20 8:00 ` Petri Latvala
2019-06-20 9:28 ` Liviu Dudau
2019-06-20 10:50 ` Petri Latvala
2019-06-20 12:39 ` Liviu Dudau
2019-06-20 12:42 ` [igt-dev] [PATCH i-g-t v3] " Liviu Dudau
2019-06-20 12:51 ` Petri Latvala [this message]
2019-06-20 12:36 ` [igt-dev] [PATCH i-g-t v2] " Daniel Vetter
2019-06-20 12:41 ` Liviu Dudau
2019-06-20 13:12 ` Daniel Vetter
2019-06-21 8:46 ` Daniel Vetter
2019-06-19 15:59 ` [igt-dev] ✓ Fi.CI.BAT: success for Add Arm drivers as supported drivers by igt. (rev2) Patchwork
2019-06-20 10:13 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-06-20 17:16 ` [igt-dev] ✓ Fi.CI.BAT: success for Add Arm drivers as supported drivers by igt. (rev3) Patchwork
2019-06-20 20:55 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=20190620125138.GJ22949@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=liviu.dudau@arm.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