On Mon, Oct 24, 2022 at 06:58:09PM +0300, Ville Syrjälä wrote: > On Mon, Oct 24, 2022 at 08:48:15AM -0700, Rob Clark wrote: > > On Mon, Oct 24, 2022 at 5:43 AM <maxime@xxxxxxxxxx> wrote: > > > > > > Hi, > > > > > > I've discussing the idea for the past year to add an IGT test suite that > > > all well-behaved KMS drivers must pass. > > > > > > The main idea behind it comes from v4l2-compliance and cec-compliance, > > > that are being used to validate that the drivers are sane. > > > > > > We should probably start building up the test list, and eventually > > > mandate that all tests pass for all the new KMS drivers we would merge > > > in the kernel, and be run by KCi or similar. > > > > Let's get https://patchwork.freedesktop.org/patch/502641/ merged > > first, that already gives us a mechanism similar to what we use in > > mesa to track pass/fail/flake > > > > Beyond that, I think some of the igt tests need to get more stable > > before we could consider a "mustpass" list. The kms_lease tests seem > > to fail on msm due to bad assumptions in the test about which CRTCs > > primary planes can attach to. The legacy-cursor crc tests seem a bit > > racy (there was a patch posted for that, not sure if it landed yet), > > etc. > > I think the safest set to start with would be pure uapi validation > stuff. Anything that interactics with real world hardware is a much > tougher cookie. So I guess we would remove kms_cursor_legacy, kms_lease and kms_tv_load_detect. Anything else? Thanks! Maxime
Attachment:
signature.asc
Description: PGP signature
