From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
Cc: igt-dev@lists.freedesktop.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
eben@raspberrypi.org
Subject: Re: [igt-dev] [PATCH i-g-t] lib/igt_kms: Set writeback connector capacity to fix VC4 testing
Date: Wed, 14 Nov 2018 16:50:08 +0100 [thread overview]
Message-ID: <20181114165008.74a5f97e@bbrezillon> (raw)
In-Reply-To: <20181114153149.14912-1-paul.kocialkowski@bootlin.com>
Hi Paul,
On Wed, 14 Nov 2018 16:31:49 +0100
Paul Kocialkowski <paul.kocialkowski@bootlin.com> wrote:
> Support for writeback connectors was recently introduced in DRM, with
> an implementation in the VC4 DRM driver. This unfortunately broke IGT
> testing for the driver due to always-failing atomic commits.
>
> After boot up, the writeback connector is attached to a CRTC, with a
> virtual encoder and a plane (that takes the same framebuffer as the
> primary plane).
That's weird, the writeback connector should not be attached to its
CRTC by default, unless someone explicitly requested that. Maybe
something related to the fbdev emulation layer, but I'm not sure.
>
> Because IGT configures all the available planes, this plane is no
> longer associated with the writeback CRTC. The connector remains
> associated with the CRTC as the core does not automatically clean it up.
> IGT is not aware of the writeback connector (hidden by default), so it
> does not detach the CRTC. As a result, the atomic commit fails because
> the CRTC is moving to a disabled state with a connector still attached.
>
> Fix this issue by setting the writeback connector cap before getting
> DRM resources so that the connector can be discovered and the CRTC
> can be detached by IGT. Since it requires atomic support, make it
> conditional and move the atomic capability before getting DRM resources.
>
> The associated cap definitions are also updated to include the required
> writeback one.
>
> Signed-off-by: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
> ---
> include/drm-uapi/drm.h | 16 ++++++++++++++++
> lib/igt_kms.c | 8 ++++++--
Looks like [1] is doing pretty much the same thing.
[1]https://patchwork.freedesktop.org/patch/260289/
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-11-14 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 15:31 [igt-dev] [PATCH i-g-t] lib/igt_kms: Set writeback connector capacity to fix VC4 testing Paul Kocialkowski
2018-11-14 15:50 ` Boris Brezillon [this message]
2018-11-15 16:36 ` Paul Kocialkowski
2018-11-14 16:42 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-11-15 3:07 ` [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=20181114165008.74a5f97e@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=eben@raspberrypi.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=paul.kocialkowski@bootlin.com \
--cc=thomas.petazzoni@bootlin.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